On Tue, Sep 02, 2014 at 10:03:51PM +0930, Michael T. Pope wrote: > On Mon, 1 Sep 2014 22:21:05 +0300 > Niklas Laxström <niklas.laxst...@gmail.com> wrote: > > There is no hard coded limit. My recommendation is to aim for two > > releases per year. > > Alas, just one in 2014 would be nice. > > > Perhaps you can consider doing a maintenance > > release with only translation updates and essential bug fixes. > > Some major internal changes have occurred. I doubt we can go > backwards without even more effort.
You should be able to create a stable branch at the point where 0.11.0 was tagged (or the commit corresponding to the release), and then let translators land translations there. I don't remember if you're using svn or git, but 'git cherrypick' is really nice for pulling fixes from trunk to the stable branch. This would give you relief if you find yourself in a similar situation where devel changes have caused too much instability to justify releases; you've given yourself the flexibility to instead do little stable releases to keep the project "alive" while trunk continues with development. (This is exactly the situation we were in with Inkscape for the past 4 years, as we replaced the internal renderer and thus incurred tons of regressions; we kept Inkscape alive via five point releases on the 0.48 series while we focused on stabilizing the new renderer on trunk.) Maintaining a stable branch may seem like taking on extra chores, and it is, however this is a perfect kind of discrete responsibility to hand off to a trusted lieutenant: Doesn't require a huge amount of time, mostly just being conservative with a careful attention to detail. Bryce ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Freecol-developers mailing list Freecol-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freecol-developers
