Re: [DISCUSS] Renaming of master branches to main?

[Richard Zowalla]

Short update: 

INFRA can do a bulk renaming. We only need to switch the CI checkouts
after INFRA-23570 is completed.

I will give an update after the renaming is done, so people can adjust
their local checkouts.




Am Dienstag, dem 09.08.2022 um 13:51 + schrieb Zowalla, Richard:
> Sure.
> 
> I created a related Jira: TOMEE-4025
> 
> In addition, I already asked INFRA, if this is a self service thing
> or if they need a ticket to switch the "default" branch for the
> GitHub/GitBox sync things.
> 
> Gruß
> Richard
> 
> Von: Jean-Louis Monteiro 
> Gesendet: Dienstag, 9. August 2022 15:24:50
> An: dev@tomee.apache.org
> Betreff: Re: [DISCUSS] Renaming of master branches to main?
> 
> I think you can take the action and update all tools. If you need
> some
> help, lemme know
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
> 
> 
> On Wed, Aug 3, 2022 at 6:40 PM Jonathan Gallimore <
> jonathan.gallim...@gmail.com> wrote:
> 
> > +1
> > 
> > On Thu, Jul 28, 2022 at 4:54 PM Richard Zowalla 
> > wrote:
> > 
> > > Hi all,
> > > 
> > > I would like to get the community's opinion on renaming the
> > > "master"
> > > branches for the TomEE related repositories to "main".
> > > 
> > > I see quite a few ASF projects (and other OSS projects) have made
> > > the
> > > change and I personally think we should, too, for the same reason
> > > of
> > > promoting inclusivity (see [1]).
> > > 
> > > I think we would need to update the target branch of the
> > > outstanding
> > > PRs, update GitHub actions, update the Jenkins build config +
> > > local
> > > checkouts. Anything else?
> > > 
> > > Thoughts?
> > > 
> > > Gruß
> > > Richard
> > > 
> > > 
> > > [1] https://sfconservancy.org/news/2020/jun/23/gitbranchname/
> > > 
> > > 

AW: [DISCUSS] Renaming of master branches to main?

[Zowalla, Richard]

Sure.

I created a related Jira: TOMEE-4025

In addition, I already asked INFRA, if this is a self service thing or if they 
need a ticket to switch the "default" branch for the GitHub/GitBox sync things.

Gruß
Richard

Von: Jean-Louis Monteiro 
Gesendet: Dienstag, 9. August 2022 15:24:50
An: dev@tomee.apache.org
Betreff: Re: [DISCUSS] Renaming of master branches to main?

I think you can take the action and update all tools. If you need some
help, lemme know
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Aug 3, 2022 at 6:40 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:

> +1
>
> On Thu, Jul 28, 2022 at 4:54 PM Richard Zowalla  wrote:
>
> > Hi all,
> >
> > I would like to get the community's opinion on renaming the "master"
> > branches for the TomEE related repositories to "main".
> >
> > I see quite a few ASF projects (and other OSS projects) have made the
> > change and I personally think we should, too, for the same reason of
> > promoting inclusivity (see [1]).
> >
> > I think we would need to update the target branch of the outstanding
> > PRs, update GitHub actions, update the Jenkins build config + local
> > checkouts. Anything else?
> >
> > Thoughts?
> >
> > Gruß
> > Richard
> >
> >
> > [1] https://sfconservancy.org/news/2020/jun/23/gitbranchname/
> >
> >
>

Re: [DISCUSS] Renaming of master branches to main?

[Jean-Louis Monteiro]

I think you can take the action and update all tools. If you need some
help, lemme know
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Aug 3, 2022 at 6:40 PM Jonathan Gallimore <
jonathan.gallim...@gmail.com> wrote:

> +1
>
> On Thu, Jul 28, 2022 at 4:54 PM Richard Zowalla  wrote:
>
> > Hi all,
> >
> > I would like to get the community's opinion on renaming the "master"
> > branches for the TomEE related repositories to "main".
> >
> > I see quite a few ASF projects (and other OSS projects) have made the
> > change and I personally think we should, too, for the same reason of
> > promoting inclusivity (see [1]).
> >
> > I think we would need to update the target branch of the outstanding
> > PRs, update GitHub actions, update the Jenkins build config + local
> > checkouts. Anything else?
> >
> > Thoughts?
> >
> > Gruß
> > Richard
> >
> >
> > [1] https://sfconservancy.org/news/2020/jun/23/gitbranchname/
> >
> >
>

Re: [DISCUSS] Renaming of master branches to main?

[Jonathan Gallimore]

+1

On Thu, Jul 28, 2022 at 4:54 PM Richard Zowalla  wrote:

> Hi all,
>
> I would like to get the community's opinion on renaming the "master"
> branches for the TomEE related repositories to "main".
>
> I see quite a few ASF projects (and other OSS projects) have made the
> change and I personally think we should, too, for the same reason of
> promoting inclusivity (see [1]).
>
> I think we would need to update the target branch of the outstanding
> PRs, update GitHub actions, update the Jenkins build config + local
> checkouts. Anything else?
>
> Thoughts?
>
> Gruß
> Richard
>
>
> [1] https://sfconservancy.org/news/2020/jun/23/gitbranchname/
>
>

RE: [DISCUSS] Renaming of master branches to main?

[Jenkins, Rodney J (Rod)]

+1

-Original Message-
From: Richard Zowalla  
Sent: Thursday, July 28, 2022 10:55 AM
To: dev@tomee.apache.org
Subject: [EXTERNAL] [DISCUSS] Renaming of master branches to main?

Nationwide Information Security Warning: This is an EXTERNAL email. Use CAUTION 
before clicking on links, opening attachments, or responding. (Sender: 
dev-return-29738-JENKIR14=nationwide@tomee.apache.org)

--


Hi all,

I would like to get the community's opinion on renaming the "master"
branches for the TomEE related repositories to "main".

I see quite a few ASF projects (and other OSS projects) have made the change 
and I personally think we should, too, for the same reason of promoting 
inclusivity (see [1]).

I think we would need to update the target branch of the outstanding PRs, 
update GitHub actions, update the Jenkins build config + local checkouts. 
Anything else?

Thoughts?

Gruß
Richard


[1] https://sfconservancy.org/news/2020/jun/23/gitbranchname/

Re: [DISCUSS] Renaming of master branches to main?

[Wiesner, Martin]

+1 for a transition to 'main'

—
https://twitter.com/mawiesne 


> Am 28.07.2022 um 19:20 schrieb Jean-Louis Monteiro :
> 
> Fully agree.
> 
> We should move to main
> 
> Le jeu. 28 juil. 2022, 16:54, Richard Zowalla  a écrit :
> 
>> Hi all,
>> 
>> I would like to get the community's opinion on renaming the "master"
>> branches for the TomEE related repositories to "main".
>> 
>> I see quite a few ASF projects (and other OSS projects) have made the
>> change and I personally think we should, too, for the same reason of
>> promoting inclusivity (see [1]).
>> 
>> I think we would need to update the target branch of the outstanding
>> PRs, update GitHub actions, update the Jenkins build config + local
>> checkouts. Anything else?
>> 
>> Thoughts?
>> 
>> Gruß
>> Richard
>> 
>> 
>> [1] https://sfconservancy.org/news/2020/jun/23/gitbranchname/
>> 
>> 



smime.p7s
Description: S/MIME cryptographic signature

Re: [DISCUSS] Renaming of master branches to main?

[Jean-Louis Monteiro]

Fully agree.

We should move to main

Le jeu. 28 juil. 2022, 16:54, Richard Zowalla  a écrit :

> Hi all,
>
> I would like to get the community's opinion on renaming the "master"
> branches for the TomEE related repositories to "main".
>
> I see quite a few ASF projects (and other OSS projects) have made the
> change and I personally think we should, too, for the same reason of
> promoting inclusivity (see [1]).
>
> I think we would need to update the target branch of the outstanding
> PRs, update GitHub actions, update the Jenkins build config + local
> checkouts. Anything else?
>
> Thoughts?
>
> Gruß
> Richard
>
>
> [1] https://sfconservancy.org/news/2020/jun/23/gitbranchname/
>
>

[DISCUSS] Renaming of master branches to main?

[Richard Zowalla]

Hi all,

I would like to get the community's opinion on renaming the "master"
branches for the TomEE related repositories to "main".

I see quite a few ASF projects (and other OSS projects) have made the
change and I personally think we should, too, for the same reason of
promoting inclusivity (see [1]).

I think we would need to update the target branch of the outstanding
PRs, update GitHub actions, update the Jenkins build config + local
checkouts. Anything else?

Thoughts?

Gruß
Richard


[1] https://sfconservancy.org/news/2020/jun/23/gitbranchname/