-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 14.03.2010 23:42, schrieb Nils Kneuper: > Now the same as short and comprehensive list: > * next 24h: tagging of 1.8rc1, announcing about 1 day later > * If things go well: after ~10 to 14 days of testing, tag current trunk as 1.8 > * If things don't work too good, release rc2 with fixes ASAP > * After tagging 1.8 wait 24h for string changes that are required in both, > then > branch trunk off into branches/1.8 > * Announce 1.8 about a week after tagging it (this gives us time to test for > severe problems, the packagers for creating (and testing) the binaries and > translators to give the announcement translation finishing touches)
Okay, I tagged 1.8rc1 on Sunday and announced it on Monday, just like planned. So far it looks like rc1 is reasonable stable. Ilor fixed some crashes that were left in the lobby last night. Basically I have the impression that we don't need another release candidate. Because of this, this is my schedule for tagging 1.8: * Make sure to commit anything you have left for 1.8 till Wednesday, 24th March, 12:00 GMT. * After that point of time I (and everyone of you) will concentrate on testing things to make sure that things behave fine. Please do *NOT* commit any changes to trunk afterwards till I tagged 1.8 unless explicitly talking to me about them in IRC. I plan to tag and package the tarball at 12:00 GMT on Thursday, 25th March. * After I tagged 1.8 I will send a mail to the dev-ml regarding how to continue from here on. In general the plan is to leave trunk open for 24 hours longer for commits that eg change strings but are required in both, trunk and branches/1.8. After this I will branch trunk off into branches/1.8 and trunk is open again for new features (expect this some time on Saturday). * If testing of the tagged 1.8 goes well I plan to announce it on April 1st. This way the packagers got one week to create the binaries and test them. If there is anything that should be taken into consideration, please mail me or ping me in IRC about them ASAP. If you encounter any blocker bug, make sure that it is reported and marked 'blocker'. Cheers, Nils Kneuper aka Ivanovic -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAkuiEHwACgkQfFda9thizwVshQCfd7KkLkn9fnmph1Tf/XcQKePy CQUAn3IiVJDyKbAp/nKLz+JoJxwvkkPi =T06V -----END PGP SIGNATURE----- _______________________________________________ Wesnoth-dev mailing list Wesnoth-dev@gna.org https://mail.gna.org/listinfo/wesnoth-dev
