<div dir="ltr"><div><div><div><div>Leo, </div>Thanks for the great write-up. For 3rd party developers, I assume that we </div>are not going to set similar guidelines and they will be free to promote between channels as they feel best. As a best practice, we can provide suggestions esp. for people using our CI infrastructure. </div> </div>/Manik </div><div class="gmail_extra"> <div class="gmail_quote">On Wed, Mar 2, 2016 at 6:46 AM, Leo Arias <<a href="mailto:leo.arias@canonical.com" target="_blank">leo.arias@canonical.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, Today we discussed about using the four channels that the store offers. We want a saner ubuntu-core snap and be able to release it often and in a predictable date. Edge: We will build an ubuntu-core snap for every change in the snappy master branch and release it to the edge channel. This channel is gated by the automated executions in pull requests: static analysis, unit and integration tests. TODO: - - Merge the pull requests with master before running the tests to prevent conflicts. - - Add a test job that builds the debian package. - - Talk with the store, spi and launchpad teams to share as many tools as possible. Beta: Every night we will run all the automated tests we have using the edge channel. If everything is green, we will have an automatic promotion to beta. This channel is gated by the integration tests that can run in all the platforms we have available in the lab, plus update and rollback tests. The platforms available are currently amd64 and x86, but we hope to get armhf in the cloud or LXC, bbb and dragonboard testbeds. This is the channel we will recommend people to use if they want to help testing the new release. Release Candidate: Every two weeks, we will promote from beta to release candidate. We will use this channel to do a lot of exploratory testing. And as almost every RC version will be the same as a stable version, we will verify the updates and rollbacks. We will test RC in the boards that we don't have available in the lab, and we will manually run the few tests that can't be automated. We will use the first two or three releases to find new gates and process changes that will let us release every week. Stable: Once we are happy with the exploratory testing on RC, we will promote to Stable. After the promotion, we will trigger the automated tests again and verify updates and rollbacks. TODO: discuss with ogra the hook into the image generation process. A note on securiy fixes: When there's a new CVE, we want to release the fix as soon as possible to stable. This will be easier if we can cherry pick only the fix instead of generating the snap normally, because we want to avoid bringing additional non-security-related package updates. Pending: - - discuss about the planning of scenarios or stories before starting a new cycle. - - discuss about the commits and changelog that goes into stable. - - find a way to include in the changelog the package updates that are new to the release. During the following weeks we will be arranging the gates, and figuring out the build and upload process. And after the first releases we'll be making adjustments for sure, so please send us your suggestions if you have any. pura vida -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJW1vzLAAoJEIUvYw0No8Dg9tMP/2rVIAPne1sNz4Ae7fwkvbHC BI68ek5HmHaEfnqgJM5HP4TC+Tp1kPC55gHut6O31s89og7f1DgbTs5wrJEcG2bx ydoQhs8p8bpZ5YtCWOD0ZuU3l+AYrnFgiK8LM5ZUEwhEYngJMPfTICh3r/ElX9Vo 30R/90gn0TxT/O6VUILSSk1w1e5LF77Zt+w7cx+ONg42ZSjS4E1Cmpw32FdGb0oT eARQIOpSQg/0i0JFVTSDK6kwJMOkwVXr0Ouv/Av/UBZCokwDsUiZxV1cFwTz9q3W xBJOWwU3G+HLMIuZro5sIgPJhf6CnSmtiWgfZZwA6+qu9s0EaT50l6NE8CF+uLSP HBh+LryBC2DHrMeX7b45lfDaiteMfFwPv4GKAGalYfbzoRhc8LDm4FAFk0qzDE6c 8KWbVeR+qUj92AMHbp5BPHqx7d02AzBqvB/dg8llk2Y/XVXgL9nr7F3m71mFiGhr PPFXwNojmFwvQWM+0gjsDarH/kub3NK0FJo8xk4OymPHJKf3+P9+5I3P00ctqAlV n3s4xb7olik3psVrVSs2Pl8ry0d7/mm2dJagnD88usvRAT1bMmmU4Gmi9v+nEziz UDLd0ydRdPSuARi5+phMMnkRO2JYKUWWDlQ5/UwzGwtZGnlgPyfhumWkxtkOqAMp LS8rDUfABCPnOga+Kzlp =nqOw -----END PGP SIGNATURE----- -- snappy-devel mailing list <a href="mailto:snappy-devel@lists.ubuntu.com">snappy-devel@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snappy-devel" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snappy-devel</a> </blockquote></div> </div>