-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody! I already asked you once to enter your planned work in the wiki at a specific page ([1]). At least some of you have done so. Based on this and the recent fixes of "really problematic bugs" (like the AI problem) I think we are really getting closer to the next stable series. To allow translators to catch up the campaigns are already under a soft stringfreeze. This means that only spelling and grammar fixes are allowed. The list regarding the current status of content is in the wiki [2]. Since the game is not only about the campaigns itself but also about the interface and all this stuff, it would be nice to phase out the new and changed strings rather soon so that translators can easily tackle this area, too. So I basically suggest that there are about two more weeks for excessive changes to strings and such and then we slowly reach the state of a soft string and feature freeze where can can completely concentrate on getting rid of the bugs left. For Christmas I would love to finally enter the hard stringfreeze, so that we can get out 1.6 maybe at the end of January. So to list the basic stuff in a comprehensive way the stuff that should happen now including some dates (I will also list this stuff (and try to keep it up to date) in the wiki at [3]):
Campaigns: * no more changes to strings (unless typo/grammar/bug-fixes) * getting them to a stable state and reducing the amount of huge wml changes (huge WML feature changes only till 14th December, afterwards just bugfixes) * balancing so that they are well balanced in 1.6 Documentation (eg manual): * getting it in sync with current game ASAP * make sure that the ingame help is in sync with the game WML (multiplayer maps/scenarios/...) * make sure that all (new) maps/scenarios are in until 7th December * balancing (for units (if possible) only till starting the RC series mid January) Code: * code changes that require strings to change only for the next two weeks (till 7th December, introduce dummystrings if you need the strings for a feature that you *will* complete before the freeze!) * getting the last features wanted in (in a working and not too buggy way!) till 14th December * after 14th December: feature freeze (bugfixes only ;) ) Other: * get in everything that requires changes/new strings till 7th December * wipe out bugs or at least report them when you encounter them Short version of the timeline: * 7th December: start of the soft stringfreeze for *everything* * 14th December: start of the feature freeze (everywhere, campaigns, scenarios, maps, code; from now on just bugfixes and balancing changes as well as "cleanup") * around Christmas: hard stringfreeze for basically everything * beginning/middle of January: first RC * beginning/middle of Febuary (maybe at FOSDEM?): release of 1.6 In parallel to this stuff, the release announcement for 1.6 has to be written. It would be great to have it ready together with the first RC of 1.6. Regarding the style it can be comparable to the one for 1.4 which is available at [4]. Of course we will also need *lots* of good screenshots. Other comments regarding the timeline/schedule for 1.6? Have I forgotten anything important? Are there reasons why the schedule should somehow be changed/altered? If yes, please answer this mail! Cheers, Nils Kneuper aka Ivanovic [1]http://www.wesnoth.org/wiki/Wesnoth1.6Features [2]http://www.wesnoth.org/wiki/TextdomainStatus [3]http://www.wesnoth.org/wiki/Wesnoth1.6ReleasePlan [4]http://www.wesnoth.org/start/1.4/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkpT8UACgkQfFda9thizwW0jgCdG6PFakRgZG2P+BP6qhFX99Pb uFMAn3r1aqQtJ4D+cdjbWS8OiBkj65/h =zICQ -----END PGP SIGNATURE----- _______________________________________________ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
