release cadence and channels for the ubuntu-core snap

[Jamie Strandboge]

On Tue, 2016-03-08 at 09:32 -0600, Leo Arias wrote:
> On 2016-03-08 09:21, Jamie Strandboge wrote:
> > 
> > FYI, there was wide agreement between teams (including Snappy
> > Core) that the stable promotion should correspond with the Ubuntu
> > kernel cadence, which is every 3 weeks.
> mvo mentioned that, but I understood we could change it this new
> cycle. We can easily make it every 3 weeks. I personally prefer a
> shorter period, and I actually find it good to keep them independent
> in details like this. So I'd like to know what are the reasons to
> keep
> them in sync. If you have a link to the discussed at hand, that would
> be nice. If not, don't worry, I'll see that we talk about it before
> making the first release.
> 

I don't have the link, but this issue is easy to summarize:

The reference kernels AIUI will be based on the Ubuntu archive kernel
which has a 3 week cadence. You should definitely plan for 3 week
cadences for the kernel snap because the archive cadence almost always
has security fixes in it. Planning a snappy kernel cadence that is
different is just going to cause pain because the disparate cadences
will go in and out and back in sync as the months go on.

Since kernel and os snaps are different, there is no requirement for
the os snap to be every three weeks and obviously pulling in security
fixes sooner is nothing I would complain about. However, I imagine that
it would be easier to keep the snappy kernel and os snap cadences
aligned otherwise the snappy release team will always be asking 'is
this week just the kernel, the os or both?'

-- 
Jamie Strandboge             | http://www.canonical.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/snappy-devel/attachments/20160308/7c4fc85d/attachment-0001.pgp>