Bill -
This has been discussed prior to the formation of the Steering
Committee, and what Mike says was the consensus. But I don't
believe the topic has been reviewed/formalized during a Steering
Committee meeting. I think it makes sense to have the discussion
at Steering Committee and formalize the conclusion.
Will
On 5/1/18 1:23 PM, Bill Shannon wrote:
Yes, I think the numbering scheme can
be decided independently of the cadence. With choice #1, the
cadence might require you to skip some numbers.
If the steering committee already considered alternatives such
as those below and explicitly decided that the first number is
"8", that should be recorded somewhere. Is it?
My impression from those discussions was that this was never
explicitly considered and that "8" was just an informal
placeholder while we discussed more important topics. If you
think the steering committee is the group that should
decide this explicitly, I can raise this issue there.
Mike Milinkovich wrote on 5/1/18 8:22 AM:
Bill, et al,
Question: Do you think we can realistically answer this
question without knowing what the Jakarta EE release cadence
and timing is going to be? And since we are quite a ways away
from knowing that release cadence, perhaps we could defer this
decision until that time?
I *think* the Steering Committee has already decided that the
very first release of Jakarta EE will be numbered as "8". I
think that is enough to go on for at least the next six
months, is it not?
That said, I think that the discussion has been valuable.
There's lots of good ideas and information in this thread.
On 2018-04-30 5:07 PM, Bill Shannon 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:
- 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.
- 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.
- 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
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
_______________________________________________
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
|