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
On Tue, Sep 25, 2018 at 3:15 PM Tom Jenkinson <tom.jenkinson@xxxxxxxxxx> wrote:


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

Thanks!



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.”

One thing that was not totally clear to me from there was the requirement about EE4J_8 branch? I see I have one:

Does that mean I should leave master alone and just use that branch? If so perhaps it could make it the default branch using github settings (I don't seem to have access to that part of the Ui for this repo)? But if we are using that branch I am not clear on the purpose of "master" then - maybe it's to avoid a force push or something?


No, that branch is for the current state of JTA as it was in Java EE 8. 
Correct me Dmitry, but while e.g. the groupId must change in BOTH branches (also EE4J_8) the version for completely unchanged code may and should also be the same as it was, therefore 1.3, like https://search.maven.org/artifact/javax.transaction/javax.transaction-api/1.3/jar (seems it was published from the EE4J_8 branch already in 2018?) 

If minor errata or bug-fixes occur before Jakarta EE 8 gets released, that branch sounds like the right one to do e.g. a 1.3.1 or 1.3.2 build, hence leaving the master branch (targetting Jakarta EE .next presumably 9 or similar) on 1.4 as will be the next Spec sounds like the best thing to do.

EE4J_8 does not require any new Spec, it's identical to whatever you had in Java EE 8 or before.

HTH,
Werner
 

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

Back to the top