Closed apastsya closed 7 years ago
Comment created by pcurran:
We discussed this at the April 2015 EC meeting. From the minutes:
"Patrick pointed out that Bill Shannon had recently filed a new issue suggesting a light-weight proposal for producing errata. (See JSR358-96 - Create an errata process separate from the MR process).
Such a process would be very restrictive of what could be changed. He also noted that the current Process Document language mandates that binary compatibility must not be broken.
Members agreed that under these circumstances no further clarification will be needed."
I will therefore close this as "Will Not Fix".
Comment created by pcurran:
See my recent comment.
Issue was closed with resolution "Won't Fix"
Jira issue originally created by user pcurran:
Section 5 of the Process Document is ambiguous about what is appropriate for a MR and what should go into a new JSR. Should we tighten up this language?
NOTE: Maintenance Leads are generally opposed to tighter requirements and want the freedom to make the determination themselves.