Bisq Maintainer - Githubissues

cbeams commented 6 years ago

Docs: https://bisq.wiki/Bisq_Maintainer Team: @bisq-network/bisq-maintainers

sqrrm commented 3 years ago

Cycle 18 report

Almost 100% review this cycle. That includes talks on design and testing. We managed to release most of it after some minor issues.

https://github.com/bisq-network/compensation/issues/693

ripcurlx commented 3 years ago

Cycle 18 report

We pre-released v1.4.0, v1.4.1 and publicly released v1.4.2. Besides taking care of issues together with @cd2357, who got the triage permission for the Bisq repository recently, I mainly worked on our upcoming build system to be able to switch to a LTS Java version and most up-to-date JavaFX version.

/cc https://github.com/bisq-network/compensation/issues/704

sqrrm commented 3 years ago

Cycle 19 report

There was a lot of work to get 1.5.0 released with all the issues we had with 1.4.2. So far 1.5.0 seems to be at least not worse than 1.4.2 which is a good thing. There are still quite a lot of support cases lingering from 1.4.2 so I would consider stronger incentives for users to upgrade if we don't get a good uptake.

https://github.com/bisq-network/compensation/issues/721

ripcurlx commented 3 years ago

Cycle 19 report

We released v1.5.0 without a pre-release phase as it is not possible to trade with older versions because of the trade protocol changes. Also we wanted to get the bug fixes introduced in v1.4.2 out there as soon as possible. We do have a 70%+ adoption rate of v1.5.0 already, so I hope support cases should decrease soon. I do check now on a daily basis all GitHub notifications to react in-time on issues and PR changes to prevent unnecessary blocks from maintainers side.

/cc https://github.com/bisq-network/compensation/issues/723

ripcurlx commented 3 years ago

Cycle 20 report

Although we fixed with v1.5.1 already most of the issues experienced in v1.5.0, v1.5.2 shipped as a regular release should finally bring some calm over the holidays into mediation and support (hopefully).

I continue to check on a daily basis all GitHub notifications to react in-time on issues and PR changes to prevent unnecessary blocks from maintainers side. Over the holidays I wasn't able to deliver on this, but I'll try my best to clean out my notifications log today.

[EDIT] I did forget to mention that I had to renew my Code Signing Certificate for Windows for €91.55 (~$111). I'll add this to the desktop maintainer amount. [/EDIT]

/cc https://github.com/bisq-network/compensation/issues/746

sqrrm commented 3 years ago

Cycle 20 report

A fair few issues going on from the previous releases which added to the review and merge workload. Reviews are in general reported separately but there is an overhead of having to monitor PRs and handling the releases.

https://github.com/bisq-network/compensation/issues/747

sqrrm commented 3 years ago

Cycle 21 report

Voting in last cycle failed which so far caused less problems than I would've expected. The DAO code worked as expected and contributors have been very good about it.

https://github.com/bisq-network/compensation/issues/773

ripcurlx commented 3 years ago

Cycle 21 report

We released v1.5.3 and v1.5.4 as a hotfix release as we experienced behavior that looked like a DoS attack. Since those two releases everything is working again (except the TOR related issues every now and then, which are based on a real DoS attack).

/cc https://github.com/bisq-network/compensation/issues/758

ripcurlx commented 3 years ago

Cycle 22 report

We released v1.5.5, v1.5.6 of , v1.5.7, v1.5.8, and v1.5.9. v1.5.6 was a hotfix that fixed startup issues for limit offers, v1.5.8 was a follow-up release introducing dynamic min tx fee powered by mempool.space and v1.5.9 a hotfix for a mailbox message startup issue.

/cc https://github.com/bisq-network/compensation/issues/795

sqrrm commented 3 years ago

Cycle 22 report

I was unwell large part of this cycle. Did minimal review and merge, not requesting anything for the maintainer role.

https://github.com/bisq-network/compensation/issues/788

ripcurlx commented 3 years ago

Cycle 23 report

We released v1.6.0, v1.6.1 of and v1.6.2. v1.6.1 was a follow-up release after a v1.6.0 pre-release and v1.6.2 a hotfix release as an issue with SPV resync was introduced in v1.6.0.

/cc https://github.com/bisq-network/compensation/issues/813

sqrrm commented 3 years ago

Cycle 23 report

I haven't done all that much on this role except being moral support for @ripcurlx

https://github.com/bisq-network/compensation/issues/817

sqrrm commented 3 years ago

Cycle 24 report

Still doing limited maintainer work

https://github.com/bisq-network/compensation/issues/838

ripcurlx commented 3 years ago

Cycle 24 report

We released v1.6.3 and v1.6.4. v1.6.4 was a follow-up release after a v1.6.3 pre-release as we wanted to filter out one infrastructure change and a graceful restart if banned seednode addresses are misconfigured. This was triggered by myself after I published a seednode address to be banned that had an incorrect format. As there is no validation in the filter form, but there is one when the bisq.properties file is read on startup this prevented all nodes that stopped or restarted within a time window of three hours to start. The workaround to start again was to remove the bannedSeednodes line from the bisq.properties file. To prevent this in the future I'll add validation to the filter fields and already removed incorrect configured nodes when read in v1.6.4.

This two releases also include a completely new way to create the installers enabling us to move to a LTS Java version again (11) and also to be able to update JavaFX form now on again.

/cc https://github.com/bisq-network/compensation/issues/846

sqrrm commented 3 years ago

Cycle 25 report

Still doing minimal maintainer work.

https://github.com/bisq-network/compensation/issues/855

ripcurlx commented 3 years ago

Cycle 25 report

We released v1.6.5 - no hotfix this time 🥳 The new build pipeline works pretty fine, except for one Java Heap Space Error that is popping up since v1.6.4.

I had to move Travis from https://travis-ci.org to https://travis-ci.com with the downside that even with the free OS plan we have to ask for 25k new free build credits every now and then. Thanks to https://github.com/maxim-belkin we already have a GitHub action in place that verifies nearly everything the current Travis build does. Probably worth to add the last bit as well and get rid of Travis to reduce future maintenance issues.

I also prepared an additional CodeQL GitHub action to run security checks over the code base as well. I also plan to add a security policy to the repository soon.

/cc https://github.com/bisq-network/compensation/issues/860

sqrrm commented 3 years ago

Cycle 26 report

All release work has been reported in other posts, @ripcurlx is keeping up the more organized maintenance work.

https://github.com/bisq-network/compensation/issues/874

ripcurlx commented 3 years ago

Cycle 26 report

We released v1.7.0 which was a hard fork because of a privacy issue reported by @woodser. This release needed in-depth testing because of different upgrade scenarios and was deployed without a pre-release version. So far we only saw issue during dispute handling which was addressed in pre-release v1.7.1. Our users started to see lots of DAO not in-sync popups which we weren't aware of before. This is still in investigation to find the exact root cause. We continue to see Java heap errors which should be addressed with version v1.7.2 which will be released soon. Because of vacation I won't be very active over the next three weeks, but I'll try to keep up with my duties as good as possible.

/cc https://github.com/bisq-network/compensation/issues/882

ripcurlx commented 3 years ago

Cycle 27 report

We released v1.7.2 which mainly focused to reduce memory consumption and fixes a couple of minor issues that were introduced in the v1.7.0 hardfork. I wasn't very active in this cycle because of vacation.

/cc https://github.com/bisq-network/compensation/issues/904

ripcurlx commented 2 years ago

Cycle 28 report

We released a [v1.7.3] (https://github.com/bisq-network/bisq/releases/tag/v1.7.3) vacation release which mainly contained minor bug fixes and UI improvements. I returned to attend to my duties as maintainer and was mainly focusing on the Tor v3 support issue this cycle.

/cc https://github.com/bisq-network/compensation/issues/904

ripcurlx commented 2 years ago

Cycle 29 report

We released [v1.7.4] (https://github.com/bisq-network/bisq/releases/tag/v1.7.4) containing the Tor v3 support. So far the release went fine and most of the network already upgraded to Tor v3 addresses as well.

/cc https://github.com/bisq-network/compensation/issues/931

ripcurlx commented 2 years ago

Cycle 30 report

We released v1.7.5 introducing 13 new payment methods and moving all remaining nodes to Tor v3 addresses.

/cc https://github.com/bisq-network/compensation/issues/939

ripcurlx commented 2 years ago

Cycle 31 report

We released v1.8.0 introducing BSQ swaps and major DAO parsing improvements. We had to increase the mandatory version to v1.8.0 as a compatibility issue, when trading with an older version with a specific payment method, surfaced. ATM we haven't set any difficulty for BSQ swaps and are also not enforcing new trading fee validations shipped with v1.8.0. This will change within the next couple of days. As part of the Windows release process I also had to renew my code signing certificate over GoGetSSL (€91,71).

/cc https://github.com/bisq-network/compensation/issues/966

ripcurlx commented 2 years ago

Cycle 32 & 33 report

We released v1.8.1 and v1.8.2 improving mediation, extending the API capabilities and fixing lots of smaller issues across the board. I'm a little less active than in previous cycles because of personal reasons, which should change to the better soon again.

/cc https://github.com/bisq-network/compensation/issues/1016

ripcurlx commented 2 years ago

Cycle 34 report

We released v1.8.3 and v1.8.4 improving privacy by automatically deleting past trade data. Besides that lots of small UI improvements and bug fixes.

Improvements

/cc https://github.com/bisq-network/compensation/issues/1041

ripcurlx commented 2 years ago

Cycle 35 report

We didn't release in this cycle as v1.9.0 development took longer than expected.

/cc https://github.com/bisq-network/compensation/issues/1060

ripcurlx commented 2 years ago

Cycle 36 report

We released v1.9.0 (pre-release) and v1.9.1 (public release) introducing the Bisq API and featuring a new navigation structure.

/cc https://github.com/bisq-network/compensation/issues/1088

ripcurlx commented 2 years ago

Cycle 37 report

We released with v1.9.2 a hotfix release based on v1.9.1 including the latest official Tor binary at the time (v0.4.7.7). I blocked one onion address (nlpqkpun5alxgmtfcworaunumrcbpupha6l6perphk45ki7fd736ueyd.onion) and related accounts from trading because of chargeback attempts based on suggestion from @pazza83 and @leo816.

/cc https://github.com/bisq-network/compensation/issues/1088

ripcurlx commented 1 year ago

Cycle 38 report

We released with v1.9.3 a pre-release and v1.9.4 as the public release to improve XMR trading and Tor connectivity.

/cc https://github.com/bisq-network/compensation/issues/1154

ripcurlx commented 1 year ago

Cycle 39 report

We released with v1.9.5 a new P2P status indicator and adding Bitcoin Core v23 compatibility.

/cc https://github.com/bisq-network/compensation/issues/1154

ripcurlx commented 1 year ago

Cycle 40 report

We didn't release a new version last cycle, as we wait for a couple of important changes.

/cc https://github.com/bisq-network/compensation/issues/1154

ripcurlx commented 1 year ago

Cycle 41 report

We released with v1.9.6 updating Tor and removing macOS notarization and Windows code signing.

/cc https://github.com/bisq-network/compensation/issues/1184

ripcurlx commented 1 year ago

Cycle 42 report

Because of major changes in the codebase the v1.9.7 release was delayed.

/cc https://github.com/bisq-network/compensation/issues/1197

ripcurlx commented 1 year ago

Cycle 43 report

We released with the v1.9.7 pre-release and the follow-up public release of v1.9.8 many improvements under the hood to improve resilience of the client and push further the decentralization of Bisq. With this release we also introduced new signers for the public release. Following is the signed public key of @alejandrogarcia83 with my private key.

/cc https://github.com/bisq-network/compensation/issues/1237

ripcurlx commented 1 year ago

Cycle 44 report

The release of v1.9.9 was the first public release of @alejandrogarcia83 🚀 . Congrats! It ships a couple of fixes for v1.9.7 to improve the new decentralization of fee distribution.

/cc https://github.com/bisq-network/compensation/issues/1237

ripcurlx commented 1 year ago

Cycle 45 report

No release took place in the last cycle. I've revoked my maintainer bond now based on the agreement to phase out my maintainer role as @alejandrogarcia83 took over the release duties. Thanks for that! I'll still help out with reviewing and merging every now and then until my availability increases again to contribute more.

/cc https://github.com/bisq-network/compensation/issues/1251

alvasw commented 5 months ago

Hi!

I was the Bisq 2 repository maintainer for the past two years. The previous maintainer gave me maintainer rights before leaving the project, even though I never locked up a bond. Up until last week it didn't matter because Bisq 2 wasn't released yet and there was no risk involved. I think it's time to hand over my maintainer rights to @alejandrogarcia83 (bonded Bisq 2 Release Manager).

@gabernard Please remove me as a maintainer and give @alejandrogarcia83 (bonded Bisq 2 Release Manager) the needed permissions to manage the Bisq 2 repository.

I'll still contribute as usual and review PRs in the future.

bisq-network / roles

Bisq Maintainer #63

Cycle 18 report

Cycle 18 report

Cycle 19 report

Cycle 19 report

Cycle 20 report

Cycle 20 report

Cycle 21 report

Cycle 21 report

Cycle 22 report

Cycle 22 report

Cycle 23 report

Cycle 23 report

Cycle 24 report

Cycle 24 report

Cycle 25 report

Cycle 25 report

Cycle 26 report

Cycle 26 report

Cycle 27 report

Cycle 28 report

Cycle 29 report

Cycle 30 report

Cycle 31 report

Cycle 32 & 33 report

Cycle 34 report

Cycle 35 report

Cycle 36 report

Cycle 37 report

Cycle 38 report

Cycle 39 report

Cycle 40 report

Cycle 41 report

Cycle 42 report

Cycle 43 report

Cycle 44 report

Cycle 45 report