Page 1 of 1

GitHub milestones post 2.0

Posted: Thu Jan 22, 2015 8:02 pm
by yellowled
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

Re: GitHub milestones post 2.0

Posted: Thu Jan 22, 2015 9:11 pm
by garvinhicking
This is funny. I was just thinking the same. Since I wanted to go through each open issue now, I'll assign those milestones. If someone disagrees we can still change them. :)

Re: GitHub milestones post 2.0

Posted: Thu Jan 22, 2015 9:28 pm
by yellowled
Pleasure doing magic with you. :mrgreen:

https://github.com/s9y/Serendipity/milestones is done. Everyone, if you find the time, please go over the issues and revise what you think should be assigned to different milestones (or people or whatever).

YL

Re: GitHub milestones post 2.0

Posted: Thu Jan 22, 2015 9:44 pm
by garvinhicking
Great. I assigned a couple of things to me that I should be able to work in in the near future. I also made some changes in milestone assignments to 1 or 2 issues.