hi, Am Donnerstag, den 24.03.2016, 16:37 +0000 schrieb Mark Shuttleworth: > On 22/03/16 18:43, Oliver Grawert wrote: > > hi, > > Am Dienstag, den 22.03.2016, 11:31 -0600 schrieb Leo Arias: > > > >> We will have a PPA where we put only the ubuntu-snappy deb generated > >> from the branch. We generate a snap using that PPA and put it in the > >> edge channel. We test and test and test, and once we are confident > >> that it is good, we will promote the snap to the stable channel and > >> push the deb from the PPA to the archive. > >> > > this sounds like the sanest option but indeed we will have the PPA in > > use for the official rootfs snaps then ... > > I thought we agreed that we could use the -proposed and -security > pockets for the rootfs (os-snap). we can, but before final release -proposed is still a pretty wildly changing place that could easily break dailies ... once the release is out the risk is lower that we have uninstallable packages (changes are rare after release) > > So, we push the deb to -proposed and build an os-snap that includes it > for edge. We can then copy that deb to the -updates pocket and not > rebuild the os-snap, because that is a copy, while AIUI you have to > rebuild if you move from PPA to primary archive. > this indeed only works if you only have that one package ... imagine there lands a broken systemd upload in -proposed at the same time... it will never enter the actual distro (because the migration tests will catch it) but we would end up with the broken package in our os snap. i think re-building after promotion is the only sane way here to avoid sneaking in potentially rolled back and broken packages.
ciao
oli
signature.asc
Description: This is a digitally signed message part
-- snappy-devel mailing list snappy-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snappy-devel
