You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Ralph Goers <ra...@dslextreme.com> on 2015/11/21 06:03:02 UTC
Deleting branch LOG4J2-89
I merged branch LOG4J2-89 and then tried to delete the branch. It appears deleting branches is no longer allowed. I suspect that also means I won’t be able to delete a tag if a release fails. I recall seeing a discussion on one of the mailing lists (board?) about this.
If this is the case then I may have to resort to doing any work on feature branches at github. I think I can specify a tag for the release process so each release will probably be tagged as rc1, rc2, etc and the last one will be the actual release tag.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Deleting branch LOG4J2-89
Posted by Mikael Ståldal <mi...@magine.com>.
I agree that it is annoying with many old branches around.
On Sat, Nov 21, 2015 at 6:17 AM, Ralph Goers <ra...@dslextreme.com>
wrote:
> They actually do get annoying when you are trying to switch branches in
> IntelliJ. You have to select from a list. Right now we only have about 20
> so it isn’t a huge issue.
>
> Ralph
>
> > On Nov 20, 2015, at 10:09 PM, Remko Popma <re...@gmail.com> wrote:
> >
> > Isn't this (deleting branches is disallowed) just a temporary measure?
> > Is there any urgent need to change our workflow because of this? Old
> branches don't get in my way, I don't mind if there are many of them.
> >
> > Remko
> >
> > Sent from my iPhone
> >
> >> On 2015/11/21, at 14:03, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >>
> >> I merged branch LOG4J2-89 and then tried to delete the branch. It
> appears deleting branches is no longer allowed. I suspect that also means I
> won’t be able to delete a tag if a release fails. I recall seeing a
> discussion on one of the mailing lists (board?) about this.
> >>
> >> If this is the case then I may have to resort to doing any work on
> feature branches at github. I think I can specify a tag for the release
> process so each release will probably be tagged as rc1, rc2, etc and the
> last one will be the actual release tag.
> >>
> >> Ralph
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
--
[image: MagineTV]
*Mikael Ståldal*
Senior software developer
*Magine TV*
mikael.staldal@magine.com
Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com
Privileged and/or Confidential Information may be contained in this
message. If you are not the addressee indicated in this message
(or responsible for delivery of the message to such a person), you may not
copy or deliver this message to anyone. In such case,
you should destroy this message and kindly notify the sender by reply
email.
Re: Deleting branch LOG4J2-89
Posted by Ralph Goers <ra...@dslextreme.com>.
They actually do get annoying when you are trying to switch branches in IntelliJ. You have to select from a list. Right now we only have about 20 so it isn’t a huge issue.
Ralph
> On Nov 20, 2015, at 10:09 PM, Remko Popma <re...@gmail.com> wrote:
>
> Isn't this (deleting branches is disallowed) just a temporary measure?
> Is there any urgent need to change our workflow because of this? Old branches don't get in my way, I don't mind if there are many of them.
>
> Remko
>
> Sent from my iPhone
>
>> On 2015/11/21, at 14:03, Ralph Goers <ra...@dslextreme.com> wrote:
>>
>> I merged branch LOG4J2-89 and then tried to delete the branch. It appears deleting branches is no longer allowed. I suspect that also means I won’t be able to delete a tag if a release fails. I recall seeing a discussion on one of the mailing lists (board?) about this.
>>
>> If this is the case then I may have to resort to doing any work on feature branches at github. I think I can specify a tag for the release process so each release will probably be tagged as rc1, rc2, etc and the last one will be the actual release tag.
>>
>> Ralph
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Deleting branch LOG4J2-89
Posted by Remko Popma <re...@gmail.com>.
Isn't this (deleting branches is disallowed) just a temporary measure?
Is there any urgent need to change our workflow because of this? Old branches don't get in my way, I don't mind if there are many of them.
Remko
Sent from my iPhone
> On 2015/11/21, at 14:03, Ralph Goers <ra...@dslextreme.com> wrote:
>
> I merged branch LOG4J2-89 and then tried to delete the branch. It appears deleting branches is no longer allowed. I suspect that also means I won’t be able to delete a tag if a release fails. I recall seeing a discussion on one of the mailing lists (board?) about this.
>
> If this is the case then I may have to resort to doing any work on feature branches at github. I think I can specify a tag for the release process so each release will probably be tagged as rc1, rc2, etc and the last one will be the actual release tag.
>
> Ralph
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Deleting branch LOG4J2-89
Posted by Gary Gregory <ga...@gmail.com>.
For me, keeping tags of failed RC is a good thing.
Gary
On Nov 20, 2015 9:03 PM, "Ralph Goers" <ra...@dslextreme.com> wrote:
> I merged branch LOG4J2-89 and then tried to delete the branch. It appears
> deleting branches is no longer allowed. I suspect that also means I won’t
> be able to delete a tag if a release fails. I recall seeing a discussion
> on one of the mailing lists (board?) about this.
>
> If this is the case then I may have to resort to doing any work on feature
> branches at github. I think I can specify a tag for the release process so
> each release will probably be tagged as rc1, rc2, etc and the last one will
> be the actual release tag.
>
> Ralph
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>