| 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 310-633-3852
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. 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@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
