cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daan Hoogland <daan.hoogl...@gmail.com>
Subject Re: [DISCUSS][PROPOSAL] cleanup repo
Date Mon, 10 Aug 2015 09:08:22 GMT
I will, Sebastien. I know that some of this is gems. A lot of it has been
merged or really abandoned and superseded by other code. I know you and
Pierre-Luc are working on docker so I would definitely inquire with you
guys about this branch.

On Mon, Aug 10, 2015 at 10:29 AM, Sebastien Goasguen <runseb@gmail.com>
wrote:

> I’d just be a bit careful here.
>
> There might be some tale branches that still have useful info.
> like the ‘docker’ branch. it might just be 100 LOC that are interesting
> but yet, that’s where they are.
>
> > On Aug 3, 2015, at 6:06 PM, Remi Bergsma <RBergsma@schubergphilis.com>
> wrote:
> >
> > +1
> >
> >> On 02 Aug 2015, at 15:46, Daan Hoogland <daan.hoogland@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
> >
>
>


-- 
Daan

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message