stable release cadence

stable release cadence

[Jan Beulich]

All,

on the hackathon we discussed this topic. With the rate of changes
going into the stable trees not being as high anymore as a few
years ago, we settled on trying to stick to a 4 month release
cycle going forward. Of course, issues like the currently severely
lagging osstest can always lead to delays, and we're not intending
to release not properly tested code just because the schedule
says so. But the intention is to at least initiate the process of
preparing stable releases mainly based on time, i.e. in particular
not taking into account the (possibly small) set of accumulated
changes.

If anyone is heavily objecting to this, or foresees other kinds of
problems with this scheme - please speak up soon!

Regards, Jan

Re: stable release cadence

[Lars Kurth]

> On 5 May 2015, at 16:44, Jan Beulich <jbeulich@suse.com> wrote:
> 
> All,
> 
> on the hackathon we discussed this topic. With the rate of changes
> going into the stable trees not being as high anymore as a few
> years ago, we settled on trying to stick to a 4 month release
> cycle going forward. 

+1

Lars

Re: stable release cadence

[Konrad Rzeszutek Wilk]

On Tue, May 05, 2015 at 04:44:30PM +0100, Jan Beulich wrote:
> All,
> 
> on the hackathon we discussed this topic. With the rate of changes
> going into the stable trees not being as high anymore as a few
> years ago, we settled on trying to stick to a 4 month release
> cycle going forward. Of course, issues like the currently severely
> lagging osstest can always lead to delays, and we're not intending
> to release not properly tested code just because the schedule
> says so. But the intention is to at least initiate the process of
> preparing stable releases mainly based on time, i.e. in particular
> not taking into account the (possibly small) set of accumulated
> changes.
> 
> If anyone is heavily objecting to this, or foresees other kinds of
> problems with this scheme - please speak up soon!

Just +1 on this.

Thank you!
> 
> Regards, Jan
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel