I am trying to make the animation syntax evolve some more... this involves some complicated upgrades of WML, which in trun might require a couple of releases to avoid pushing too much changes in one go to the user...
so a 2/3 week release frequency means 4-6 releases until feature freeze... this is probably enough for me but might be a little short. Ivanovic/Isaac, would it be possible to check with me before releases if I have pushed a "step" of my changes before each release ? this would make sure I don't accidentally miss a release, which might push me out of schedule... Thx Boucman On 9/27/07, Mark de Wever <[EMAIL PROTECTED]> wrote: > > On Tue, Sep 25, 2007 at 04:55:49PM +0200, Nils Kneuper wrote: > > -----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. > > I think aiming for a release in the first half of 2008 would be nice, I > consider the following items a must have. > > * Addon server rewritten (I'll start on that soon). > * MP random working (Baufo was/is working on that). > * MP campaigns working (Rhuvaen posted quite some bugs regarding the > problems). > * Allow custom terrains in the editor (I think a must have since also > some mainline campaigns use custom terrains, at least UtbS does.) > > I hope we manage to get the bug count down before 1.4. I know a lot more > features which would be nice, but don't think they're really critical. > > Regards, > > Mark de Wever aka Mordante/SkeletonCrew > > _______________________________________________ > Wesnoth-dev mailing list > [email protected] > https://mail.gna.org/listinfo/wesnoth-dev >
_______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
