Skip to first unread message
Kevin Sutter
Jun 27, 2019, 1:56:35 PM6/27/19
to Eclipse MicroProfile
Hi,
This post is really meant for John Clingan and Edwin Derks since they have volunteered to head up the next release of MicroProfile 3.1 in October. But, we might as well do the "education" publicly so that others might learn along the way. Also, part of this exercise is for John and Edwin to not only validate the instructions we currently have, but to also augment these instructions where they are lacking.
To start off, most of our release processing is documented on this wiki page:
Although we are focused with the Platform release, I know the Emily and Nathan have learned a few things with preparing for the Reactive Messaging 1.0 and Context Propagation 1.0 releases (scheduled for July 9). Some of the instructions for standalone releases were found elsewhere in the wiki. It would be nice to try to organize the material so that an eventual release manager could follow one wiki path for standalone and another path for platform release. Just thinking out loud...
Back to the Platform release... Some of you may have noticed I already put the key dates on the MicroProfile calendar:
Look at Sept and Oct for the key dates for the Component pieces as well as the Platform release. I give some wiggle room on these deadlines to allow for unforeseen circumstances. For example, I always give two weeks for the release review to occur. If all the stars line up, this can probably be done in 10 days to 1 week, but I don't like to push my luck with the Eclipse processes. I also target the first Eclipse review each month (1st Wed of the month), which allows for a slip to the 3rd Wednesday if there's a hiccup. To be honest, I'm not sure how much of this is documented. I'm just typing off the top of my head for this note.
John has already started discussing the content of the 3.1 release on our bi-weekly hangouts. This is good. This needs to be brought up on every hangout to ensure that everyone knows what is happening. Also, if some Components are not attending our hangouts (ie. OpenAPI...), we should be attempting to ping them so that neither party is surprised by a proposed Release and its content.
Hope this helps get us started. If we want or need to track some of this via an Issue, that's fine. But, since we're only updating a wiki, I don't think an Issue is necessary. I'll let John and Edwin decide. I'm sure you all have opinions on this process, but let's let John and Edwin decide what works for them since they are the ones on the hook. Thanks!
Good luck,
Kevin
John Clingan
Jun 29, 2019, 9:03:38 AM6/29/19
to Eclipse MicroProfile
Thanks Kevin. At first I was thinking we could slip it two weeks and target closer to EclipseCon Europe for an announcement, but I remember last year's discussion about the December break and not having as much time to work on specs. So, dates look good.
I'd like all spec teams to come to the next Live Hangout with a confirmation of whether or not they plan to deliver a release. After that, we can create an official release plan. Config, Metrics and "maybe" Health check are what we have so far.
On Thursday, June 27, 2019 at 10:56:35 AM UTC-7, Kevin Sutter wrote:
Hi,This post is really meant for John Clingan and Edwin Derks since they have volunteered to head up the next release of MicroProfile 3.1 in October. But, we might as well do the "education" publicly so that others might learn along the way. Also, part of this exercise is for John and Edwin to not only validate the instructions we currently have, but to also augment these instructions where they are lacking.To start off, most of our release processing is documented on this wiki page:Although we are focused with the Platform release, I know the Emily and Nathan have learned a few things with preparing for the Reactive Messaging 1.0 and Context Propagation 1.0 releases (scheduled for July 9). Some of the instructions for standalone releases were found elsewhere in the wiki. It would be nice to try to organize the material so that an eventual release manager could follow one wiki path for standalone and another path for platform release. Just thinking out loud...Back to the Platform release... Some of you may have noticed I already put the key dates on the MicroProfile calendar:
Reply all
Reply to author
Forward
0 new messages