You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Mark Struberg <st...@yahoo.de> on 2015/01/28 15:07:21 UTC
useless branches and branch deletes at asf git repos
Hi folks!
I've found another thing which is ugly
release-tomee-1.7.2 and
tomee-1.7.2 branches which are actually just leftovers it seems?
Please be aware that we MUST NOT DELETE anything at ASF repos! We must not do history rewrite!
So think REALLY hard before creating branches which are just utter garbage. In git you just cannot get rid of them that easily. They get mirrored downstream automatically and we have no whatever control about them anymore!
Please read how we handle GIT over at DeltaSpike.
We e.g. release with localCheckout=true and pushChanges=false.
Just ping me if I need to go into details.
LieGrue,
strub
Re: useless branches and branch deletes at asf git repos
Posted by Mark Struberg <st...@yahoo.de>.
No worries John. I think what happened is that the setup for GIT is still wrong. Will need to dig and fix it.
LieGrue,
strub
> On Wednesday, 28 January 2015, 15:49, Jonathan Gallimore <jo...@gmail.com> wrote:
> >T hese are leftovers from the vote cancelled earlier this week. My intention
> was to clean them up - sounds like that should not be done from what you're
> saying? I'll ping you to discuss.
>
> Jon
>
>
> On Wed, Jan 28, 2015 at 2:09 PM, Romain Manni-Bucau
> <rm...@gmail.com>
> wrote:
>
>> I'd just delete them since it is not tag but working branch - tag
>> shouldn't have been pushed since vote didnt pass.
>>
>> We are free to create branches and remove them once we consider them
>> useless
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau
>> http://www.tomitribe.com
>> http://rmannibucau.wordpress.com
>> https://github.com/rmannibucau
>>
>>
>> 2015-01-28 15:07 GMT+01:00 Mark Struberg <st...@yahoo.de>:
>> > Hi folks!
>> >
>> > I've found another thing which is ugly
>> >
>> > release-tomee-1.7.2 and
>> > tomee-1.7.2 branches which are actually just leftovers it seems?
>> >
>> >
>> > Please be aware that we MUST NOT DELETE anything at ASF repos! We must
>> not do history rewrite!
>> >
>> > So think REALLY hard before creating branches which are just utter
>> garbage. In git you just cannot get rid of them that easily. They get
>> mirrored downstream automatically and we have no whatever control about
>> them anymore!
>> >
>> > Please read how we handle GIT over at DeltaSpike.
>> >
>> > We e.g. release with localCheckout=true and pushChanges=false.
>> >
>> >
>> > Just ping me if I need to go into details.
>> >
>> > LieGrue,
>> > strub
>>
>
Re: useless branches and branch deletes at asf git repos
Posted by Jonathan Gallimore <jo...@gmail.com>.
These are leftovers from the vote cancelled earlier this week. My intention
was to clean them up - sounds like that should not be done from what you're
saying? I'll ping you to discuss.
Jon
On Wed, Jan 28, 2015 at 2:09 PM, Romain Manni-Bucau <rm...@gmail.com>
wrote:
> I'd just delete them since it is not tag but working branch - tag
> shouldn't have been pushed since vote didnt pass.
>
> We are free to create branches and remove them once we consider them
> useless
>
>
> Romain Manni-Bucau
> @rmannibucau
> http://www.tomitribe.com
> http://rmannibucau.wordpress.com
> https://github.com/rmannibucau
>
>
> 2015-01-28 15:07 GMT+01:00 Mark Struberg <st...@yahoo.de>:
> > Hi folks!
> >
> > I've found another thing which is ugly
> >
> > release-tomee-1.7.2 and
> > tomee-1.7.2 branches which are actually just leftovers it seems?
> >
> >
> > Please be aware that we MUST NOT DELETE anything at ASF repos! We must
> not do history rewrite!
> >
> > So think REALLY hard before creating branches which are just utter
> garbage. In git you just cannot get rid of them that easily. They get
> mirrored downstream automatically and we have no whatever control about
> them anymore!
> >
> > Please read how we handle GIT over at DeltaSpike.
> >
> > We e.g. release with localCheckout=true and pushChanges=false.
> >
> >
> > Just ping me if I need to go into details.
> >
> > LieGrue,
> > strub
>
Re: useless branches and branch deletes at asf git repos
Posted by Romain Manni-Bucau <rm...@gmail.com>.
I'd just delete them since it is not tag but working branch - tag
shouldn't have been pushed since vote didnt pass.
We are free to create branches and remove them once we consider them useless
Romain Manni-Bucau
@rmannibucau
http://www.tomitribe.com
http://rmannibucau.wordpress.com
https://github.com/rmannibucau
2015-01-28 15:07 GMT+01:00 Mark Struberg <st...@yahoo.de>:
> Hi folks!
>
> I've found another thing which is ugly
>
> release-tomee-1.7.2 and
> tomee-1.7.2 branches which are actually just leftovers it seems?
>
>
> Please be aware that we MUST NOT DELETE anything at ASF repos! We must not do history rewrite!
>
> So think REALLY hard before creating branches which are just utter garbage. In git you just cannot get rid of them that easily. They get mirrored downstream automatically and we have no whatever control about them anymore!
>
> Please read how we handle GIT over at DeltaSpike.
>
> We e.g. release with localCheckout=true and pushChanges=false.
>
>
> Just ping me if I need to go into details.
>
> LieGrue,
> strub
Re: useless branches and branch deletes at asf git repos
Posted by Thiago Veronezi <th...@veronezi.org>.
Hi guys,
So "develop" is dead, right?
Can we update http://tomee.apache.org/dev/source-code.html ?
[]s,
Thiago.
On Wed, Mar 11, 2015 at 8:03 AM, Mark Struberg <st...@yahoo.de> wrote:
> So be it *pusheldiekatz*
>
> I now merged ‚develop‘ into ‚master‘
>
> I’m also working on some windows related issues which I have at a customer.
> Mainly bat scripting and test fixes…
>
> LieGrue,
> strub
>
>
>
> > Am 30.01.2015 um 17:37 schrieb Alan D. Cabrera <li...@toolazydogs.com>:
> >
> > Let’s GID! :)
> >
> >
> > Regards,
> > Alan
> >
> >> On Jan 28, 2015, at 11:39 AM, Mark Struberg <st...@yahoo.de> wrote:
> >>
> >> I personally would suggest we disable history rewrite for our whole ASF
> repo. This is a single config line in the repo.
> >>
> >> History rewrite has a huge potential to crack the repo beyond repair
> anyway.
> >>
> >>
> >>
> >> LieGrue,
> >> strub
> >>
> >>
> >>
> >>
> >>
> >>> On Wednesday, 28 January 2015, 20:12, Romain Manni-Bucau <
> rmannibucau@gmail.com> wrote:
> >>>> Nothing forbids it so it is responsability of everyone.
> >>>
> >>> Le 28 janv. 2015 19:59, "Alan D. Cabrera" <li...@toolazydogs.com>
> >>> a écrit :
> >>>
> >>>> Ahh, ok, your warnings did seem overly broad to me.
> >>>>
> >>>> How is that enforced on ASF infrastructure? Is it by an “honor
> system”
> >>>> that we assume no history rewrites are taking place?
> >>>>
> >>>>
> >>>> Regards,
> >>>> Alan
> >>>>
> >>>>
> >>>>> On Jan 28, 2015, at 10:12 AM, Mark Struberg <st...@yahoo.de>
> >>> wrote:
> >>>>>
> >>>>> Deleting those is fine. But we must make sure that no essential
> commit
> >>>> gets lost. And this is only doable by totally forbidding history
> rewrite on
> >>>> the repo.
> >>>>>
> >>>>> LieGrue,
> >>>>> strub
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>> On Wednesday, 28 January 2015, 18:27, Alan Cabrera <
> >>>> list@toolazydogs.com> wrote:
> >>>>>>> Deleting committed changes is definitely bad. Deleting
> >>> branches that
> >>>> ultimately
> >>>>>> participate in the release is also bad.
> >>>>>>
> >>>>>> However, deleting tags for "failed" releases is fine as
> >>> is deleting a
> >>>>>> branch that never transitively participated in a release should be
> >>> fine
> >>>> as well.
> >>>>>>
> >>>>>> Do I misunderstand something? Is there some infrastructure
> >>> limitation?
> >>>>>>
> >>>>>> Sent from my iPhone
> >>>>>>
> >>>>>>
> >>>>>>> On Jan 28, 2015, at 6:07 AM, Mark Struberg
> >>> <st...@yahoo.de> wrote:
> >>>>>>>
> >>>>>>> Hi folks!
> >>>>>>>
> >>>>>>> I've found another thing which is ugly
> >>>>>>>
> >>>>>>> release-tomee-1.7.2 and
> >>>>>>> tomee-1.7.2 branches which are actually just leftovers it
> >>> seems?
> >>>>>>>
> >>>>>>>
> >>>>>>> Please be aware that we MUST NOT DELETE anything at ASF repos!
> >>> We must
> >>>> not
> >>>>>> do history rewrite!
> >>>>>>>
> >>>>>>> So think REALLY hard before creating branches which are just
> >>> utter
> >>>> garbage.
> >>>>>> In git you just cannot get rid of them that easily. They get
> >>> mirrored
> >>>> downstream
> >>>>>> automatically and we have no whatever control about them anymore!
> >>>>>>>
> >>>>>>> Please read how we handle GIT over at DeltaSpike.
> >>>>>>>
> >>>>>>> We e.g. release with localCheckout=true and pushChanges=false.
> >>>>>>>
> >>>>>>>
> >>>>>>> Just ping me if I need to go into details.
> >>>>>>>
> >>>>>>> LieGrue,
> >>>>>>> strub
> >>>>>>
> >>>>
> >>>>
> >>>
> >
>
>
Re: useless branches and branch deletes at asf git repos
Posted by Mark Struberg <st...@yahoo.de>.
So be it *pusheldiekatz*
I now merged ‚develop‘ into ‚master‘
I’m also working on some windows related issues which I have at a customer.
Mainly bat scripting and test fixes…
LieGrue,
strub
> Am 30.01.2015 um 17:37 schrieb Alan D. Cabrera <li...@toolazydogs.com>:
>
> Let’s GID! :)
>
>
> Regards,
> Alan
>
>> On Jan 28, 2015, at 11:39 AM, Mark Struberg <st...@yahoo.de> wrote:
>>
>> I personally would suggest we disable history rewrite for our whole ASF repo. This is a single config line in the repo.
>>
>> History rewrite has a huge potential to crack the repo beyond repair anyway.
>>
>>
>>
>> LieGrue,
>> strub
>>
>>
>>
>>
>>
>>> On Wednesday, 28 January 2015, 20:12, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>>> Nothing forbids it so it is responsability of everyone.
>>>
>>> Le 28 janv. 2015 19:59, "Alan D. Cabrera" <li...@toolazydogs.com>
>>> a écrit :
>>>
>>>> Ahh, ok, your warnings did seem overly broad to me.
>>>>
>>>> How is that enforced on ASF infrastructure? Is it by an “honor system”
>>>> that we assume no history rewrites are taking place?
>>>>
>>>>
>>>> Regards,
>>>> Alan
>>>>
>>>>
>>>>> On Jan 28, 2015, at 10:12 AM, Mark Struberg <st...@yahoo.de>
>>> wrote:
>>>>>
>>>>> Deleting those is fine. But we must make sure that no essential commit
>>>> gets lost. And this is only doable by totally forbidding history rewrite on
>>>> the repo.
>>>>>
>>>>> LieGrue,
>>>>> strub
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> On Wednesday, 28 January 2015, 18:27, Alan Cabrera <
>>>> list@toolazydogs.com> wrote:
>>>>>>> Deleting committed changes is definitely bad. Deleting
>>> branches that
>>>> ultimately
>>>>>> participate in the release is also bad.
>>>>>>
>>>>>> However, deleting tags for "failed" releases is fine as
>>> is deleting a
>>>>>> branch that never transitively participated in a release should be
>>> fine
>>>> as well.
>>>>>>
>>>>>> Do I misunderstand something? Is there some infrastructure
>>> limitation?
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>>
>>>>>>> On Jan 28, 2015, at 6:07 AM, Mark Struberg
>>> <st...@yahoo.de> wrote:
>>>>>>>
>>>>>>> Hi folks!
>>>>>>>
>>>>>>> I've found another thing which is ugly
>>>>>>>
>>>>>>> release-tomee-1.7.2 and
>>>>>>> tomee-1.7.2 branches which are actually just leftovers it
>>> seems?
>>>>>>>
>>>>>>>
>>>>>>> Please be aware that we MUST NOT DELETE anything at ASF repos!
>>> We must
>>>> not
>>>>>> do history rewrite!
>>>>>>>
>>>>>>> So think REALLY hard before creating branches which are just
>>> utter
>>>> garbage.
>>>>>> In git you just cannot get rid of them that easily. They get
>>> mirrored
>>>> downstream
>>>>>> automatically and we have no whatever control about them anymore!
>>>>>>>
>>>>>>> Please read how we handle GIT over at DeltaSpike.
>>>>>>>
>>>>>>> We e.g. release with localCheckout=true and pushChanges=false.
>>>>>>>
>>>>>>>
>>>>>>> Just ping me if I need to go into details.
>>>>>>>
>>>>>>> LieGrue,
>>>>>>> strub
>>>>>>
>>>>
>>>>
>>>
>
Re: useless branches and branch deletes at asf git repos
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Let’s GID! :)
Regards,
Alan
> On Jan 28, 2015, at 11:39 AM, Mark Struberg <st...@yahoo.de> wrote:
>
> I personally would suggest we disable history rewrite for our whole ASF repo. This is a single config line in the repo.
>
> History rewrite has a huge potential to crack the repo beyond repair anyway.
>
>
>
> LieGrue,
> strub
>
>
>
>
>
>> On Wednesday, 28 January 2015, 20:12, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>> Nothing forbids it so it is responsability of everyone.
>>
>> Le 28 janv. 2015 19:59, "Alan D. Cabrera" <li...@toolazydogs.com>
>> a écrit :
>>
>>> Ahh, ok, your warnings did seem overly broad to me.
>>>
>>> How is that enforced on ASF infrastructure? Is it by an “honor system”
>>> that we assume no history rewrites are taking place?
>>>
>>>
>>> Regards,
>>> Alan
>>>
>>>
>>>> On Jan 28, 2015, at 10:12 AM, Mark Struberg <st...@yahoo.de>
>> wrote:
>>>>
>>>> Deleting those is fine. But we must make sure that no essential commit
>>> gets lost. And this is only doable by totally forbidding history rewrite on
>>> the repo.
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> On Wednesday, 28 January 2015, 18:27, Alan Cabrera <
>>> list@toolazydogs.com> wrote:
>>>>>> Deleting committed changes is definitely bad. Deleting
>> branches that
>>> ultimately
>>>>> participate in the release is also bad.
>>>>>
>>>>> However, deleting tags for "failed" releases is fine as
>> is deleting a
>>>>> branch that never transitively participated in a release should be
>> fine
>>> as well.
>>>>>
>>>>> Do I misunderstand something? Is there some infrastructure
>> limitation?
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>>
>>>>>> On Jan 28, 2015, at 6:07 AM, Mark Struberg
>> <st...@yahoo.de> wrote:
>>>>>>
>>>>>> Hi folks!
>>>>>>
>>>>>> I've found another thing which is ugly
>>>>>>
>>>>>> release-tomee-1.7.2 and
>>>>>> tomee-1.7.2 branches which are actually just leftovers it
>> seems?
>>>>>>
>>>>>>
>>>>>> Please be aware that we MUST NOT DELETE anything at ASF repos!
>> We must
>>> not
>>>>> do history rewrite!
>>>>>>
>>>>>> So think REALLY hard before creating branches which are just
>> utter
>>> garbage.
>>>>> In git you just cannot get rid of them that easily. They get
>> mirrored
>>> downstream
>>>>> automatically and we have no whatever control about them anymore!
>>>>>>
>>>>>> Please read how we handle GIT over at DeltaSpike.
>>>>>>
>>>>>> We e.g. release with localCheckout=true and pushChanges=false.
>>>>>>
>>>>>>
>>>>>> Just ping me if I need to go into details.
>>>>>>
>>>>>> LieGrue,
>>>>>> strub
>>>>>
>>>
>>>
>>
Re: useless branches and branch deletes at asf git repos
Posted by Mark Struberg <st...@yahoo.de>.
I personally would suggest we disable history rewrite for our whole ASF repo. This is a single config line in the repo.
History rewrite has a huge potential to crack the repo beyond repair anyway.
LieGrue,
strub
> On Wednesday, 28 January 2015, 20:12, Romain Manni-Bucau <rm...@gmail.com> wrote:
> > Nothing forbids it so it is responsability of everyone.
>
> Le 28 janv. 2015 19:59, "Alan D. Cabrera" <li...@toolazydogs.com>
> a écrit :
>
>> Ahh, ok, your warnings did seem overly broad to me.
>>
>> How is that enforced on ASF infrastructure? Is it by an “honor system”
>> that we assume no history rewrites are taking place?
>>
>>
>> Regards,
>> Alan
>>
>>
>> > On Jan 28, 2015, at 10:12 AM, Mark Struberg <st...@yahoo.de>
> wrote:
>> >
>> > Deleting those is fine. But we must make sure that no essential commit
>> gets lost. And this is only doable by totally forbidding history rewrite on
>> the repo.
>> >
>> > LieGrue,
>> > strub
>> >
>> >
>> >
>> >
>> >
>> >> On Wednesday, 28 January 2015, 18:27, Alan Cabrera <
>> list@toolazydogs.com> wrote:
>> >>> Deleting committed changes is definitely bad. Deleting
> branches that
>> ultimately
>> >> participate in the release is also bad.
>> >>
>> >> However, deleting tags for "failed" releases is fine as
> is deleting a
>> >> branch that never transitively participated in a release should be
> fine
>> as well.
>> >>
>> >> Do I misunderstand something? Is there some infrastructure
> limitation?
>> >>
>> >> Sent from my iPhone
>> >>
>> >>
>> >>> On Jan 28, 2015, at 6:07 AM, Mark Struberg
> <st...@yahoo.de> wrote:
>> >>>
>> >>> Hi folks!
>> >>>
>> >>> I've found another thing which is ugly
>> >>>
>> >>> release-tomee-1.7.2 and
>> >>> tomee-1.7.2 branches which are actually just leftovers it
> seems?
>> >>>
>> >>>
>> >>> Please be aware that we MUST NOT DELETE anything at ASF repos!
> We must
>> not
>> >> do history rewrite!
>> >>>
>> >>> So think REALLY hard before creating branches which are just
> utter
>> garbage.
>> >> In git you just cannot get rid of them that easily. They get
> mirrored
>> downstream
>> >> automatically and we have no whatever control about them anymore!
>> >>>
>> >>> Please read how we handle GIT over at DeltaSpike.
>> >>>
>> >>> We e.g. release with localCheckout=true and pushChanges=false.
>> >>>
>> >>>
>> >>> Just ping me if I need to go into details.
>> >>>
>> >>> LieGrue,
>> >>> strub
>> >>
>>
>>
>
Re: useless branches and branch deletes at asf git repos
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Nothing forbids it so it is responsability of everyone.
Le 28 janv. 2015 19:59, "Alan D. Cabrera" <li...@toolazydogs.com> a écrit :
> Ahh, ok, your warnings did seem overly broad to me.
>
> How is that enforced on ASF infrastructure? Is it by an “honor system”
> that we assume no history rewrites are taking place?
>
>
> Regards,
> Alan
>
>
> > On Jan 28, 2015, at 10:12 AM, Mark Struberg <st...@yahoo.de> wrote:
> >
> > Deleting those is fine. But we must make sure that no essential commit
> gets lost. And this is only doable by totally forbidding history rewrite on
> the repo.
> >
> > LieGrue,
> > strub
> >
> >
> >
> >
> >
> >> On Wednesday, 28 January 2015, 18:27, Alan Cabrera <
> list@toolazydogs.com> wrote:
> >>> Deleting committed changes is definitely bad. Deleting branches that
> ultimately
> >> participate in the release is also bad.
> >>
> >> However, deleting tags for "failed" releases is fine as is deleting a
> >> branch that never transitively participated in a release should be fine
> as well.
> >>
> >> Do I misunderstand something? Is there some infrastructure limitation?
> >>
> >> Sent from my iPhone
> >>
> >>
> >>> On Jan 28, 2015, at 6:07 AM, Mark Struberg <st...@yahoo.de> wrote:
> >>>
> >>> Hi folks!
> >>>
> >>> I've found another thing which is ugly
> >>>
> >>> release-tomee-1.7.2 and
> >>> tomee-1.7.2 branches which are actually just leftovers it seems?
> >>>
> >>>
> >>> Please be aware that we MUST NOT DELETE anything at ASF repos! We must
> not
> >> do history rewrite!
> >>>
> >>> So think REALLY hard before creating branches which are just utter
> garbage.
> >> In git you just cannot get rid of them that easily. They get mirrored
> downstream
> >> automatically and we have no whatever control about them anymore!
> >>>
> >>> Please read how we handle GIT over at DeltaSpike.
> >>>
> >>> We e.g. release with localCheckout=true and pushChanges=false.
> >>>
> >>>
> >>> Just ping me if I need to go into details.
> >>>
> >>> LieGrue,
> >>> strub
> >>
>
>
Re: useless branches and branch deletes at asf git repos
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Ahh, ok, your warnings did seem overly broad to me.
How is that enforced on ASF infrastructure? Is it by an “honor system” that we assume no history rewrites are taking place?
Regards,
Alan
> On Jan 28, 2015, at 10:12 AM, Mark Struberg <st...@yahoo.de> wrote:
>
> Deleting those is fine. But we must make sure that no essential commit gets lost. And this is only doable by totally forbidding history rewrite on the repo.
>
> LieGrue,
> strub
>
>
>
>
>
>> On Wednesday, 28 January 2015, 18:27, Alan Cabrera <li...@toolazydogs.com> wrote:
>>> Deleting committed changes is definitely bad. Deleting branches that ultimately
>> participate in the release is also bad.
>>
>> However, deleting tags for "failed" releases is fine as is deleting a
>> branch that never transitively participated in a release should be fine as well.
>>
>> Do I misunderstand something? Is there some infrastructure limitation?
>>
>> Sent from my iPhone
>>
>>
>>> On Jan 28, 2015, at 6:07 AM, Mark Struberg <st...@yahoo.de> wrote:
>>>
>>> Hi folks!
>>>
>>> I've found another thing which is ugly
>>>
>>> release-tomee-1.7.2 and
>>> tomee-1.7.2 branches which are actually just leftovers it seems?
>>>
>>>
>>> Please be aware that we MUST NOT DELETE anything at ASF repos! We must not
>> do history rewrite!
>>>
>>> So think REALLY hard before creating branches which are just utter garbage.
>> In git you just cannot get rid of them that easily. They get mirrored downstream
>> automatically and we have no whatever control about them anymore!
>>>
>>> Please read how we handle GIT over at DeltaSpike.
>>>
>>> We e.g. release with localCheckout=true and pushChanges=false.
>>>
>>>
>>> Just ping me if I need to go into details.
>>>
>>> LieGrue,
>>> strub
>>
Re: useless branches and branch deletes at asf git repos
Posted by Mark Struberg <st...@yahoo.de>.
Deleting those is fine. But we must make sure that no essential commit gets lost. And this is only doable by totally forbidding history rewrite on the repo.
LieGrue,
strub
> On Wednesday, 28 January 2015, 18:27, Alan Cabrera <li...@toolazydogs.com> wrote:
> > Deleting committed changes is definitely bad. Deleting branches that ultimately
> participate in the release is also bad.
>
> However, deleting tags for "failed" releases is fine as is deleting a
> branch that never transitively participated in a release should be fine as well.
>
> Do I misunderstand something? Is there some infrastructure limitation?
>
> Sent from my iPhone
>
>
>> On Jan 28, 2015, at 6:07 AM, Mark Struberg <st...@yahoo.de> wrote:
>>
>> Hi folks!
>>
>> I've found another thing which is ugly
>>
>> release-tomee-1.7.2 and
>> tomee-1.7.2 branches which are actually just leftovers it seems?
>>
>>
>> Please be aware that we MUST NOT DELETE anything at ASF repos! We must not
> do history rewrite!
>>
>> So think REALLY hard before creating branches which are just utter garbage.
> In git you just cannot get rid of them that easily. They get mirrored downstream
> automatically and we have no whatever control about them anymore!
>>
>> Please read how we handle GIT over at DeltaSpike.
>>
>> We e.g. release with localCheckout=true and pushChanges=false.
>>
>>
>> Just ping me if I need to go into details.
>>
>> LieGrue,
>> strub
>
Re: useless branches and branch deletes at asf git repos
Posted by Alan Cabrera <li...@toolazydogs.com>.
Deleting committed changes is definitely bad. Deleting branches that ultimately participate in the release is also bad.
However, deleting tags for "failed" releases is fine as is deleting a branch that never transitively participated in a release should be fine as well.
Do I misunderstand something? Is there some infrastructure limitation?
Sent from my iPhone
> On Jan 28, 2015, at 6:07 AM, Mark Struberg <st...@yahoo.de> wrote:
>
> Hi folks!
>
> I've found another thing which is ugly
>
> release-tomee-1.7.2 and
> tomee-1.7.2 branches which are actually just leftovers it seems?
>
>
> Please be aware that we MUST NOT DELETE anything at ASF repos! We must not do history rewrite!
>
> So think REALLY hard before creating branches which are just utter garbage. In git you just cannot get rid of them that easily. They get mirrored downstream automatically and we have no whatever control about them anymore!
>
> Please read how we handle GIT over at DeltaSpike.
>
> We e.g. release with localCheckout=true and pushChanges=false.
>
>
> Just ping me if I need to go into details.
>
> LieGrue,
> strub