Open Stack

This would be a more conducive option if that works out. Stable release every month and if there is an urgent need to cut a release cause of a regression, there can always be one with that particular change.

--
Ganesh

> -----Original Message-----
> From: Shinde, Archana M [mailto:archana.m.shinde at intel.com]
> Sent: Wednesday, July 24, 2019 4:31 PM
> To: Ernst, Eric <eric.ernst at intel.com>; kata-dev at lists.katacontainers.io
> Subject: Re: [kata-dev] Release cadence - propose to slow cadence?
> 
> I agree, as we are focused more on overall stability of the project now, it
> makes sense to space out the releases.
> 
> Making a major/minor release every 12 weeks sounds good to me, we can even
> push the stable release to every 4 weeks, making a stable release earlier if
> there is a end-user requirement to do so.
> 
> - Archana
> 
> ________________________________
> 
> From: Ernst, Eric [eric.ernst at intel.com]
> Sent: Wednesday, July 24, 2019 4:03 PM
> To: kata-dev at lists.katacontainers.io
> Subject: [kata-dev] Release cadence - propose to slow cadence?
> 
> 
> 
> Hey ya'll,
> 
> 
> 
> Today, we are running on a time based release schedule, making a minor
> release every 6 weeks, with stable releases made ever other week (with
> possibility of faster stable releases if issues are identified).  This was
> necessary as the project started, but as Kata matures, this adds unnecessary
> burden on release process of project infra folks as well as a shorter window
> of support for the stable branches for user.
> 
> 
> 
> I'd like to propose we slow the cadence, to every 3 weeks for stable and 12
> weeks for major/minor. TBH, I just made that cadence up as a starting point
> and would like feedback, folks!
> 
> 
> 
> WDYT?  Proposals/suggestions?
> 
> 
> 
> I'd like input from folks active in the community, and especially from end-
> users.
> 
> 
> 
> Thanks,
> 
> Eric