On tir. 9. des. 2014 at 14.27 Rohit Yadav <rohit.ya...@shapeblue.com> wrote:
> Hi, > > CloudMonkey's git repo history is mostly linear and the work on master > is simply getting synced on 5.3 branch. I want to ask the community if > anyone has any objections on just keeping master as the working branch > and have branches when they are needed (say documentation, feature work > etc) and once they are merged they can be removed. We have git tags to > identify past release so is it also alright with everyone to remove the > support branches such as 5.3/5.2 etc. > > This way we will have: > - one main working branch (master) > - branch based workflow: feature branches for doing feature work, pull > requests or reviewboard for bugfixes for non-committers > - master is aimed to remain stable > - master will have its own TravisCI and tests (in upcoming weeks) > - CloudMonkey aims for progressive/rolling releases that are backward > compatible with older releases and have clean upgrades > > For this please vote with your comments/suggestions; > > +1 approve > +0 no opinion > -1 disapprove (and reason why) > > +1, seems like the best thing to do. -- Erik
