It is getting very close to the release of 2.3, so I figure we should sort a few things out before we hit the launch button.
Trac tickets basically boil down into tickets that are: a) useless. (can't replicate, no good info in said ticket) b) general corruption. (can't replicate) c) other corruption (can't replicate) d) we know about it, but no fix yet. It really doesn't do us any good to keep a,b & c tickets open. I recommend we set all those to pending information (ie, a way to replicate). On the release of 2.3, I recommend we have a transition period for the lobby server that will tell 2.2.x clients to upgrade to 2.3 ASAP, then after 2-3 weeks or so, we just echo the message of 'Update to 2.3' and close the connection. This will help our online community get much bigger, and not splinter them with different versions floating around. On Qt, everyone should basically try and help out to get this branch working correctly on all platforms, in preparation for the merge to trunk. At that point, I feel a branch to 2.5 (or whatever is in order) to get testing done ASAP. Once this has completed, then we can work on newnet, and fix the issues it has on windows machines, and of course, we also have the lua branch which is roughly 55-65% completed. If at all possible, we should try to not have any new features in the beta releases, and leave them as bug fixes only, and do a 'release early, release often' policy. _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
