[2.0] Add milestones in GitHub

Discussion corner for Developers of Serendipity.
Post Reply
User avatar
yellowled
Regular
Posts: 7072
Joined: Fri Jan 13, 2006 12:46 pm
Location: Eutin, Germany
Contact:

[2.0] Add milestones in GitHub

Post by yellowled » Thu Mar 06, 2014 1:41 pm

GitHub offers the possibility to add milestones to issues. Since we're now entering the development phase where 2.0 could become beta and later RC, we might want to use that to indicate which phase an issue is relevant for.

For 2.0 (or even for further releases), I'd like to suggest

* Beta: should be implemented/fixed before beta phase
* RC: should be implemented/fixed before (any) release candidate
* Stable: should be implemented/fixed before actual release

These are not meant to set deadlines (we can actually add due dates to milestones, but we don't have to), just to make it easier to find issues which block any kind of development status. If you guys think this isn't worth the effort, we don't have to use it. :)

Thoughts?

YL
amazon Wishlist - Serendipity-Podcast (German only, sorry)

User avatar
garvinhicking
Core Developer
Posts: 30020
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

Re: [2.0] Add milestones in GitHub

Post by garvinhicking » Thu Mar 06, 2014 5:01 pm

Sure, why not :)
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/

User avatar
onli
Regular
Posts: 2254
Joined: Tue Sep 09, 2008 10:04 pm
Contact:

Re: [2.0] Add milestones in GitHub

Post by onli » Thu Mar 06, 2014 6:05 pm

+1

User avatar
yellowled
Regular
Posts: 7072
Joined: Fri Jan 13, 2006 12:46 pm
Location: Eutin, Germany
Contact:

Re: [2.0] Add milestones in GitHub

Post by yellowled » Thu Mar 06, 2014 7:28 pm

https://github.com/s9y/Serendipity/issues/milestones

I tried my best to decide which issue to assign to which milestone, but feel free to move them around if there's a good reason why something is relevant for an earlier or later phase. Also, please make sure to assign milestones to new issues relevant for any of the three phases, this doesn't make much sense if we don't do that.

If an issue is not relevant to any of the three phases, we probably should just not assign it to any milestone. (I was thinking about adding a fourth milestone “Nice to have”, but I guess that would be overly complicated.)

YL
amazon Wishlist - Serendipity-Podcast (German only, sorry)

Post Reply