Re: [jakarta.ee-spec.committee] [BALLOT] Jakarta EE Specification Versio

[Andrew Pielage <andrew.pielage@xxxxxxxxxxx>]

Yep you’re correct, it’s an oversight from us changing the behaviour and not updating it in all respective locations.

 

I have suggested amendments.

 

Thanks!

--

Andrew Pielage
Senior Software Engineer

 

From: jakarta.ee-spec.committee <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> On Behalf Of Emily Jiang via jakarta.ee-spec.committee
Sent: Monday, September 4, 2023 5:47 PM
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Cc: Emily Jiang <EMIJIANG@xxxxxxxxxx>
Subject: Re: [jakarta.ee-spec.committee] [BALLOT] Jakarta EE Specification Versioning, Change, and Deprecation Process Update

 

Since I missed last Spec call, I went through the doc once more. I noticed one conflicting statement when talking about transiting a feature from mandatory to optional.

 

On page 4 under Component Specification

Component Feature

Changes to Component features follow this versioning strategy:

• Major version change - removal of an optional or mandatory feature, or the transition of an existing mandatory feature to being an optional one.

 

Later on, the doc has:

As noted above, the transition of the feature to being optional would mandate a minor release, and the removal of it would mandate a major one.

 

and later the example also builds on the minor change statement.

 

The Component specification transitions the feature to being an optional one in release 2.1 and marks it for removal. 

• A Component specification defines a mandatory feature in release 2.0 and this is included in the Platform specification release X. 
• The Component specification transitions the feature to being an optional one in release 2.1 and marks it for removal. 

 

I think transition of an existing mandatory feature to being an optional one is a major version change. The first statement was correct, and the following ones should be updated to be consistent. Andrew, can you confirm?

 

 

Thanks

Emily
================
Emily Jiang

Java Champion, Fellow of BCS

STSM, Jakarta and MicroProfile Architect @IBM

Liberty Cloud Native Architect & Advocate

 

E-mail: emijiang@xxxxxxxxxx
Twitter: @emilyfhjiang

LinkedIn: https://www.linkedin.com/in/emilyfhjiang/

 

---

From: jakarta.ee-spec.committee <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> on behalf of Ivar Grimstad via jakarta.ee-spec.committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Sent: 03 September 2023 07:13
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Cc: Ivar Grimstad <ivar.grimstad@xxxxxxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [jakarta.ee-spec.committee] [BALLOT] Jakarta EE Specification Versioning, Change, and Deprecation Process Update

 

+1 (PMC) Ivar On Fri, Sep 1, 2023 at 2: 34 PM Kenji Kazumura (Fujitsu) via jakarta. ee-spec. committee <jakarta. ee-spec. committee@ eclipse. org> wrote: +1 (Fujitsu) -Kenji Kazumura From: jakarta. ee-spec. committee <jakarta. ee-spec. committee-bounces@ eclipse. org>

ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

This message came from outside your organization.

Report Suspicious

 

 

ZjQcmQRYFpfptBannerEnd

+1 (PMC)

 

Ivar 

 

On Fri, Sep 1, 2023 at 2:34 PM Kenji Kazumura (Fujitsu) via jakarta.ee-spec.committee <jakarta.ee-spec.committee@xxxxxxxxxxx> wrote:

+1 (Fujitsu)

 

-Kenji Kazumura

 

From: jakarta.ee-spec.committee <jakarta.ee-spec.committee-bounces@xxxxxxxxxxx> On Behalf Of Andrew Pielage via jakarta.ee-spec.committee
Sent: Tuesday, August 29, 2023 1:10 AM
To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Cc: Andrew Pielage <andrew.pielage@xxxxxxxxxxx>
Subject: [jakarta.ee-spec.committee] [BALLOT] Jakarta EE Specification Versioning, Change, and Deprecation Process Update

 

Greetings Jakarta EE Specification Committee,

 

I request your vote to approve and ratify the update to the requirements & guidelines regarding versioning and compatibility requirements for Jakarta EE specifications.

 

The relevant materials are available here:

• Original compatibility requirements: https://jakartaee.github.io/jakartaee-platform/CompatibilityRequirements
• Google doc with updated requirements & guidelines: https://docs.google.com/document/d/1d49zY05ZBqUp3Jqe_bPpYf9HU8GBbvXF

 

This will be a fourteen-day ballot, ending on Monday, September 11, 2023, that requires a super-majority positive vote of the Specification Committee members.

Please respond with +1 (positive), 0 (abstain), or -1 (reject). Any feedback that you can provide to support your vote will be appreciated.

 

Thanks,

--

Andrew Pielage
Senior Software Engineer

		payara.fish
		+448005385490

Try our fully managed cloud native application runtime. 15 day trial available. Payara.cloud

Payara Services Ltd., Registered office: Malvern Hills Science Park, Geraldine Road, Malvern, WR14 3SZ, United Kingdom
Registered in England and Wales: 09998946 | VAT: GB 193854467

Payara is a proud recipient of the prestigious Queen's Award for Enterprise: International Trade 2021

 

_______________________________________________
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

 

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation Eclipse Foundation - Community. Code. Collaboration. 

Unless otherwise stated above:

IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU