Hi all, especially @tschumilas, @Kirsten, @Theodore, @rachel, @lin_d_hop, @sauloperez, and @lauriewayne1.
We’ve come up with a way to better allow for fair selection of which severity 3 bugs we put through the delivery pipe.
The process we shall trial
Similar to the process we’ll use for Papercuts, we’ll work in cycles of 6-7 weeks where each active instance will select their most painful S3 bug to be fixed. And we’ll then repeat the cycle, so each 6-7 weeks you’ll be asked to selected your next most painful S3, and so on, and so on, and so on. Simple!
How to select your priority bug
!! Before you do this step, you need to have the Zenhub extension set up in your browser (Firefox and Chrome only). If you haven’t got this set up and need help, yell out on Slack and someone can help you easily enough.
Go to the list of S3 bugs in GitHub
Peruse the list, and find the bug that you want to select as your instance’s priority to be fixed. You may already know which one you want to choose. Good for you! Otherwise, work through the list and find the one that is the most annoying for your instance.
Open the bug issue.
Look on the right hand side of the issue, you’ll see a whole lot of metadata about the bug. Specifically, click on the “Labels” option.
Find your instance label (AU, BE, CA, FR, KAT, UK, US) and add it to the labels list.
Then look above the label option, click on the Pipelines option.
Find the S3 bugs prioritised pipeline option and select it.
Then scroll all the way to the bottom of the issue and add a comment about it being the priority for your instance in the next cycle of fixes.
.
And that’s it. You’re done. I’ll then collate all the prioritised bugs into the delivery pipe and make sure they’re fixed.
I’ll also have a prompt service set up so that you know when to do your next cycle selection. And you’re welcome to make the decision amongst your instance folk or however you’d like, just make sure once you’ve decided on one you follow the process above to make it official.
-The End-
