Hi everyone.
As part of the work we are doing to reduce and organize the issue backlog we have thought about a potential split of the open issues into buckets and a proposed plan to work on these buckets.
Looking at the remaining issues we propose to split them as follows:
Our proposed approach is as following:
- Every week we will focus as a community on one of the buckets and will also use the bi-monthly backlog review meetings to help focus
- For each issue reviewed the reviewer should check if that issue can be closed (duplicate, not relevant, etc...) or is a valid issue
- If you believe this is a valid issue remove the "needs-review" label to indicate the issue has been triaged (or ping James/me to to do it)
- Later on once we have finished with reviewing the issue backlog we can then move on to decide on adding new labels (such as MVP) and removing/joining old labels
Propose timeframe:
- 2nd week of August - issues opened this year which are not bugs and are labeled kata-2.0-features (45 open issues)
- 3rd week of August - issues opened this year which are bugs (112 open issues)
- 4th week of August - issues opened this year which are not bugs and are not labeled kata-2.0-features (129 open issues)
- 1st week of September - starting to work on issues from previous years depending on our progress
Let us know if this plan makes sense, if you have comments or other suggestions.
Thanks.