If I might make a suggestion for the versioning for the next stable release: could it finally be called Wesnoth 2.0? We've gone on with 1.x.x for awhile now with no sign of stopping, which really gives the impression that not much is being changed.
I believe it's a good time as ever to switch version numbers - the UI has been/is being greatly revamped recently. Plus taking into account all the changes made during the 1.9 development cycle, and how greatly the game has improved since 1.0, I really think a change to 2.0 would be optimal. There are two possible routes to go: * Proceed with the 1.11.x development cycle, up to the rc releases, at which point the number would be bumped to 2.0. After that, the current system of even-stable, odd-dev releases could be kept through 2.1.x, 2.2.x, etc. * Proceed with the 1.11.x development cycle, up to the rc releases, at which point the number would be bumped to 2.0. After that, 2.x releases would be all subsequent stable releases, and 3.x created when the time comes to create a new dev series. On Sun, Nov 10, 2013 at 9:17 PM, Lipka Boldizsár <[email protected]> wrote: > As for me, I have the MP interface to polish out before the next stable > release. Right now it's good enough to go into a dev release (hence I'm > alright with 1.11.7 next Saturday), but it has some deficiencies that ought > to be fixed before the freeze. I hope to get it done in the next month. > However, in an extreme case, the December 21. deadline might be 1-2 weeks > too tight for me. > > ---- On Sun, 10 Nov 2013 11:31:20 +0200 *Nils Kneuper > <[email protected] <[email protected]>>* wrote ---- > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi folks! > Today shadowmaster raised the topic of the next dev release and the start > of > the preps for 1.12. First question: > > * Does releasing 1.11.7 next Saturday work for you? Are there any blockers > or > things you really need to have in it? > > The more important question though is when to work on the next stable > series. > The last stable series is now getting close to 2 years old. He mentioned > that > having 1.11.8 as start of a feature freeze would make sense to him. My > question to you folks is if this will also work for you. This is what I > would > propose as timeline for the 1.12 series: > > * Start of feature (and string!) freeze with 1.11.8 shortly before > Christmas > (December 21st?) > * Stabilization phase for ~2 month (with a release every ~3 weeks) > * Start of RC time mid February (hopefully only 1 RC), might be a possible > time for branching off the new stable branch > * Release of 1.12.0 around March 1st 2014 > > What do you think of a plan like this? Will this work for you? I supposed > less > than 2 month for the string and feature freeze time won't work otherwise > the > translators have no chance to play catch up. What should also be > considered in > the timeline is if we want to participate in GSoC and have students work > directly master. Another option would be not to release a stable series > this > year, but I think then it would be *extremely* long since the last one. > > Please post your comments here on the ML so that everyone can participate > in > the discussion. > > Cheers, > Nils Kneuper aka Ivanovic > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > > iEYEARECAAYFAlJ/UmgACgkQfFda9thizwV++ACgghR98Iot6a3R89CSMa6eR/4Y > 2a8An3eB6setjEJ+WUU3bw6Wq6/vQb+c > =YYB3 > -----END PGP SIGNATURE----- > > _______________________________________________ > 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 > >
_______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
