Serendipity Forums

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

Sure, why not

+1

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