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
If you release the API under 1.4 as the current POM suggest, then it would be weird to call the Spec 1.3.1 even if the changes are minimal.
These numbers at least of Spec and API should be in sync. 

The Spec Committee has briefly touched this, but now deals with other issues. There were even more radical views like having to sync up every single version of every artifact (hence raise the Spec and publish a new version even if there's a minor bugfix e.g. 1.4.3 of the TCK) but at least the first Spec should correspond to whatever version of the API you have by then, if it's 1.4.1, sure why not, but I would not call the Spec 1.3.1 if the API already got out as 1.4.x.




On Tue, Sep 25, 2018 at 3:11 PM Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:
I do actually have a PR to change the groupId, artifact:

But it's not clear to me exactly if you are suggesting there is some more fundamental agreement about a spec transfer related to JCP that needs to happen before I can do a release of the artifact?

On Tue, 25 Sep 2018 at 13:36, Werner Keil <werner.keil@xxxxxxxxx> wrote:
IMO the API repository that does exist should be aligned with a still to be defined and created spec artifact.

https://github.com/eclipse-ee4j/jta-api/blob/master/pom.xml (also has not updated to "jakarta" btw.) currently says
1.4-SNAPSHOT  
If you prefer the next version to be 1.3.1 instead of 1.4, then please also do the same in the API;-)

Werner




On Tue, Sep 25, 2018 at 2:30 PM Dmitry Kornilov <dmitry.kornilov@xxxxxxxxxx> wrote:
Hi,

It’s described here:

Pasting it here for convenience:

"The released version should be the project's next version after the Java EE release. For example, it should be version 1.0.1 if the last version released by Oracle is 1.0.”

In your case the version should be 1.3.1

Thanks,
Dmitry


On 25 Sep 2018, at 13:57, 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

_______________________________________________
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
_______________________________________________
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
_______________________________________________
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