| Re: [jakarta.ee-spec.committee] [External] : Re: Update proposal for JESP |
As I understand it, the BoD is considering the version that is
checked in under version_1.3, and the red-line comparison draft,
today. I do not know the results of that meeting.
-- Ed
I know we had feedback on the JESP that had not been addressed and said so at the board meeting, so we were not considering the 1.3 a done deal yet. Did the board vote to approve this draft as final?
On Wed, Oct 20, 2021 at 8:32 PM Ed Bratt <ed.bratt@xxxxxxxxxx> wrote:
_______________________________________________Hi there,
The Eclipse Foundation Specification Process (EFSP) revision for 1.3 has been taken to the Eclipse BoD. I wasn't aware that this work had advanced to that point but here we are. Wayne has been keeping a red line change draft comparing v1.2 to the draft 1.3 is here. The text for EFSP 1.3 is sourced from the EFSP Repository and is in the version_1_3 branch. I believe the goal was to track all substantive changes via issues against this repository.
As a reminder, The Jakarta EE working group has a specialized specification process document, the Jakarta EE Specification Process (JESP). Our JESP adheres to EFSP 1.2.
I'm not aware of anything forcing us to take quick action, but I think we should start preparing for a revision of the JESP. While version 1.3 of the EFSP has not yet been adopted as I compose this message, I expect the current draft, or something close to it will be adopted soon.
According to the process, the Spec. committee is responsible for generating proposed revisions to the JESP -- Draft proposals that we must approve by at least a super-majority threshold -- after which the proposed draft is taken up by the Steering Committee for a similar, super-majority vote.
The JESP is sourced from the JESP repository. JESP 1.2 has served us for a couple of years. There are a few issues logged, that could be addressed for this update. We may want to consider new text, if there are changes in EFSP 1.3 that we would like to preserve in the JESP. Wayne provided the revision effort for 1.2, but I suspect he will prefer that we do that work from the committee this go-around.
I propose we start the process by taking input -- primarily by working through issues on the JESP repository -- with the express goal of releasing a JESP 1.3. We should consider both the existing issues and creating new ones if needed -- and that the goal of this effort be to adopt the EFSP 1.3 update. As a prelude to any input you might like to provide, I'd recommend all the members review the updated EFSP.
Please respond with your reactions, comments, suggestions.
Paul, we probably will want to allocate time at one or more committee meetings to discuss this.
Thanks,
-- Ed
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
_______________________________________________ jakarta.ee-spec.committee mailing list jakarta.ee-spec.committee@xxxxxxxxxxx To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee__;!!ACWV5N9M2RV99hQ!ZF1wOjpBSj00p-DwLikWbKq7vhyKv6XjpCQrxsVLYdDOpENiJ9JJ_ymTXTXMuI8$