Phil, there is a grey area: proven functionality can be backported to the stable branch once tested on the development branch. There are rules about what can be backported.
Two-per year might seem slow for new-feature releases, but it is much faster than the old ad hoc when-its-ready schedule. The problem with releasing faster is that we only have the resources to support one stable branch. If we have new-feature releases more often, the stable branch will change to quickly to be considered stable. Popular and tested features that do not change the API are often backported to stable. Stable bug-fix releases often contain new features. On 25/01/13 03:41, Phil Scadden wrote: > Perhaps I should get some clarification on what is meant by "release"? > What I would like to see is fairly frequent bug-fix releases but perhaps > more delayed "new feature" releases. 2 a year seems a little infrequent > to me. I could us using nightly builds with all the possible issues, > simply because we desperately want a feature and we arent prepared to > wait 4-5 months for it. -- Ben Caradoc-Davies <[email protected]> Software Engineer CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
