On Thu, Aug 18, 2016 at 10:10 AM, Matthew Miller
<mattdm(a)fedoraproject.org> wrote:
On Thu, Aug 18, 2016 at 11:35:17AM -0500, Adam Miller wrote:
> Currently the compose (pungi) produces an Atomic ostree, installable ISO, and
> various cloud images nightly. Those artifacts are then tested via AutoCloud.
> I'm proposing that we add a second "new" repo, every two weeks we will
sync
> the latest commit from the current repo/ref that has passed testing in
Presumably everything in the new repo could be hardlinks, so there
wouldn't be much by way of space increase?
Do we want to also have a mechanism for adding off-cycle critical
security updates?
Someone on the two week stream could manually add a critical update
with `ostree admin unlock` or they could rebase to the continuous
stream (assuming the two-week is the default) to get the update. Would
handling this with docs and manual intervention be sufficient?
>
> --
> Matthew Miller
> <mattdm(a)fedoraproject.org>
> Fedora Project Leader
> _______________________________________________
> rel-eng mailing list
> rel-eng(a)lists.fedoraproject.org
>
https://lists.fedoraproject.org/admin/lists/rel-eng@lists.fedoraproject.org