Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] [External] : Jakarta NoSQL

Taken directly from the EFSP: "No formal reviews are required for a Milestone build". 
 https://www.eclipse.org/projects/efsp/?version=1.2#efsp-milestones 

This means, in clear text: 
- You CAN release a Milestone WITHOUT a review
- You MUST do a Milestone build when you want to do a Progress Review

I think this whole discussion clearly shows that we need a simplified guide for specification project teams (similar to the JCP Spec Lead Guide).

Ivar

On Thu, Mar 4, 2021 at 9:32 AM Werner Keil <werner.keil@xxxxxxx> wrote:

Maybe a better example you know best is this release tag:

https://github.com/eclipse-ee4j/mvc-api/releases/tag/2.0.0.M1

 

Did we or anybody do a Progress review there or just vote on the Final 2.0.0?

 

Not sure, if everything would have to be phrased exactly like below, but to me it sounds like the EFSP might need small change for that because the whole review section is not specific to the JESP.

 

Werner

 

 

Von: Ivar Grimstad
Gesendet: Donnerstag, 4. März 2021 08:53
An: Jakarta specification committee
Betreff: Re: [jakarta.ee-spec.committee] [External] : Jakarta NoSQL

 

Don't complicate it, Werner :)

GlassFish is not a specification, hence none of this discussion applies to it. GlassFish follows the Eclipse Development Process, as all Eclipse projects do.

 

Regarding updates to the Jakarta EE Specification pages, I think we can summarize as follows:

 

Updates to the Jakarta EE Specification pages (https://jakarta.ee/specifications/) should not be done unless:

- it is done in association with a review from the Specification Committee (creation, plan, progress, release), or

- it is fixing an obvious error (like a wrong link, or misspelling, etc.), or 

- it is adding a new compatible implementation

 

Anything I am missing?

 

Ivar

 

 

On Wed, Mar 3, 2021 at 7:44 PM Werner Keil <werner.keil@xxxxxxx> wrote:

 

On Wed, Mar 3, 2021 at 7:22 PM Werner Keil <werner.keil@xxxxxxx> wrote:

Ivar,

 

Thanks for the clarificaiton, hope David is a bit less confused now because he asked at least once about Ballots for prereleases.

 

No worries :)

 

What David is talking about is Progress Review. 

Progress Review is defined by the EFSP and is a means for the project team to get feedback from the specification committee that they are on the right track as well as show the specification committee that they are making progress. There is a ballot associated with a Progress Review.

We haven't had any specification doing a Progress Review yet, so this could be an opportunity to set the standard for what we should expect for a progress review.

 

Ivar

 

 

>The timing of a Progress Review must coincide with the staging of a Milestone Build which must be delivered to the PMC and the >Specification Committee before the start of the Review.

sounds pretty clear to me

 

While Alpha or Beta Releases such as this B3 might do a Progress Review, the first Progress Review that must happen would be a M1 or beyond (can’t remember if we also did that for Glassfish btw for Milestones like https://github.com/eclipse-ee4j/glassfish/releases/tag/6.0.0-M1 or https://github.com/eclipse-ee4j/glassfish/releases/tag/6.0.0-M3-2020-10-04 ?)

 

Werner

 

 

Werner

 

 

Von: Ivar Grimstad
Gesendet: Mittwoch, 3. März 2021 18:48
An: Jakarta specification committee
Betreff: Re: [jakarta.ee-spec.committee] [External] : Jakarta NoSQL

 

Werner, I honestly don't know what you are talking about here. 

If I should guess, it may be that I pointed out on the mailing list that you normally don't need a release review to release a alpha, beta, or RC. For a final release of the spec, you MUST go through a release review with the specification committee. 

This is not what we are talking about here. The topic is whether these updates can be done to the specification page without a progress review. And if it even is right to make these updates as Ed pointed out.

 

Ivar

 

On Wed, Mar 3, 2021 at 6:41 PM Werner Keil <werner.keil@xxxxxxx> wrote:

According to Ivar there isn’t until the project was to publish a Final release.

 

Except for the Proposed Final Release that also matches everything the JCP did (not in the EC lately so not sure, if something like an Early Draft Ballot now exists, but earlier it didn’t, only renewal Ballots but that AFAIK also is not something the JESP defined yet, of Course there are also no penalties for some members who miss the calls for 9 or 12 months in a row ;-/)

 

Werner

 

Gesendet von Mail für Windows 10

 

Von: David Blevins
Gesendet: Mittwoch, 3. März 2021 18:37
An: Jakarta specification committee
Betreff: Re: [jakarta.ee-spec.committee] [External] : Jakarta NoSQL

 

On Mar 3, 2021, at 8:40 AM, Werner Keil <werner.keil@xxxxxxx> wrote:

 

There are no ballots until either of these specs is final.

 

I'm confused.  Are you saying there is no such thing as a Progress Review ballot in the JESP or simply that the project does not want to do a Progress Review ballot?

 

 

-David

 

 

_______________________________________________
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


 

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation

Eclipse Foundation - Community. Code. Collaboration. 

 

_______________________________________________
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


 

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation

Eclipse Foundation - Community. Code. Collaboration. 

 

_______________________________________________
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


 

--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation

Eclipse Foundation - Community. Code. Collaboration. 

 

_______________________________________________
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


--

Ivar Grimstad

Jakarta EE Developer Advocate | Eclipse Foundation

Eclipse Foundation - Community. Code. Collaboration. 


Back to the top