Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-spec-project-leads] [ee4j-pmc] Preparing for Jakarta EE 8 Release
Thanks Scott - I wondered if we were getting everything in this release except the final spec texts. IMO it would be useful to align the GAVs soon.

e.g. jakarta.transaction for Jakarta Transactions would be nice to reflect in the GAV sooner so it can be integrated to Glassfish and the TCK.

On Fri, 12 Jul 2019 at 14:58, Scott Stark <starksm64@xxxxxxxxx> wrote:
I would expect that GAVs should not be updated in this Jakarta EE 8 release. I’ll bring this up on the spec committee.


On Jul 12, 2019, at 6:23 AM, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:



On Fri, 12 Jul 2019 at 11:54, Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:
I have two questions about this:

On Wed, 3 Jul 2019 at 18:00, Ivar Grimstad <ivar.grimstad@xxxxxxxxx> wrote:
Hi, 

First, a message to all the specification project leads:
You are strongly encouraged to join this mailing list:

We are on a tight schedule to get the Jakarta EE specifications ready for the Jakarta EE 8 Release. I am in the process of creating GitHub issues in the projects that will be followed up here: https://github.com/orgs/eclipse-ee4j/projects/15

If you don't have an issue created for you yet, please feel free to create an issue titled "Prepare Jakarta XXX for the Jakarta EE 8 Release" with the following content in your issue tracker:
-----
### Instructions

- [ ] Update text files

Should we be doing something about acronym usage within the Java source files too. 
For example:
a. @Since doclets such as https://github.com/eclipse-ee4j/jta-api/blob/EE4J_8/src/main/java/javax/transaction/Transactional.java#L55 where we reference JTA 1.2 - personally I think that is fine as it is factual
b. Reference to old acronyms to describe the behaviours in the javadocs. For instance "JTA transaction" in https://github.com/eclipse-ee4j/jta-api/blob/EE4J_8/src/main/java/javax/transaction/Transactional.java#L77 could be changed to "Jakarta Transactions transaction"


- [ ] Generate "boilerplate" specification project
- [ ] Make a staging release

As part of the release to staging should we be updating the groupId and artifactIds to reflect the outcome of the naming decision. In the Jakarta Transactions case that would mean a change  jakarta.transaction:jakarta-transaction-api to jakarta.transactions:jakarta-transaction-api to reflect the decision here https://github.com/eclipse-ee4j/jta-api/issues/36#issuecomment-499446887

This is my only outstanding query that I need an answer for now - thanks! 


Thanks!
- [ ] Generate Stand-alone TCK test results
- [ ] Submit tests for ballot
- [ ] Release to Maven Central

See [here](https://wiki.eclipse.org/How_to_Prepare_API_Projects_to_Jakarta_EE_8_Release) for detailed instructions.
------

All the above need to be done by July 15 in order to follow the plan for the Jakarta EE 8 Release.

Ivar
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads

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

Back to the top