by Datahead8888 » 27 Oct 2015, 13:25
In order for a feature freeze as Sydney pointed out above to work, I see two things needing to happen:
* Someone with write access to the Super Tux repo in github has to create the new branches. One branch has to exist for the Milestone 2 release, which then no longer takes new features, and another has to exist for further features (Milestone 3). Master can be one of these two branches if you want, but people will probably keep putting features in master if no other branch exists.
* A clearer announcement has to be made. A forum post with its own title "Feature Freeze" should be in the forum. It also might be good to set the announcement in IRC. This bug testing forum post is very good, but the feature freeze could still be overlooked.
The feature freeze will allow Milestone 2 to stabilize; each new feature added has a risk of serious bugs that could even crash the game in the release. You'd also need to decide how much bug fixing time is needed. I'd at least allow a month, quite likely more.
Again, it's up to to the Super Tux team as to how you handle this, but this is what's needed to make the feature freeze take effect.