+1 On Sunday, August 2, 2015, Daan Hoogland <daan.hoogl...@gmail.com> wrote:
> As we are changing our review process I want to clean up the > repository at apache getting rid of stale branches. Of course the > release branches of old releases should stay, but a lot of old > branches have been merged at unknown places in the master or old > release branches. I want to propose to delete them as much as > possible. > > - I want to delete any branch that has no commits newer then one year old > - I want to ask the last commiter on any branch with commits newer > then one year to review if 'their' branch can be removed > - All branches that are merged back are to remain untouched. > > ideally only the branches 4.0, 4.1, 4.2, 4.3, 4.4, 4.5 and master will > remain as branches HEAD. This is unfortunately not true for some older > releases that were never merged back into their respective release > branches. Any work in progress will of course not be touched. > > comments? > -- > Daan > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud <http://solidfire.com/solution/overview/?video=play>*™*
