Re: [jakarta.ee-spec.committee] EFSP 1.1

[Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>]

I've applied the changes that we discussed.

Service releases now require a release review.

To avoid confusion, I've changed the statement that the first release must be a Major release to instead state that the first release must be a Major or Minor Release.

I've used the term "ballot" instead of "vote". 

I added note that states:

The notions of Major, Minor, and Service Release bear a close resemblance to the "MAJOR.MINOR.PATCH" structure described by the Semantic Versioning specification. While a Specification Team may opt to use Semantic Versioning when naming their releases, this process imposes no requirement to do so. Further, this process imposes no requirement to tie any particular type of Release to any particular Semantic Versioning scheme.

I added an escape hatch that permits "minor corrections" to be effected during a Specification Committee ballot and added a corresponding entry to the "knobs and dials" document to encourage a specification committee to determine how to determine whether or not a change impacts the semantic intent of the Specification.

I've attached the PDF. The comparison link that I gave previously compares the top of the version_1_1 branch, so it will still work.

I have issues opened for each of the changes that I'm working into this version.

Comments welcome.

Wayne

On Mon, Mar 4, 2019 at 10:55 PM Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx> wrote:

I've completed my pass of updates to the EFSP. Attached is a draft PDF of version 1.1. Note that there is some odd formatting in the "Open Source Licenses" definition; this isn't rendered in the HTML (and we don't currently distribute the PDF). 

I added a "History" section at the end of the document.

You can see the file-by-file, line-by-line changes here: compare with version 1.0.

We had originally hoped to get a vote to approve on Wednesday of this week, but there clearly isn't enough time for that. Let's defer that vote to our next call (March 13/2019).

In the meantime, if you have any concerns regarding the changes that I've made, please let them be known. You can post them here, comment on existing GitHub issues, or open a new issue.

Thanks,

Wayne

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Attachment: efsp.pdf
Description: Adobe PDF document