There has been some talk on IRC about future release plans, and I thought we should get that discussion started here.
2.3.0 has so far seemed like a pretty solid release, and there is no desperate need for a 2.3.1 yet. Discussions of new features seem to have moved to trunk. How about we try to schedule a 2.3.1 bug-fix-only release for mid-June? Trunk seems rather stable at the moment, and branching it as a possible release point before merging any of the big 3 feature branches may be a good idea. One idea is to branch is to a codename branch, start merging the feature branches, and depending on how stable or unstable trunk becomes after that, either proceed to release from the codename branch, or from trunk after the merges (nuking the codename branch). We have 3 big feature branches that we need to merge before accelerating bitrot makes merging even more difficult. The merge priority that we have discussed earlier for the big 3 feature branches is 1) Qt branch, 2) newnet, and 3) lua. Last comes last because it seems most unfinished yet, and Qt branch first because it has seemed closest to completion and has the most developers familiar with the new code. However, we can easily change the merge order - there are no interdependencies between them. If we proceed to make a release from present trunk, we can probably start the betas for that quite soon and maybe aim for an July/August release. That depends on no last minute large rewrites of anything hitting trunk first. That means: June - 2.3.1 (bug fix only) August - 3.0 (current trunk) December - 4.0 (qt, newnet, lua, new savegame format) Any other ideas? - Per _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
