|Re: [jakartaee-platform-dev] Clarification on versioning and what it means for breaking changes|
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.
(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
_______________________________________________ jakartaee-platform-dev mailing list jakartaee-platform-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
Back to the top