You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The worked delivered below is the result of around 230 hours of full-time development work that began at the end of Cycle 7. The large focus was on making the P2P layer more robust (fixing bugs), testable (added ~250 test cases), and making it easier to change in the future (comments, javadocs, cleaner design). It concluded with the v1.2.4 testing the ensured it was stable upon release.
I spent the remaining time split between compensated work (triaging incoming bugs/code reviews) and non-compensated work (keybase questions, new dev onboarding, dev process feedback, writing proposals).
Overall, it has been a positive experience contributing to Bisq and I hope the community agrees that my work has been valuable to the project. Don't hesitate to get in touch if you have questions or comments.
Contributions delivered
Provide links to contributions you have delivered, the amount of BSQ you are requesting for each, and any comments that will help stakeholders understand its value.
As this was the first time through the manual testing release cycle, I was able to identify a few nice-to-haves for future testing, validate known customer pain points, and reproduce some user-submitted bugs so that the fixes could make it into the release.
Development Efforts $25,200
The development work focused on the P2P layer. It started with full unit testing of the P2PDataStorage code that identified numerous edge case bugs and performance issues that were delivered in this cycle. The work was very incremental so it should be easy to parse for anyone interested in how or why I made the changes.
Overall, I am very happy with the end state of the code. I believe that the next dev who needs to work with it can do so in a much safer environment and get better feedback about their changes.
This work involved full testing of the P2P synchronization path (even between multiple instances of P2PDataStorage) that identified multiple bugs and performance issues that were delivered as part of the cycle.
Bug Fixes [$9750]
Full bug dump after my review and testing of P2PDataStorage can be found here. It lays out what I found, which Pull Requests addressed the various issues, and which items are still outstanding.
Unit testing of P2PDataStorage and associated objects that increased code coverage dramatically and added over 250 tests. This was required to ensure the bug fixes had regression tests and that all changes were done safely. All future changes to this code will be much easier due to the additional safety net these tests now provide.
Only includes the initial work to verify it was not a regression and non-critical. All work related to the fix would go into the cycle where the fix was delivered.
Contributions in progress
Provide links to work you're involved with that is still in progress. This section is optional, and is for your own benefit in keeping track of what you're doing and keeping other contributors up to date with the same.
Summary
$27,200
$27,200
/ $0.81 =33580
30e4147c5bb9c8c271fce803ec65cac95d719d6b2eeb11ec79694f9f0a996a7a
The worked delivered below is the result of around 230 hours of full-time development work that began at the end of Cycle 7. The large focus was on making the P2P layer more robust (fixing bugs), testable (added ~250 test cases), and making it easier to change in the future (comments, javadocs, cleaner design). It concluded with the v1.2.4 testing the ensured it was stable upon release.
I spent the remaining time split between compensated work (triaging incoming bugs/code reviews) and non-compensated work (keybase questions, new dev onboarding, dev process feedback, writing proposals).
Overall, it has been a positive experience contributing to Bisq and I hope the community agrees that my work has been valuable to the project. Don't hesitate to get in touch if you have questions or comments.
Contributions delivered
Testing Efforts (v1.2.4)
$2,000
Bugs Filed
TestPad Report
As this was the first time through the manual testing release cycle, I was able to identify a few nice-to-haves for future testing, validate known customer pain points, and reproduce some user-submitted bugs so that the fixes could make it into the release.
Development Efforts
$25,200
The development work focused on the P2P layer. It started with full unit testing of the
P2PDataStorage
code that identified numerous edge case bugs and performance issues that were delivered in this cycle. The work was very incremental so it should be easy to parse for anyone interested in how or why I made the changes.Overall, I am very happy with the end state of the code. I believe that the next dev who needs to work with it can do so in a much safer environment and get better feedback about their changes.
Feature Development [$5000]
This work involved full testing of the P2P synchronization path (even between multiple instances of
P2PDataStorage
) that identified multiple bugs and performance issues that were delivered as part of the cycle.Bug Fixes [$9750]
Full
bug dump
after my review and testing ofP2PDataStorage
can be found here. It lays out what I found, which Pull Requests addressed the various issues, and which items are still outstanding.P2PDataStorage Audit Fixes [$6000]
Incorrect Key Usage Bugs [$3000]
Other Individual Bugs [$750]
Performance Work [$1500]
Code Quality [$8000]
Unit testing of
P2PDataStorage
and associated objects that increased code coverage dramatically and added over 250 tests. This was required to ensure the bug fixes had regression tests and that all changes were done safely. All future changes to this code will be much easier due to the additional safety net these tests now provide.v1.2.3
master 12-11-19
Code Reviews [$600]
Bug Triage [$350]
Contributions in progress
Development Efforts
Feature Development
Roles performed
N/A
The text was updated successfully, but these errors were encountered: