Re: [glassfish-dev] Project Board

[Bill Shannon <bill.shannon@xxxxxxxxxx>]

(Catching up on email...)

Can I assume that GlasFish is now ready for jakarta.* versions of APIs and implementations to be integrated?

I've got 2.0.0-RC1 versions of Activation and Mail that I could start integrating.  Ditto the TCK.  Should I just go ahead and do this?  Any rules or caveats I should know about?

Steve Millidge (Payara) wrote on 2/18/20 10:03 AM:

 

I have created a project board https://github.com/eclipse-ee4j/glassfish/projects/1.

 

My suggestion is we create issues for tasks required for the 6.0 release and target them to the 6.0.0 milestone. We can then pull all the 6.0.0 milestone issues onto the project board and track progress that way.

 

Ideas for first issues, of the top of my head, are;

 

JDK 11 support.

1 issue for incorporation of each api

1 issue for each Compatible Implementation that GlassFIsh pulls in e.g Tyrus, Jersey etc.

Analysis of the deployment subsystem and a series of issues of work in this area.

1 issue for each spec compatible implementation that is a part of GlassFish e.g. Connectors, Enterprise Beans etc.

 

Thoughts?

 

Steve

 

 

 

 

_______________________________________________
glassfish-dev mailing list
glassfish-dev@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/glassfish-dev__;!!GqivPVa7Brio!McoNrHKQzPLbuPkinHPaRxdb5DdgTmuxjTI7IFBXqHlaokCtd8bFcKiPcZmvJCls2Q$