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

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Exactly, David!  Just
trying to get this idea of the PRs for updating the Spec pages ingrained
in the developers' heads will help in the long run.

>  - Initial Creation or Plan Review: here's a PR with our basic metadata

Separate topic,
but...  this was part of the conversation on this week's meeting that
I didn't agree with.  I don't think that the Creation Review should
also cover a Plan Review.  I think they need to be completely separate
since we don't know the exact plans for a project when it's getting created.
 The Creation Review should be used to discuss whether we want to
even entertain the inclusion of said Project in Jakarta EE.  There
may be some existing work associated with a Spec Project proposal, or it
may be a brand new idea.  We shouldn't assume that a release plan
is understood at the time of a Creation review.  When the Plan Review
is held, then that's a perfect time to request an initial PR for the Spec
pages.

---------------------------------------------------
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:
       David
Blevins <dblevins@xxxxxxxxxxxxx>
To:
       Jakarta
specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx>
Date:
       05/15/2020
12:23
Subject:
       [EXTERNAL]
Re: [jakarta.ee-spec.committee] Use of jakarta.ee Specification pages for
Milestone deliverables
Sent
by:        jakarta.ee-spec.committee-bounces@xxxxxxxxxxx

---

One thing that didn't really come up
in our discussions, but I think is a good point to raise.

If we are properly updating these pages
throughout the process there would be considerably less work at the end.
 It might look something like this:

 - Initial Creation or Plan Review:
here's a PR with our basic metadata

 - Milestone Review: here's a PR
to add download links

 - Final Review: here's a PR to
update our links and add a certified implementation

I think what we
know as developers stands here too: a lot of little PRs is easier than
one big PR.

-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com
310-633-3852

On May 15, 2020, at 7:37 AM, Scott Stark
<sstark@xxxxxxxxxx>
wrote:

Ok, so I'll create a draft PR for dependency
injection today. Needing that to be more final is what has led to me not
creating this earlier, so that will also help to show more progress on
specs as well.

On Fri, May 15, 2020 at 9:26 AM Kevin
Sutter <sutter@xxxxxxxxxx>
wrote:
Yes, Scott.  Basically,
we might have multiple revisions of these "draft" PRs as we progress
through this release.  We're now talking about a "Milestone 1
PR".  If this drags on, maybe we will have to talk about a "Milestone
2 PR" before we finally create the "Final Release PR".  The
"draft" aspect was to let people know that these were not ready
to be merged yet.  We can still use and promote the "draft PR"
github mechanism as we are creating these "Milestone 1 PRs".

All of this may require some updates to our Ops guide...

---------------------------------------------------
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
_______________________________________________
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