Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cu-dev] Move RI repo to GlassFish project

Hi Ed,

 

I’ll raise the question on the Glassfish project list.

 

From a CI point of view I was hoping we could move the repo only in an organisational sense i.e. it would be owned by the GlassFish project rather than do anything to it on GitHub. Hopefully that is possible. I’ve CC’d in Wayne to see if that is possible.

 

Steve

 

From: Ed Bratt <ed.bratt@xxxxxxxxxx>
Sent: 06 June 2019 01:01
To: cu developer discussions <cu-dev@xxxxxxxxxxx>; Steve Millidge (Payara) <steve.millidge@xxxxxxxxxxx>
Subject: Re: [cu-dev] Move RI repo to GlassFish project

 

Steve,

Presumably, we would need a similar question posed to the GlassFish project (which, Steve, you are also lead of so that shouldn't have much trouble). Is that your plan?

Also, if we move anything we will need to be mindful of the CI related work that will need to be updated. Anything that is watching for updates at a particular repository location, will need to track changes such as described in this proposal. This is likely to require some work, beyond just moving the repository.

As contributor to the "project boss" effort, I am concerned about anything that's not absolutely necessary for releasing Jakarta EE 8, but I am committed to supporting what the project team consensus settles on.

-- Ed

On 6/5/2019 6:17 AM, Steve Millidge (Payara) wrote:

Hi,

 

This project needs to be converted into a specification project consisting of the API, TCK and Spec document which is the focus of the scope statement change and the name change. Therefore the concurrency-api repo will move to this new spec project.  However this leaves the concurrency-ri repo. I am not aware that the RI is used anywhere but within GlassFish.

 

I am therefore calling a committer vote as to whether the concurreny-ri repo should be moved to the GlassFish project.

 

+1 if you agree

0 to abstain

-1 to veto

 

If we get a vote in favour I will propose this as part of the project restructuring review.

 

I am +1

 

Thanks

 

Steve

 

 

 

 



_______________________________________________
cu-dev mailing list
cu-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cu-dev

Back to the top