FreeGameDev

Hello all,
As the subject says, we need bug testers. If you can please be testing the latest git pull.
Right now is extremely vital to have bugs sought out, because in 2 short months Milestone 2 will be officially released with nothing holding it back. We do not want to blow a release that has been 10 years in the making. Please do what you can.
Also, if you find a bug and are able to fix it yourself, please do and open a pull request.
As of yesterday we are starting to enter a feature freeze.
Thanks!

-head8debian (Sydney)

I'll put here some bugs from the old bug tracker those I can't reproduce.
Please don't put your bugs to that old bug tracker, but here! >> https://github.com/SuperTux/supertux/issues

So it's here:
http://supertux.lethargik.org/bugs/view.php?id=683
http://supertux.lethargik.org/bugs/view.php?id=894
http://supertux.lethargik.org/bugs/view.php?id=1067
http://supertux.lethargik.org/bugs/view.php?id=397
http://supertux.lethargik.org/bugs/view.php?id=995
http://supertux.lethargik.org/bugs/view.php?id=443
http://supertux.lethargik.org/bugs/view.php?id=622
http://supertux.lethargik.org/bugs/view.php?id=937
http://supertux.lethargik.org/bugs/view.php?id=585
http://supertux.lethargik.org/bugs/view.php?id=680
http://supertux.lethargik.org/bugs/view.php?id=637
http://supertux.lethargik.org/bugs/view.php?id=515
And again, report your bugs to: https://github.com/SuperTux/supertux/issues

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.

Yes, currently we are trying to get all our features that we want implemented in, so we can move on to a *real* feature freeze.

I'd assume we should put the real feature freeze date for in 2 weeks (or so)? Let's get most of the stuff in.