I disagree. The release process is taking long because we dont have enough people working on the release. Sometimes, even the blockers don't get enough attention. There is no point in adding features on already broken/blocked master which is not releasable. "un-freezing" master for new features shouldn't be the goal in my opinion. We should move towards faster releases/release cycles.
Thanks, ~ Rajani http://cloudplatform.accelerite.com/ On May 8, 2017 at 2:11 PM, Daan Hoogland (daan.hoogl...@shapeblue.com) wrote: LS, In a lot of occasions, we have seen new features that are waiting for releases with blocker bugs and while these bugs certainly must be solved, users that are not hindered by those bugs directly are stopped by them. Therefore, I propose we will fork on the first RC branches for future releases, so that development is not stopped for it. If the release process takes too long and to nice features get merged in between we can always decide to re-branch before releasing. Thoughts..? Daan daan.hoogl...@shapeblue.com www.shapeblue.com ( http://www.shapeblue.com ) 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue