Scott –
Would you be available to attend the Steering Committee meeting on Tuesday in order to give a status update on Jakarta EE 10 and the release date or release date scenarios?
Tanja will add you to the invite.
Thanks
Will
From: "jakarta.ee-spec.committee" <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> on behalf of David Blevins <dblevins@xxxxxxxxxxxxx>
Reply-To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date: Wednesday, April 20, 2022 at 1:36 PM
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Subject: [External] : [jakarta.ee-spec.committee] Freeze Date (Re: Agenda for the April 20th Jakarta EE Specification Committee call)
Picking up on Scott's comments here and the brief discussion the call.
We need to establish and evolve the concept of a freeze date. There needs to be a date by which, in spirit, all specification work is complete, considered frozen and implementations are the only remaining obstacle. In practice, there
will still be the need to address TCK challenges. The release date would be planned to be some number of weeks after the freeze date. If the freeze date moves, the release date moves by the same amount.
In practice, things will still be messy by the time the freeze date comes. As the messes begin to show, we can evaluate each one and ask ourselves "do we think where this thing is at is is in spirit of where we should be by a freeze date?"
If the answer is no, then we have to either push the freeze date (and therefore the release date) or we cut the spec from the release if that's possible.
What this does is allow us to be honest about where we are and know a few weeks in advance if our release date is going to get pushed.
From what I heard today, we're at least a month out and have not yet reached what I would call a freeze date (specs and TCKs are not yet frozen). Our release date is going to get pushed. Before we communicate a new timeline, we should
decide two dates; a freeze date and subsequent release date.
One item to discuss is whether there needs to be more emphasis on producing public milestone releases of spec project API jars (released to maven central) in the process guide. Some project do not want or cannot
incorporate a staging repository into their build process and the lack of maven central artifacts has slowed down updating implementations and testing of the TCKs.
The agenda for our committee call on Wednesday at 16:00 UTC is here.
Please add any other business items as required.
Please be prepared to discuss the readiness for ballot of the
specs you mentor. Component specs need to be in ballot no later than May 1st.
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
