-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody! Since there were not too many replies to my last mail (Subject: "The last release in the 1.6.x series... (plus future plans!)") and it looks like there is not too much on your list of open items, here are the plans:
Mordante wrote that he has some open items, most important is clearly the fix of the "resize crash". A clean fix for this one will require some more work and at least take three weeks to implement (plus some testing is required afterwards). He listed his other open items in the wiki at [1]. Beside the mail from mordante there was no real feedback so I assume that you are rather satisfied regarding features and all the likes. That is why I think it is reasonable to start the feature freeze preparing for 1.8 on Sunday next week (so that you have on week left to work on the features you want to get in). Together with the feature freeze the string freeze will start. I already warned about the "soon" start of it several times on #wesnoth-dev, so it should not hit you unprepared. So, what does this mean regarding the release of 1.8? 1) The string- and feature-freeze starts on Sunday, 27th September 15:00 GMT+2. At that time I will try to package 1.7.6 which will basically be the first 1.8 beta (since it should be feature complete ;) ). From now on you should just work on fixing bugs! 2) Every two weeks a new version. Once mordante is ready with his resize fix those will most likely be release candidates. 3) At least four weeks after 1.7.6 (more likely 6 weeks) 1.8 should be ready. This is the case if/when things are stable and the amount of known bugs down to some "reasonable value" (no fixed numbers, more like a feeling...) So if you have *any* reason why I should not stick to this plan for the release of 1.8, please ping me ASAP. Before you ask what else is required before we can get 1.8 out of the door, here are some things: * Polish existing features so that they work without too many problems. * Make sure that the new mp lobby ilor worked on as part of SoC on can be used and is activated by default. * Fix as many bugs as possible. * Write some nice release announcement (like the ones we had for all the other stable releases). * Create screenshots featuring the new stuff (eg Drakes, portraits and new terrains). * Help the translation teams [2] finish and polish the respective translations if you can (as in know the respective language and have enough time). I already updated the textdomain status page [3] marking almost everything as ready, since almost nobody indicated that anything would still be open... Cheers, Nils Kneuper aka Ivanovic [1] http://www.wesnoth.org/wiki/Wesnoth1.8Features [2] http://www.wesnoth.org/wiki/WesnothTranslations [3] http://www.wesnoth.org/wiki/TextdomainStatus -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAkq2Ds4ACgkQfFda9thizwUgAgCaAp11kYAWMCbmB9/16/v835rr e8kAn1sZcF4mBLS05QkQU9W6iq3zg82z =Bya+ -----END PGP SIGNATURE----- _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
