2019 Release Schedule Logistics (especially MicroProfile 2.2 in Feb)

[Kevin Sutter]

Hi,

Earlier this year, we as a community decided that we should plan on three releases in 2019.  These release dates were selected so as to match up with the Spring, Summer, and Fall conference schedules -- Feb 1, Jun 1, and Oct 1.  This approach also got us out of the "bad" habit of releasing in December, which is extremely hard to accomplish due to holidays and vacations.

But, as I look at the Feb 1 release date for MicroProfile 2.2, I'm wondering about the doability of this exercise.  If we want to release on Feb 1, there are two Eclipse Release Review dates available in January -- Jan 2 and Jan 16 (the first and third Wednesday of each month).  To be ready for a Release Review, the Spec, API, and TCK need to be completed.  Yes, there can be tweaks due to RC drivers and reviews, but for the most part, everything should be done by the time you submit for a Release Review.  Although we only release the TCK, we have also indicated that a Compatible Implementation needs to be available to verify that the Spec is implementable and the TCK works as expected.  Thus, some type of open-source implementation of each component release needs to be ready by mid January at the latest.

Is this doable?  Currently, the MicroProfile 2.2 release looks to contain several component releases (Fault Tolerance, Open API, Config, etc).  I know we still have some time, but I'm trying to be realistic.  When we talk about a Feb 1 for MicroProfile 2.2 and it's components, we're really looking at a late December or early January completion date for all of the artifacts to allow time for a proper review.

So, my questions are...

• When we discussed Feb 1, Jun 1, and Oct 1, were those the expected dates?
• Or, did we mean more general dates like the months of Feb, Jun, and Oct?

If it's the former, then we have a lot of work to do before the end of the year to be ready for MicroProfile 2.2.  If it's the latter, then we have a bit more breathing room, but it's still tight. 

I wanted to get this conversation started before our next Hangout on the 27th.  Let's start the discussion via this thread and, hopefully, we can come to some conclusions on the 27th.

Thanks,

Kevin

[Emily Jiang]

Good questions.

I think we should aim for the dates we defined (first day of Feb, Jun or Oct). If someone somehow asks for a few days last minute delay, I think we should be a bit flexible. We normally aim for Month release instead of Date release.

If we aim to release MP 2.2 on 1st Feb, the RC1 needs to be done in Jan.

My 2cents.

Emily

[Kevin Sutter]

This was discussed at yesterday's MicroProfile Hangout:  Minutes  Video

We decided the goal for MicroProfile 2.2 is an announce date of Tuesday, Feb 12 (which requires an Eclipse Release Review on Wed, Feb 06).  This gives us a buffer for any hiccups with a backup Release Review date of Wed, Feb 20, and an announcement date of Tue, Feb 26.

We also decided to use github Milestones to help track the content of these releases:

MicroProfile 2.2 (Feb 2019)

MicroProfile 2.3 (Jun 2019)

MicroProfile 2.4 (Oct 2019)

thanks,

Kevin

[Jay Balunas]

On Wed, Nov 28, 2018 at 4:48 PM Kevin Sutter <kwsu...@gmail.com> wrote:

This was discussed at yesterday's MicroProfile Hangout:  Minutes  Video

We decided the goal for MicroProfile 2.2 is an announce date of Tuesday, Feb 12 (which requires an Eclipse Release Review on Wed, Feb 06).  This gives us a buffer for any hiccups with a backup Release Review date of Wed, Feb 20, and an announcement date of Tue, Feb 26.

We also decided to use github Milestones to help track the content of these releases:

MicroProfile 2.2 (Feb 2019)

MicroProfile 2.3 (Jun 2019)

MicroProfile 2.4 (Oct 2019)

These are perfect, thanks a lot!  This makes it easy to see, share, and comment on the plans!

 

thanks,

Kevin

On Wednesday, November 21, 2018 at 4:40:42 PM UTC-6, Emily Jiang wrote:

Good questions.

I think we should aim for the dates we defined (first day of Feb, Jun or Oct). If someone somehow asks for a few days last minute delay, I think we should be a bit flexible. We normally aim for Month release instead of Date release.

If we aim to release MP 2.2 on 1st Feb, the RC1 needs to be done in Jan.

My 2cents.

Emily

On Tuesday, November 20, 2018 at 10:42:45 PM UTC, Kevin Sutter wrote:

Hi,

Earlier this year, we as a community decided that we should plan on three releases in 2019.  These release dates were selected so as to match up with the Spring, Summer, and Fall conference schedules -- Feb 1, Jun 1, and Oct 1.  This approach also got us out of the "bad" habit of releasing in December, which is extremely hard to accomplish due to holidays and vacations.

But, as I look at the Feb 1 release date for MicroProfile 2.2, I'm wondering about the doability of this exercise.  If we want to release on Feb 1, there are two Eclipse Release Review dates available in January -- Jan 2 and Jan 16 (the first and third Wednesday of each month).  To be ready for a Release Review, the Spec, API, and TCK need to be completed.  Yes, there can be tweaks due to RC drivers and reviews, but for the most part, everything should be done by the time you submit for a Release Review.  Although we only release the TCK, we have also indicated that a Compatible Implementation needs to be available to verify that the Spec is implementable and the TCK works as expected.  Thus, some type of open-source implementation of each component release needs to be ready by mid January at the latest.

Is this doable?  Currently, the MicroProfile 2.2 release looks to contain several component releases (Fault Tolerance, Open API, Config, etc).  I know we still have some time, but I'm trying to be realistic.  When we talk about a Feb 1 for MicroProfile 2.2 and it's components, we're really looking at a late December or early January completion date for all of the artifacts to allow time for a proper review.

So, my questions are...

• When we discussed Feb 1, Jun 1, and Oct 1, were those the expected dates?
• Or, did we mean more general dates like the months of Feb, Jun, and Oct?

If it's the former, then we have a lot of work to do before the end of the year to be ready for MicroProfile 2.2.  If it's the latter, then we have a bit more breathing room, but it's still tight. 

I wanted to get this conversation started before our next Hangout on the 27th.  Let's start the discussion via this thread and, hopefully, we can come to some conclusions on the 27th.

Thanks,

Kevin

--
You received this message because you are subscribed to the Google Groups "Eclipse MicroProfile" group.
To unsubscribe from this group and stop receiving emails from it, send an email to microprofile...@googlegroups.com.
To post to this group, send email to microp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/microprofile/81a9a202-205e-4641-87b8-e986b2acc3f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Pavol Loffay]

Hi, 

is the proposed date for 2.2 still valid? 

The release should include OpenTracing 1.3 which depends on Rest Client 1.2 which hasn't been released yet. I would like to ask Rest Client maintainers to leave us enough time to release OpenTracing before the overall spec.

Regards,

[Kevin Sutter]

Yes, MP 2.2 is still valid.  Rest Client 1.2 is expected to be part of that release.  The last I heard, the Rest Client team was working closely with the Open Tracing team to ensure that the requirements were being satisfied.  I suppose "closely" is left up to the beholder to define...  :-)  I'd suggest reaching out directly to Andy McCright if you have concerns...

Thanks,

Kevin

[Pavol Loffay]

Hi Kevin,

yes were working together and the integration works so far very well. My question was more related to the timing of the release. When do you want to release RC1 of the platform?

The rest client team is aiming to cut the final the week 14-20th of January https://github.com/eclipse/microprofile/issues/70. If that holds we need one week to go through RC and release final of OpenTracing spec.

[Kevin Sutter]

Hi Pavol (and everybody else planning for MP 2.2),

I had put a placeholder on our MP Google Calendar (https://calendar.google.com/calendar/embed?src=gbnbc373ga40n...@group.calendar.google.com&pli=1) for the Component releases to be completed by Jan 16.  This would allow one week buffer before we would submit the MP Platform release request to Eclipse.  If we submit the release review request by the 23rd, then that gives us two weeks before the Eclipse Review on Feb 6.  And, the MP 2.2 release would be announced the following Tuesday, Feb 12.

Given your schedule below, that doesn't give us enough time to tie up the loose ends.  If both you and Rest Client could do your final releases during the week of the 14th-18th, then we probably still have enough time to make the reviews.  Can you work with the Rest Client team to see what can be done?

Also, as a reminder to everyone...  We do have Issues created for each of the Components planning to release in February (whether you are integrated into the Platform or not).  Please try to keep these updated.  The main thing is to get the pom.xml file updated for the Platform release.  Thanks!

https://github.com/eclipse/microprofile/milestone/1

Thanks!

Kevin

[Pavol Loffay]

This is not an ideal situation given there should be one week for the community review. 

The only thing we can do to align with the schedule is to cut the RC based on the latest milestone release of the rest client and then update to the final version just for the final release of OpenTracing. What do you think Kevin? 

On Wednesday, January 9, 2019 at 3:19:44 PM UTC+1, Kevin Sutter wrote:

Hi Pavol (and everybody else planning for MP 2.2),

I had put a placeholder on our MP Google Calendar (https://calendar.google.com/calendar/embed?src=gbnbc373ga40n0tvbl88nkc3r4@group.calendar.google.com&pli=1) for the Component releases to be completed by Jan 16.  This would allow one week buffer before we would submit the MP Platform release request to Eclipse.  If we submit the release review request by the 23rd, then that gives us two weeks before the Eclipse Review on Feb 6.  And, the MP 2.2 release would be announced the following Tuesday, Feb 12.

[Kevin Sutter]

Hi Pavol,

I can't speak to the "comfort level" for this approach since this is really affected by your combined teams' efforts.  The approach sounds reasonable, but whether it's technically doable is not my call.  As long as we have the Component content ready by the 23rd, then we can submit the Review request to Eclipse.

(To be totally transparent here...  Not every single "t" has to be crossed and "i" dotted before we submit for a review.  But, the overall content of the MP 2.2 release has to be extremely close to completing.  The final Component releases should be done.  And, the RC releases for the Platform have to be under way.  If there are minor tweaks due to the Platform RC releases, those are still doable.)

Please note, all new or updated dependencies have to be identified, logged, and processed via CQs before we can finalize our Release:

https://wiki.eclipse.org/MicroProfile/3rdPartyDependencyProcess

Thanks!

Kevin

[Pavol Loffay]

I have spoken with Andy and the current plan is that our OpenTracing RC will depend on Rest Client RC which will be released this Friday. Before the final release we just change to the final version. This should give us the most up to date artifacts. 

Regards,