Re: [jakartaee-platform-dev] Clarification on versioning and what it mea

[Scott Stark <starksm64@xxxxxxxxx>]

Ultimately the specification committee needs to formalize requirements in the JESP. I have created an issue for that to take up in the next SC meeting. The CompatibilityRequirements page of the jakarta-platform could then be updated to provide clarifying info and context in the form of the Q/A section.

https://github.com/jakartaee/specification-committee/issues/72

https://github.com/eclipse-ee4j/jakartaee-platform/issues/605

On Jan 30, 2023 at 11:24:23 AM, Reza Rahman <reza_rahman@xxxxxxxxx> wrote:

I think platform project leads and committers should comment on whether these are in fact settled matters. Scott has already suggested updating the documentation to better reflect status quo. This feels like it is potential content for that update.

On 1/30/2023 9:46 AM, Manfred Riem wrote:

Hi all,

 

(not sure if this is the correct list. If not, please let me know)

 

As there seems to be a bit of confusion with regards to breaking changes and versioning I would like to see a

community poll, preferably binding with the following yes or no question so it is properly documented once

and for all.

 

Should the following model be the standard for any specification in the Jakarta EE process.

 

Major version change – breaking changes OK, but not actively encouraged.

Minor version change – breaking changes not OK, only allowed to fix specification bugs.

Patch version change – breaking changes not OK

 

Thoughts?

 

Thanks!

 

Kind regards,

Manfred Riem

 

_______________________________________________
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