-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hiho everybody! I wanted to raise this topic to get some feedback about how we should handle the eventual release of 1.4. Basically this mail is about how much time you still need to get features in that you want to see in 1.4.0.
I would like to start a feature freeze around christmas. A feature freeze means that no more new features may be added to trunk until we branch 1.4 off. At the same time I would also like to start a light string freeze and get out the first beta release (not rc). Light string freeze means: basically all strings are frozen. Only spelling and grammar mistakes are to be fixed, no more new content. About one month later a "hard string freeze" should start that is hold until 1.4 gets released. "Hard string freeze" means that absolutely no strings get changed. I want to start releasing RC versions by the middle of febuary, shortly after the hard string freeze is active. I would like to finally release 1.4 in the middle of march, about 10 weeks after the start of the feature freeze. Those 10 weeks should be used for killing as many bugs in Wesnoth as possible. I want to stick to the "a release every three to four weeks"-policy for the whole time. Any objections against this? Anyone of you definatly needing more time for a "must have in 1.4"-feature? Of course there are no fixed dates so far and the "around christmas" ain't fixed either. But it is meant as a general goal to tackle. Things that definatly should be done until the feature freeze starts: Sort out if we want to ship all campaigns available in trunk within the 1.4 release. Be should remove all campaigns we don't want to have in 1.4 before entering the feature freeze. The feature freeze does also mean that no new campaigns/maps/whatever get added. That time is meant to tackle bugs and improve balancing. The "API" itself should be rather stable that time so that no major WML changes take place either. Feel free to comment in here and on IRC. Cheers, Nils Kneuper aka Ivanovic -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+SF1fFda9thizwURAgnjAJ9DRpMxz/nDx79ii4fCO/OyCPGDMACePXJt xRvMNZcxWz7q20VO4xF2pXc= =tnJo -----END PGP SIGNATURE----- _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
