release cadence and channels for the ubuntu-core snap

[Leo Arias]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2016-03-02 12:58, Oliver Ries wrote:
> Our experience is that processes like this will evolve [1] over
> time and I think we need to closely monitor the efficiency of these
> measures, do we have some notion of escaped defects?

Not a good one yet. The situation now is that we don't have a
community testing our releases so most of the bugs are found by the
devs while they are working in master.
That's another topic we should discuss again:
1. We should make a bug report in launchpad for every problem we find,
even if they are found on master and the dev who finds it quickly
prepares a fix. We proposed this and Gustavo said no. I'm now throwing
the suggestions is smaller doses, so we'll propose it again soon.
2. We need a community of testers. Once we get ubuntu-image and a
decently sane beta channel, we can spend some time again on the
testing days we tried last year.
3. We need this formal release process so Federico and I can spend a
decent amount of time on exploratory testing for 16.04 during the
week, just as we do on 15.04 and snapcraft releases.

After that I would hope to get more bug reports that we can triage,
analyze and turn into new regression tests at different levels. Then
we can start with a simple metric like counting the # of bugs found in
each channel at the start of a new cycle. But first we need bug reports.

> Also, another important next step is to hook this pipeline into
> the image creation & publication process, what is the status
> there?

The idea is that a new image is generated every time we promote to
stable. So, every two weeks to begin with. This week we are focusing
on earlier triggers than that, so we'll be discussing it as we
approach to the stable gate.

> O. [1] euphemism for a "ht... did this happen??1? We need to add
> tests for that!"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJW3hcpAAoJEIUvYw0No8DgWM4P/iZkJY1XMNHPBFwRjnxGEX0A
UIEiWV7Vk3ddQC04OfFXemQwA6iWqjqSKXvEnw5d+XM4/R0Mu8/lDdpIdFduANYK
gGuePGAOEot9xd5Hbl8VjT2RsGMmPtNo3adHDiGTXyAxoW53qjjOh3azcz4v4l92
Oa05ya6l1+PIZDailc40ihMCmeYda52c/QdfHCkVJI2K86fQJvFDc7njjGeUdvtO
QWN5Qnl7aKlg/hmTUNh6vcZRLmXsV6H1hkx2MP1IecBfQr4mt5p6UUXOBmdTdstN
6L6U2OrQetjU8SScUvbl9acsiimPwlzBFSwBppFgCGjLzApmO8mpvEugmY8GvHKk
QnYRA3uBjkiOAXImcgc4+8QqGeBh6x8lSAYTIrTvGEGpZY8IgIkd6tO0XJrKEhS4
MAmHPZnrMVvpqJatcwgaZncek5vZ+XBJCdPSKxTHhnxUEmM8Qscspk46oO8Oq+El
w3arnI04qj1hJEmTWRl6Fw8HCuUYt+5Y8qS0PdGuBEizzxMn1lpmd4xnGkGdKcao
B3n13yDvktFRKHg0pe2ladntBOZVNNemGvpjVsyIP8HFG2X0cx4SeswbloH5djTv
j212+1amTTfedVoNs1k3CkDPSFAfMoqn/bqP4OljLC2/5XNuho4gp8Q0fu5soYUB
1GtZq+Df4xqLmueNacZB
=PRp0
-----END PGP SIGNATURE-----