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
+1, Richard, with separating the Jakarta EE version from the Java SE version.  I don't think Jakarta should be tightly tied to the Java version from a naming perspective.  We can still specify a required minimum Java version for a given Jakarta version, but let's not try to correlate the version names.

But, I'm not a fan of using years in the "version name" unless we're dealing with continuous delivery scenarios.  So, my vote would be to continue with current versioning scheme and call subsequent releases as Jakarta EE 9, Jakarta EE 10, etc.  Provides continuity with Java EE naming and will continue the loyalty with the old brand.

---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:        Richard Monson-Haefel <rmonson@xxxxxxxxxxxxx>
To:        Jakarta EE community discussions <jakarta.ee-community@xxxxxxxxxxx>
Date:        05/01/2018 10:48 AM
Subject:        Re: [jakarta.ee-community] Which will be the initial Versioning Number for the first version of Jakarta EE
Sent by:        jakarta.ee-community-bounces@xxxxxxxxxxx



I think its important to show continuity with Java EE 8 by naming the first release Jakarta EE 8 but after that the Jakarta version numbers should be independent of the Java SE version numbers. I don’t want Jakarta EE release schedule to be dictated by Java SE. Also, I think its more difficult to reach concensus on Jakarta EE specifications than it is on Java SE where Oracle totally owns the process. 

We should consider using year versions as well.  Jakarta EE 8 might be the first but after that it could be Jakarta EE 2019 with a release schedule that is annual rather than every 6 months.

On Mon, Apr 30, 2018 at 4:11 PM Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
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
--
Richard Monson-Haefel
http://twitter.com/rmonson
http://www.tomitribe.com
http://www.tomitribe.io
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_jakarta.ee-2Dcommunity&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=R9dtOS3afYnRUmu_zogmh0VnVYl2tse_V7QBUA9yr_4&m=V3SuLKfPxcdLvYyudZC-irds5Qg1inL9F-NEW5g7A8w&s=UKxYPPICt7w2thRUFCsztDbirwtsQV5eg4P1n0FHex0&e=



Back to the top