Difference between revisions of "Wesnoth1.6ReleasePlan"

Latest revision as of 13:46, 21 February 2009

Outline for Wesnoth 1.6 release schedule

21 February - today
22 February - tagging 1.6 beta3
1 March - tagging 1.6 rc1
8 March - tagging 1.6 rc2
15 March - if everything is fine, tag 1.6
several days later - announce 1.6 and celebrate

The schedule in detail

Today

The first two beta releases for 1.6 are out and everything is under string and feature freeze. Currently it is time for bug hunting.

22 February

If the state of trunk allows 1.6 beta3 should be tagged/released. That is if the two reported bugs marked as "security issue" are fixed.

1 March

About a week after 1_6beta3 assuming that everything is fine, the first rc for 1.6 will be tagged and announced.

It should basically be working nicely, but needs some *real* testing. From this release on there should be no more changes that break compatibility between releases (eg unit balancing and stuff like this) so that the RC versions and the final stable line are compatible on the MP server.

Beside this the release announcement for 1.6 has to be written. It can maybe be modeled after the 1.4 announcement which was really well done. And we need lots of screenshots to be created so that we got something to show off together with the new stable release.

8 March

A week after rc1 get another release candidate out to have the latest changes and fixes tested a little more.

15 March

Tagging 1.6 and branching it into branches/1.6 once we are sure that the quality level we want to achieve is met. Packagers and translators should have "several days" (at least three or four) to finalize the announcement and all devs should give the release tarball some extra testing to make sure that everything works basically as expected.

Three or four days later

Big announcement of 1.6/party in IRC/holidays/whatever.

All time in between

Work on the bugs and test as much as possible to find the bad bugs. If you find any that should be blockers for 1.6, list them here.

Collect spelling mistakes in the wiki, so that we can fix them in a big batch, which is a little easier for translators (especially since esr created pofix.py).

@@ Line 1: / Line 1: @@
 == Outline for Wesnoth 1.6 release schedule ==
-* 23 November - today
+* 21 February - today
-* 7 December - soft string freeze for everything
+* 22 February - tagging 1.6 beta3
-* 14 December - feature freeze
+* 1 March - tagging 1.6 rc1
-* Christmas - hard string freeze for everything
+* 8 March - tagging 1.6 rc2
-* beginning/middle of January - first RC of 1.6
+* 15 March - if everything is fine, tag 1.6
-* middle of Febuary (around FOSDEM 09) - release of 1.6
+* several days later - announce 1.6 and celebrate
-* in between - a development/beta release every two to three weeks
 == The schedule in detail ==
 === Today ===
-All campaigns, the tutorial and -units under a soft string freeze. This means in those areas only spelling-, grammar- and bug-fixes should happen.
+The first two beta releases for 1.6 are out and everything is under string and feature freeze. Currently it is time for bug hunting.
-=== December 7th ===
+=== 22 February ===
-Start of the soft string freeze for everything that is not yet frozen.
+If the state of trunk allows 1.6 beta3 should be tagged/released. That is if the two reported bugs marked as "security issue" are fixed.
-=== From 23 November to 14 December ===
+=== 1 March ===
-Implement your [[Wesnoth1.6Features|features you would like to get in 1.6]] and enter which bugs you want to / plan to fix. If you want a delay on the freeze, tell it Ivanovic. Make sure that the strings you need are already in by December, 7th. After the start of this feature freeze no new features should be added no matter if c++ code or WML.Every change from now on should be "bugfix and balancing only".
+About a week after 1_6beta3 assuming that everything is fine, the first rc for 1.6 will be tagged and announced.
-Keep in mind that all features added late in the process should be basically working in a nice way, that is no "dummy features" where the pseudo feature is said to be there but it is "just broken". If you need an extension of the time till the feature freeze, explicitly ask Ivanovic for it!
-=== around Christmas ===
-Merge of the [http://www.wesnoth.org/wiki/SpellingMistakes spelling and grammar mistakes] into trunk and start of the hard string freeze. No more string changes from now on.
-=== beginning/middle of January ===
-Release of the first release candidate for 1.6.
 It should basically be working nicely, but needs some *real* testing. From this release on there should be no more changes that break compatibility between releases (eg unit balancing and stuff like this) so that the RC versions and the final stable line are compatible on the MP server.
@@ Line 30: / Line 21: @@
 Beside this the release announcement for 1.6 has to be written. It can maybe be modeled after the [http://www.wesnoth.org/start/1.4/ 1.4 announcement] which was really well done. And we need lots of screenshots to be created so that we got something to show off together with the new stable release.
-=== beginning/middle of Febuary ===
+=== 8 March ===
-Tagging 1.6 and branching it into branches/1.6 once we are sure that the quality level we want to achieve is met. This is not before FOSDEM 09 and at least four weeks after the release of the first RC so that there is enough time for it to be really well tested.
+A week after rc1 get another release candidate out to have the latest changes and fixes tested a little more.
+=== 15 March ===
+Tagging 1.6 and branching it into branches/1.6 once we are sure that the quality level we want to achieve is met. Packagers and translators should have "several days" (at least three or four) to finalize the announcement and all devs should give the release tarball some extra testing to make sure that everything works basically as expected.
 === Three or four days later ===
@@ Line 39: / Line 33: @@
 Work on the bugs and test as much as possible to find the bad bugs. If you find any that should be blockers for 1.6, list them [http://www.wesnoth.org/wiki/Wesnoth1.6Features#BUGS_.2F_features_that_must_be_addressed here].
-Collect spelling mistakes [http://www.wesnoth.org/wiki/SpellingMistakes in the wiki], so that we can fix them in a big batch, which is a little easier for translators. A development/beta release  will have to be released every two to three weeks.
+Collect spelling mistakes [http://www.wesnoth.org/wiki/SpellingMistakes in the wiki], so that we can fix them in a big batch, which is a little easier for translators (especially since esr created pofix.py).
 ==See also==
 [[Wesnoth1.6Features| Plans and blockers for 1.6]]
@@ Line 49: / Line 42: @@
 [http://bugs.wesnoth.org bugs.wesnoth.org] - List of known and reported bugs
-[[Fosdem2009|FOSDEM 09]]
 [[Category:Development]]