Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-build] Version number of the next release
I don't see what could be wrong with 1.4 but as you talk about the Spec Document, there isn't even a clear and definitive translation path for those specs, given they are all (except CDI who is the only spec to dual-license it under both the JCP Spec License and Apache 2) under the JCP Spec License, which is unknown and unaccepted by Eclipse Foundation.

Has the API repository for JTA been transferred already?

Werner 


On Tue, Sep 25, 2018 at 1:58 PM Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:
Hi,

Is there some guidance on the version numbers we should use for our first release from Jakarta?

If we take JTA as an example:

I don't think it should be 1.4 given it is the same as the original 1.3 in functional terms:

Options I could see are:
1.3 - match the JavaEE version
1.3.1 - does it warrant a micro?
1.0 - as this is a new groupId

If it was discussed on a different mailing list please do let me know with a link.

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

Back to the top