search

apastsya / jcpnext4

0 stars 0 forks source link

JCPNEXT4-69: Change requirement to announce when a JSR that was previously available standalone will in future only be bundled into a platform #63

Closed apastsya closed 7 years ago

apastsya commented 9 years ago

Jira issue originally created by user pcurran:

The Process Document says:

"Technologies may be incorporated into a Profile or Platform Edition after having been initially delivered standalone. A JSR for a new version of an API that proposes to become part of a Profile or Platform Edition and is considering discontinuing standalone availability must state the rationale for this change and must inform the public of the intention to discontinue the availability of the standalone RI, and TCK one JSR submission in advance."

This implies that if the relevant JSR is at version X, the change should be announced when JSR X1 is submitted. That version must be included in the next version of the platform, but no standalone version need be released with the following version of the platform.

This seems unnecessarily rigorous. I propose that we change "one JSR submission in advance" to "one JSR release in advance".

This would permit the announcement to be made when X1 is released rather than submitted ("this is the last release of the platform for which JSR foo will be available standalone").

apastsya commented 9 years ago

Comment created by pcurran:

Fixed in version 8 of the revised Process Document

apastsya commented 9 years ago

Issue was closed with resolution "Fixed"