You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Greg Mann <gr...@mesosphere.io> on 2018/03/27 17:49:51 UTC

1.6 Release Manager

Hey folks,
I'd like to volunteer to manage the 1.6 release. AlexR has kindly offered
to help me through the process, since this is my first time. Thanks Alex!

It seems like we're converging on a quarterly release cadence in the email
thread on that topic, so I'll tentatively plan on a release date of May 8,
which is 3 months after the 1.5 release on Feb. 8. Looking ahead to that
time, I'll be unavailable on May 1st and 2nd, so I may wait until May 3rd
to cut the first RC. This means we would hit the May 8 target if all goes
well with that RC, or release shortly thereafter if we find some issues.

If you have any feedback on this projected timeline and how it might impact
you or your organization, please let me know!

Cheers,
Greg

Re: 1.6 Release Manager

Posted by Vinod Kone <vi...@mesosphere.io>.
I would suggest to shoot end of April for the first RC, given our history of first rc rarely being the final rc. 

Sent from my phone

> On Mar 27, 2018, at 10:49 AM, Greg Mann <gr...@mesosphere.io> wrote:
> 
> Hey folks,
> I'd like to volunteer to manage the 1.6 release. AlexR has kindly offered
> to help me through the process, since this is my first time. Thanks Alex!
> 
> It seems like we're converging on a quarterly release cadence in the email
> thread on that topic, so I'll tentatively plan on a release date of May 8,
> which is 3 months after the 1.5 release on Feb. 8. Looking ahead to that
> time, I'll be unavailable on May 1st and 2nd, so I may wait until May 3rd
> to cut the first RC. This means we would hit the May 8 target if all goes
> well with that RC, or release shortly thereafter if we find some issues.
> 
> If you have any feedback on this projected timeline and how it might impact
> you or your organization, please let me know!
> 
> Cheers,
> Greg