On Tue, Aug 5, 2014 at 7:44 PM, Erik Weber <terbol...@gmail.com> wrote:
> On Wed, Aug 6, 2014 at 12:55 AM, Prachi Damle <prachi.da...@citrix.com> > wrote: > > > I fail to understand how will this model help us with the maintenance > > releases? > > > > > That's what gitflow support branches is for. > I find this quite descriptive: > > https://groups.google.com/forum/#!msg/gitflow-users/I9sErOSzYzE/AwVH06CuKT0J > > > > > For CloudStack we also keep working on prior releases and ship out > > maintenance releases. > > I suppose we will be cutting the maintenance releases from the release > > branches? So we will have to keep around the release branches for that > > purpose. > > > > > I've asked earlier, but what is the policy on old releases? How long do we > support them? > > Today (e.g. subject to change) we claim to support as a community the two most recent feature releases. (for instance, we just stopped support the 4.2.x line with the release of 4.4.0, and currently support 4.3.x and 4.4.x) We support those feature releases with bug fix releases that contain no additional functionality. --David
