Hello Community,
At today's platform call, an inconsistency in our policy for XML schemas regarding version numbers was surfaced:
-
Component specifications for EE releases have not always been updated every time a major release of EE 11 has happened.
To address this inconsistency, for EE 11, we are adopting the following rule:
-
When the version of the spec is updated, the version number and file name of the schemas must be updated to match the version number of the component specification for that EE release, even if there are no normative
changes to the XSD files themselves.
This rule is added to our existing, common-sense, but apparently not explicitly stated rule:
-
If an XSD file has normative changes during an EE release cycle, its version number and file name must be updated to match the version number of the component specification for that EE release.
I judge this is sufficiently non-controversial that I don't want to tag this with a [DISCUSS] subject, nor put it to a vote, but if someone feels strongly about it, please reply
and prepend [DISCUSS] to the Subject: and we'll go down that road.
Thanks
Ed Burns
Jakarta EE 11 release co-coordinator.
| Reply anonymously to this email:
https://purl.oclc.org/NET/edburns/contact