On Jul 30, 2014, at 5:13 PM, David Nalley <da...@gnsa.us> wrote: > On Wed, Jul 30, 2014 at 4:26 PM, Daan Hoogland <daan.hoogl...@gmail.com> > wrote: > >> On Wed, Jul 30, 2014 at 10:15 PM, Sebastien Goasguen <run...@gmail.com> >> wrote: >>> and merge it in other needed branches (master and develop) >> >> >> that part will be hard as it will merge all commits (also hotfixes and >> others) that aren't on the the ancestry of the branch to merge into. >> So this is only possible if the 4.4 branch is relatively clean. >> >> >> > Agreed - in many respects the rate of change almost dictates that we'll end > up with multiple release branches. I worry it's a bit naive to think that > something as complicated and large as CloudStack, and moving at the > velocity we do, will end up with only one set of 'master and develop' >
I don't think cloudstack is that special. But let's wait to see a proposal to all have a common understanding of how this would work. Right now we have several threads on the same subject. > --David
