Establish critical bugs board and process about projects HOT 13 CLOSED

Please actually check boxes in the description when you complete them, thanks. It's also OK to re-post them as comments as has been done above here, but the only essential thing is to check the boxes in the description and add a comment saying you've done so. Thanks.

from projects.

• @ripcurlx to go through spreadsheet and add critical bugs to the new board
• @ripcurlx to transcribe any notes and linked issues from the spreadsheet to the actual critical bug

from projects.

• @leo816 to work with @ripcurlx to make sure critical bugs listed in private support spreadsheet are reflected on the new board

from projects.

@ripcurlx, now that the Critical Bugs board is in place and populated, we're getting close to this project being complete. What remains is to document and announce the board and its process. To that end, I've created a stub at https://bisq.wiki/Critical_Bugs. Would you be willing to flesh it out? If so, please create an admin task, assign it to yourself and reference it here, thanks.

You'll see that I've also created stubs for the Dev Team and the larger Development Process of which the Critical Bugs board/process are a part. Wiki links should connect all of them (and mostly already do).

from projects.

• Updated wiki page for critical bugs: https://bisq.wiki/Critical_Bugs

from projects.

• announced critical bugs board in GitHub dev team as discussion: https://github.com/orgs/bisq-network/teams/dev/discussions/2

from projects.

@cbeams Do you want to close this issue after your wiki edits?

from projects.

from projects.

@cbeams Do you want to close this issue after your wiki edits?

yes, will do

Actually, this project shouldn't be considered complete until the board and process are linked to from the places that (especially new) developers would look to as a reference on our development process. I've added checkboxes in the description to this effect. I would be fine if these links are surgically added in a rough / quick way. We should more fully revise and unify the resources mentioned there, but that's a separate effort.

As an aside, this is a good example of end-to-end thinking when it comes to projects / what it means to really deliver something. We created the board, documented the process and announced it to @bisq-network/dev and @bisq-network/support, but without the links mentioned above, it's likely that future developers won't know about the board/process unless someone mentions it to them.

from projects.

• https://bisq.wiki/Development_Process
• https://docs.bisq.network/contributor-checklist.html
  • Create PR: bisq-network/bisq-docs#193
• CONTRIBUTING.md in the main repo
  • Create PR: bisq-network/bisq#3996

from projects.

Ok, I've updated the description to reflect recent proliferation of links to the critical bugs article in all the right places. We're just waiting on the two PRs to be merged, and I think we can consider this project delivered.

from projects.

Ok, I've updated the description to reflect recent proliferation of links to the critical bugs article in all the right places. We're just waiting on the two PRs to be merged, and I think we can consider this project delivered.

Both PRs were merged: Seems to be a very active maintainer 😉

from projects.

I just want to note here that this is our first delivered project under the new proposed project management infrastructure at #1. When we put together the first review meeting, we can go over this as an example.

I've just labeled the project as was:delivered accordingly.

from projects.