Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-community] Which will be the initial Versioning Number for the first version of Jakarta EE
On Tue, 1 May 2018 at 07:34, Yordan Nalbantov <iordannalbantov@xxxxxxxxx> wrote:
Hello,

My personal opinion is that the $major.$minor.$security scheme is good because of the reasons described here http://openjdk.java.net/jeps/223

Jakarta EE is a specification, not an implementation, so it doesn't make sense to apply the same versioning as you would to an implementation. For example specifications don't have patch/security releases, since patch/security releases don't change any interfaces, but a specification is nothing but an interface so it's logically impossible for Jakarta EE to have patch/security releases.

JEP 223 is talking explicitly about the versioning applied to implementations of the JDK, specifically OpenJDK and OracleJDK, not the Java specification itself - that's still a single number, eg 8, 9 etc. So I don't think JEP 223 is relevant here. It may make sense to adopt that versioning scheme for an implementation, such as Glassfish, but for the Jakarta EE specification.

Also alignment of the Major number with the Java SE that is the primary compatibility requirement for Jakarta EE is logical.

Kind regards,
Yordan Nalbantov


2018-05-01 0:07 GMT+03:00 Bill Shannon <bill.shannon@xxxxxxxxxx>:
I think we've been using "8" or "8.0" as an informal way of indicating that it will be compatible with Java EE 8, but I think we should make an explicit decision about how to do version numbering for Jakarta EE once we have the right group in place to make that decision.  I'm not clear on whether that would be the Steering Committee, the Specification Committee, or the Jakarta EE Platform project.

Once we're clear on who gets to make the decision, I see three obvious choices:
  1. Continue the Java EE version numbering approach with Jakarta EE X being based on Java SE X, for all values of X.  With the new rapid release cycles of Java SE, that might mean skipping some version numbers to allow Jakarta EE to stay in sync with Java SE.
  2. Start with Jakarta EE 8 and increment the version number for each release, making a separate and explicit decision as to what version of Java SE to base each release on.
  3. Since so much of Jakarta EE is a break from the past, start over with Jakarta EE 1, incrementing the version number for each release.

Independently of the above is the decision of whether or not to use minor version numbers, and if so for what purpose.



Dmitry Kornilov wrote on 04/30/18 03:53 AM:
8.0

— Dmitry

On 30 Apr 2018, at 12:28, Alexander Salvanos <salvanos@xxxxxx> wrote:

Hi everybody,
 
So far, we had agreed that the first version of Jakarta EE should technologically be conform to the state of Java EE 8 technologies and no further additions should be added. Is this still the plan? And if we so, what version number should we use for this initial version of Jakarta EE? Currently, I was thinking it will be Jakarta 1.0. But, in the email conversion Jakarta 8.0 appeared as well.
 
Best Regards,
Alex
 
 
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community



_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community


_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community




--
Best regards,
Yordan Nalbantov
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community


--
James Roper
Senior Octonaut

Lightbend – Build reactive apps!
Twitter: @jroper

Back to the top