Re: [jakartaee-platform-dev] [jakarta.ee-spec] Jakarta EE Versioning, Ch

[Jan Westerkamp <jan.westerkamp@xxxxxxx>]

Hi,

I really appreciate moving closer to true Semantic Versioning (semver) and many thanks for the draft work!

But I have some concerns:

Why we want to handle umbrella specs (Jakarta Platform) differently?
What's the reason we expect not to have Patch Releases for Jakarta Platform - how we fix things like CVEs, the current dependency or JPMS issues?

How we support older versions of specs in general?

How is the braking change handled that raises from changing up the Java SE minimum version to build and run a component specs (there is a definition on the Platform spec)?

How do we handle the fact, when there is no maintenance at all on a component spec (lack of resources) but maintenance is required? If nobody wants to spend resources on it, we might need to remove it immediately from the next platform release instead waiting two releases (can take 4 years) and may be deliver broken versions or delay the Platform release until somebody spends some time on it.

In general, why we do not agree to do follow Semantic Versioning where possible, while adding that we try to prepare Users for breaking changes - may be with Patch level releases on the Platform if necessary.

I asked for the right to comment on the original document - I can add my concerns then there for further discussion too.

Best,

Jan

Am 01.08.23 um 20:05 schrieb lenny--- via jakartaee-platform-dev:

LGTM! Great job!

On Aug 1, 2023, at 2:50 AM, Emily Jiang via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:

Just forward this thread to the platform mailing list to get more attention. Feedback is welcome.

Thanks

Emily

---------- Forwarded message ---------
From: Andrew Pielage via jakarta.ee-spec <jakarta.ee-spec@xxxxxxxxxxx>
Date: Thu, Jul 20, 2023 at 4:45 PM
Subject: [jakarta.ee-spec] Jakarta EE Versioning, Change, and Deprecation Process
To: Jakarta specification discussions <jakarta.ee-spec@xxxxxxxxxxx>
Cc: Andrew Pielage <andrew.pielage@xxxxxxxxxxx>

Hello all,

 

Kicked off after it was pointed out that there was a desire for change to the Backwards Compatibility Requirements for Jakarta EE specifications, along with some calls to define a versioning system (semantic or otherwise), the Specification Committee has been working on an updated process to define all of this.

The draft proposal we’ve produced covers how versioning for the Platform and Component specifications will be done, and how features can be deprecated or changed in a breaking manner.

 

We would like to invite you to review and provide feedback against the draft proposal which can be found here: https://docs.google.com/document/d/1d49zY05ZBqUp3Jqe_bPpYf9HU8GBbvXF/edit?usp=sharing&ouid=116336929537635035739&rtpof=true&sd=true

 

Thanks,

--

Andrew Pielage
Senior Software Engineer

<image001.png>

<image002.png>

<image003.png>

	<image004.png>	payara.fish
	<image005.png>	+448005385490

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 mailing list
jakarta.ee-spec@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec

--

Thanks
Emily

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev

_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev