You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The /continuous stream has a very small target audience - basically people who want to test git master. But /alpha has potentially a much larger one, and I think we should get to the point where we say "Yes, it's totally sane to mix some alpha machines into your staging/production".
Tasks for that are the same baseline things for all release streams:
Mirroring
Signing
Security updates (we should have a process to auto-respin alphas when underlying CentOS changes)
The text was updated successfully, but these errors were encountered:
Perhaps the simplest here is that Alpha goes into the same ostree repo as downstream, and we at least place the qcow2/vagrant boxes in the same directories?
That makes sense to me. Do we like the name alpha? I've started getting used to it, but is it too bleeding edge sounding, or perhaps the right amount of bleeding edge sounding?
The /continuous stream has a very small target audience - basically people who want to test git master. But /alpha has potentially a much larger one, and I think we should get to the point where we say "Yes, it's totally sane to mix some alpha machines into your staging/production".
Tasks for that are the same baseline things for all release streams:
The text was updated successfully, but these errors were encountered: