Re: [jakarta.ee-spec.committee] Use of jakarta.ee Specification pagesfor

["Kevin Sutter" <sutter@xxxxxxxxxx>]

That's a fair question,
Werner.  Right now, I am only concerned about the content of the Jakarta
EE 9 release.  But, if Jakarta NoSQL wanted to publish an early Milestone
(or MVC), would they follow this same process?  If we decide this
is the process for Milestone deliverables for Jakarta EE 9, then it should
apply across the board even for those Specifications not part of the Platform.

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       Werner
Keil <werner.keil@xxxxxxx>
To:
       Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:
       05/14/2020
15:44
Subject:
       [EXTERNAL]
Re: [jakarta.ee-spec.committee] Use of jakarta.ee Specification pagesfor
Milestone deliverables
Sent
by:        jakarta.ee-spec.committee-bounces@xxxxxxxxxxx

---

Would that also include Milestones like the upcoming Beta 2 of NoSQL (still Needs to be added btw, I asked Otavio if he could look into that) or similar Milestones of MVC?

 

Werner

 

Sent from Mailfor Windows 10

 

From: Kevin Sutter
Sent: Thursday, May 14, 2020 22:31
To: Jakarta EE Specification Committee Discussions
Subject: [jakarta.ee-spec.committee] Use of jakarta.ee Specification pagesfor Milestone deliverables

 

Hi,
The topic on yesterday's Spec Committee call that we didn't have time for was whether to use the jakarta.ee Specification pages for the Milestone deliverables:
https://jakarta.ee/specifications/
https://jakarta.ee/specifications/platform/
https://jakarta.ee/specifications/platform/9/

On the surface, it might sound like the logical approach, but there are a few questions...

• Do we replace the "(Under Development)" with "Milestone 1" (or something similar) on the section titles?
• Or, do we modify the bulleted links on the individual Spec pagesto read something like...?
  Jakarta EE Platform 9 Milestone 1 Specification Document
  Jakarta EE Platform 9 Milestone 1 Javadoc
  Jakarta EE Platform 9 Milestone 1 TCK(sig,sha,pub)
• We already have a handful of draft PRs for the "final" release.  And, I have been advocating for the Spec Projects to create these draft PRs.  I can redirect the story to indicate that we're going to use these Specification PRs to announce the Milestone deliverables (if we decide this is the path we want to go).
• Going this path will help solidify the instructions we were discussing on yesterday's call.  Maybe we'll get more feedback on the complexity and how we might simplify things...
• It will also be clear on what's being delivered for the Milestone and what's not...  If a Spec Project doesn't provide a PR to update their information, then it won't be published or publicized.  So, it's in their best interest to announce this to the wider community via these pages.

If you can't tell, I am in favor of going this route.  My only hesitation
is whether we'll get the participation we are looking for.  Since
I haven't received much input for the pre-creation of the Spec PRs up to
this point, I'm not sure how quickly the teams will jump on board to do
this for Milestone 1.  At least the main deliverables -- the Platform
Spec, API, TCK, and CI will be available for Milestone 1.

Thoughts or suggestions?

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter

 _______________________________________________
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