-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bisq Maintainer #63
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
2018.05 reportReviewing and merging of PRs and release preparations for v0.7.0 |
2018.06 reportReviewing and merging of PRs and release preparations for v0.7.1 |
2018.06 reportNothing to report. Note that I plan to remove myself from the set of desktop maintainers. |
@ripcurlx wrote
I think it's important that we account separately for maintainer work and PR review work. I've written about this in the WIP Roles doc, see https://deploy-preview-46--bisq-docs.netlify.com/roles.html#maintainer. I'm +1'ing your compensation request as-is, but something to keep in mind as you review that doc. |
I've updated the @bisq-network/desktop-maintainers team and the description of this issue to reflect that @ManfredKarrer and @ripcurlx are Bisq Desktop maintainers now, and that I've removed myself. |
@cbeams Regarding PR reviewer work. Should this be part of the general |
Cycle 30 reportWe released v1.7.5 introducing 13 new payment methods and moving all remaining nodes to Tor v3 addresses. |
Cycle 31 reportWe 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). |
Cycle 35 reportWe didn't release in this cycle as v1.9.0 development took longer than expected. |
Cycle 37 reportWe 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. |
Cycle 39 reportWe released with v1.9.5 a new P2P status indicator and adding Bitcoin Core v23 compatibility. |
Cycle 40 reportWe didn't release a new version last cycle, as we wait for a couple of important changes. |
Cycle 41 reportWe released with v1.9.6 updating Tor and removing macOS notarization and Windows code signing. |
Cycle 42 reportBecause of major changes in the codebase the v1.9.7 release was delayed. |
Cycle 43 reportWe 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.
|
Cycle 44 reportThe 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. |
Cycle 45 reportNo 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. |
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. |
I'm unlocking my bond for this role since I'm no longer active. |
Docs: https://bisq.wiki/Bisq_Maintainer
Team: @bisq-network/bisq-maintainers
The text was updated successfully, but these errors were encountered: