[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jakartaee-platform-dev] Issue with a quick Jakarta EE 9 name change only release
- From: Scott Stark <starksm64@xxxxxxxxx>
- Date: Fri, 10 May 2019 15:08:44 -0700
- Delivered-to: email@example.com
Right and Alasdair pointed out it does not make much sense to have an unsupported spec release. The notion is really more of how to work through the discontinuity that the Jakarta 9 release will bring about from the perspective of implementing new features and the tooling around this.
> On May 10, 2019, at 2:26 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:
> Yes, changing all the names will be a huge amount of work for any implementation. And do we really want to release Jakarta EE 9 without an implementation of the compatibility profile (assuming we define such a thing)? There's a bunch more work.
> Scott Stark wrote on 5/10/19 6:41 AM:
>> In discussing some of the suggested options and timelines that have been suggested, a question about how we could actually accomplish a quick Jakarta EE 9 name change only release arose due to the fact that any release requires at least one compatible implementation. Working through the name and resource handling in a given server might not be a huge effort, but getting the associated TCKs worked through and passing is most likely going to add a significant amount of time to even a simple name change only release.