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:
Here:
I understand that it’s complicated to find all these documents. We need to have a normal wiki somewhere where all committers have access. 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?
You should do the groupId change in both branches. EE4J_8 is what will be used in the first Eclipse Glassfish release. The idea was to limit a number of changes there to only critical bug fixes and dependency changes. In light of this, I am not sure that it’s a good idea of making it the default branch.
In your case the version should be 1.3.1
Thanks, Dmitry
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@xxxxxxxxxxxTo 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 listee4j-build@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/ee4j-build
|