We’ve come to believe that a good systems workflow has to be totally clear for everyone. Looking at how our github issues and process have matured over the years, it is time for a cleanup. 

 

 

Many of our labels were not being consistently used. Many were entirely subjective, and some were vague in ways that implied we might be committing to something we weren’t. 

We’re going to be using github’s Kanban board to do more release management moving forward. Our goal with labels is to create a standardized system anyone can agree on. In the big picture we should be able to hand this list to a junior dev and have them classify new issues properly. Each label should describe a clear undisputable set of truths about the issue. It is then up to the individual using these labels to search to determine what is a high priority to themselves. 

 

• Type - Choose only one...

  • Bug - Existing functionality not performing as expected.

  • Enhancement - A need for something new. 

  • Test - This is a test we’d run against the core. 

 

• Status - Choose only one, moves forward with issue’s lifecycle...

  • Proposal - This needs discussion before anyone should start coding.

  • Available - Reviewed issue, it’s real, we’d review a pull request. 

  • In-Progress - Someone is actively working on this now.

  • Blocked - This can’t move forward until something else happens. Should include a link to the blocking issue.

  • On-Hold - For one reason or another, all work on this should stop. 

  • Abandoned - Progress here has stopped for reasons we don’t understand.

  • Ready for Review - This is ready for PL to review.

 

• Bug Priority - Choose only one...

  • Low - This would be a nice fix, but it mildly improves things that already work.

  • Medium - There’s a viable work around, but this would make it much better. 

  • High - Very broken, and no work around. 

 

• Product Areas - Pick many...

  • Dashboard

  • Internationalization

  • Multi-Site

  • Blocks

  • File manager

  • Express

  • Sitemap

  • Performance

  • Code Quality

  • Attributes

  • Api

  • Database

  • Calendar

  • Conversations

  • Framework

  • Accessibility

  • Build Process

  • Distribution

  • Server compatibility

 

• Effects - Pick many...

  • Content Creators

  • Developers

  • Site Visitors

 

• Good First Issue