On Wed, Feb 27, 2013 at 12:47:43PM -0500, David Nalley wrote: > Hi folks, > With 4.0.2 being actively worked on in parallel with 4.1 - we need to > have some discussions around setting expectations for support > lifecycle of a given release. > Our feature releases are relatively rapid (~every 4 months). At the > same time, people deploying CloudStack like stability. Our bugfix > releases provide 'stability' with a minimal level of change, but there > is also a lot of overhead for managing a release, getting bugfixes > done, etc. And while we only have a single bugfix running currently - > by the time we get to 4.2.1, it's entirely possible that we'd have 3 > bugfix releases running simultaneously. > > > So - discuss and lets come to a decision. > > --David >
I stated my opinion on this previously [1], but for the record again: I would suggest that we only do bug-fix releases for: - The latest feature release of our active major version number (i.e.: 4.x) - The latest feature release of our last major version number (doesn't exist today, but will be 4.x when / if we bump to 5.0) Just my opinion though. Others? [1] http://markmail.org/message/quzgjne44prl5m2c
