You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Daan Hoogland <da...@gmail.com> on 2015/08/02 15:46:11 UTC
[DISCUSS][PROPOSAL] cleanup repo
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
RE: [DISCUSS][PROPOSAL] cleanup repo
Posted by Somesh Naidu <So...@citrix.com>.
+1
I believe we are saying these branches will no longer have any future releases; that they are technically EOM/EOL.
Regards,
Somesh
From: Rohit Yadav [mailto:rohit.yadav@shapeblue.com]
Sent: Monday, August 03, 2015 10:41 AM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS][PROPOSAL] cleanup repo
+1
I think we can easily cleanup all branches that are 6+ months older.
On 03-Aug-2015, at 10:46 am, Rajani Karuturi <ra...@apache.org>> wrote:
+1 Agree. We have more than 200 branches.
~Rajani
On Mon, Aug 3, 2015 at 4:39 AM, Boris Schrijver <bo...@pcextreme.nl>> wrote:
+1
Best regards,
Boris Schrijver
TEL: +31633784542
MAIL: boris@pcextreme.nl<ma...@pcextreme.nl>
On August 2, 2015 at 5:17 PM Wido den Hollander <wi...@widodh.nl>>
wrote:
On 08/02/2015 03:46 PM, Daan Hoogland 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?
Nope, a good idea. We should remove old branches. I'd say that
everything over 6 months is also old.
Wido
Regards,
Rohit Yadav
Software Architect, ShapeBlue
[cid:9DD97B41-04C5-45F0-92A7-951F3E962F7A]
M. +91 88 262 30892 | rohit.yadav@shapeblue.com<ma...@shapeblue.com>
Blog: bhaisaab.org<http://bhaisaab.org> | Twitter: @_bhaisaab
Find out more about ShapeBlue and our range of CloudStack related services
IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build/>
CSForge - rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-engineering/>
CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
Re: [DISCUSS][PROPOSAL] cleanup repo
Posted by Rohit Yadav <ro...@shapeblue.com>.
+1
I think we can easily cleanup all branches that are 6+ months older.
On 03-Aug-2015, at 10:46 am, Rajani Karuturi <ra...@apache.org>> wrote:
+1 Agree. We have more than 200 branches.
~Rajani
On Mon, Aug 3, 2015 at 4:39 AM, Boris Schrijver <bo...@pcextreme.nl>> wrote:
+1
Best regards,
Boris Schrijver
TEL: +31633784542
MAIL: boris@pcextreme.nl<ma...@pcextreme.nl>
On August 2, 2015 at 5:17 PM Wido den Hollander <wi...@widodh.nl>>
wrote:
On 08/02/2015 03:46 PM, Daan Hoogland 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?
Nope, a good idea. We should remove old branches. I'd say that
everything over 6 months is also old.
Wido
Regards,
Rohit Yadav
Software Architect, ShapeBlue
[cid:9DD97B41-04C5-45F0-92A7-951F3E962F7A]
M. +91 88 262 30892 | rohit.yadav@shapeblue.com<ma...@shapeblue.com>
Blog: bhaisaab.org<http://bhaisaab.org> | Twitter: @_bhaisaab
Find out more about ShapeBlue and our range of CloudStack related services
IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
CSForge - rapid IaaS deployment framework<http://shapeblue.com/csforge/>
CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-engineering/>
CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/>
CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>
This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark.
Re: [DISCUSS][PROPOSAL] cleanup repo
Posted by Rajani Karuturi <ra...@apache.org>.
+1 Agree. We have more than 200 branches.
~Rajani
On Mon, Aug 3, 2015 at 4:39 AM, Boris Schrijver <bo...@pcextreme.nl> wrote:
> +1
>
>
> Best regards,
>
> Boris Schrijver
>
> TEL: +31633784542
> MAIL: boris@pcextreme.nl
>
> >
> > On August 2, 2015 at 5:17 PM Wido den Hollander <wi...@widodh.nl>
> wrote:
> >
> >
> >
> >
> > On 08/02/2015 03:46 PM, Daan Hoogland 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?
> > >
> >
> > Nope, a good idea. We should remove old branches. I'd say that
> > everything over 6 months is also old.
> >
> > Wido
> >
>
Re: [DISCUSS][PROPOSAL] cleanup repo
Posted by Boris Schrijver <bo...@pcextreme.nl>.
+1
Best regards,
Boris Schrijver
TEL: +31633784542
MAIL: boris@pcextreme.nl
>
> On August 2, 2015 at 5:17 PM Wido den Hollander <wi...@widodh.nl> wrote:
>
>
>
>
> On 08/02/2015 03:46 PM, Daan Hoogland 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?
> >
>
> Nope, a good idea. We should remove old branches. I'd say that
> everything over 6 months is also old.
>
> Wido
>
Re: [DISCUSS][PROPOSAL] cleanup repo
Posted by Wido den Hollander <wi...@widodh.nl>.
On 08/02/2015 03:46 PM, Daan Hoogland 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?
>
Nope, a good idea. We should remove old branches. I'd say that
everything over 6 months is also old.
Wido
Re: [DISCUSS][PROPOSAL] cleanup repo
Posted by Mike Tutkowski <mi...@solidfire.com>.
+1
On Sunday, August 2, 2015, Daan Hoogland <da...@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.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the cloud
<http://solidfire.com/solution/overview/?video=play>*™*
Re: [DISCUSS][PROPOSAL] cleanup repo
Posted by Daan Hoogland <da...@gmail.com>.
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 <ru...@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 <RB...@schubergphilis.com>
> wrote:
> >
> > +1
> >
> >> On 02 Aug 2015, at 15:46, Daan Hoogland <da...@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
Re: [DISCUSS][PROPOSAL] cleanup repo
Posted by Sebastien Goasguen <ru...@gmail.com>.
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 <RB...@schubergphilis.com> wrote:
>
> +1
>
>> On 02 Aug 2015, at 15:46, Daan Hoogland <da...@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
>
Re: [DISCUSS][PROPOSAL] cleanup repo
Posted by Remi Bergsma <RB...@schubergphilis.com>.
+1
> On 02 Aug 2015, at 15:46, Daan Hoogland <da...@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