GitHub milestones post 2.0
Posted: Thu Jan 22, 2015 8:02 pm
As the Stable milestone is now 100% done, I was just wondering if we should re-organize GitHub milestones.
We're most likely going to close the Stable milestone soon, but Future might not be granular enough. Maybe we should distribute the issues assigned to Future to new milestones, for example:
* 2.0.x (meaning: this issue should be addressed for the next patch release – so asap)
* 2.x.0 (meaning: this issue should be addressed for the next minor release – so not urgent)
* x.0.0 (meaning: this issue should be addressed for the next major release – so take your time)
We could also keep Stable and Future, but that will get confusing as closed issues pile up. I think I'd prefer to have this neatly organized so everyone can always see what's left to do for which release?
YL
We're most likely going to close the Stable milestone soon, but Future might not be granular enough. Maybe we should distribute the issues assigned to Future to new milestones, for example:
* 2.0.x (meaning: this issue should be addressed for the next patch release – so asap)
* 2.x.0 (meaning: this issue should be addressed for the next minor release – so not urgent)
* x.0.0 (meaning: this issue should be addressed for the next major release – so take your time)
We could also keep Stable and Future, but that will get confusing as closed issues pile up. I think I'd prefer to have this neatly organized so everyone can always see what's left to do for which release?
YL