Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-pmc] Migration to Jakarta installation of Nexus

+1

arjan tijms wrote on 2/18/20 6:37 AM:
Hi,

It's a +1 from my side, acknowledging that it's the "glassfish-bot user" which is A user of the org.glassfish.* namespace, but not the only one.

If some others explicitly +1 as well we'd be good to go.

Kind regards,
Arjan



On Tue, Feb 18, 2020 at 3:28 PM Terry Yanko <tyanko@xxxxxxxxxxxx> wrote:
Hello, 

Just following up on this discussion. I don't believe I ever got a clear answer in terms of whether or not we were ready to migrate the glassfish-bot user. Should we proceed with this?

Best, 

Terry

On Fri, Feb 7, 2020 at 11:34 AM arjan tijms <arjan.tijms@xxxxxxxxx> wrote:
Hi,

Thanks! I’ll try to stage or just access Jakarta.oss soon.

I’m just a member of the GF team so I’m not authorised to decide about shutting down.

Steve is the team lead (should be reading this list) and would be in a better position for that. I will discuss with Romain who is much involved with the practical side of running the jobs.

Thx!

On Friday, February 7, 2020, Terry Yanko <tyanko@xxxxxxxxxxxx> wrote:
Hello Arjan, 

Thanks for volunteering to help out with the remaining migrations. The glassfish-bot user is created on the new instance, I'll just need to assign it the org.glassfish deployment role and you'll be all set. Before we proceed, are you able to authorize disabling the account on oss.sonatype.org? We wouldn't want to cause any unexpected interruptions.  If there are other users you'd like to activate on the new host in addition to the glassfish-bot users, just let me know (the process will be similar for them).

Thanks!

Terry

On Thu, Feb 6, 2020 at 8:50 PM David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
On Feb 6, 2020, at 5:32 PM, arjan tijms <arjan.tijms@xxxxxxxxx> wrote:

On Fri, Feb 7, 2020 at 1:47 AM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
Better, they should just switch to the new Nexus and avoid the confusion.

Indeed, so that means the user for GlassFish has to be created on the new Nexus. I'm willing to volunteer, but I've no idea how to do that.

Terry,

Meet Arjan who has volunteered to organize the remaining batches of migrations (the users we held).


Arjan, the primary job is:

 - Don't kill Terry with a dozen migration requests -- try to organize the projects into say 1 to 3 more batches/waves
 - Knock on the doors of the implementation projects and ask:
    - if they want to migrate (it's their choice)
    - ask them when they might want to migrate
    - group them together as makes sense
 - Work with Terry to identify a cutover date for each batch
 - Work with the implementation projects to ensure they are aware and ready for their cutover date
 - Deal with any complaints

The shorter version is, do the best you can, try to get people to help you while you help them :)


-David





_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/ee4j-pmc__;!!GqivPVa7Brio!NaPVG7lLYn4rLEvaeE-_FkjwzmRAQFYf2rA801CiX9b7wk3cmnCsdDtpgQkwCLmKqg$ 


Back to the top