Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Work to make alpha more accessible #164

Open
cgwalters opened this issue Oct 6, 2016 · 3 comments
Open

Work to make alpha more accessible #164

cgwalters opened this issue Oct 6, 2016 · 3 comments

Comments

@cgwalters
Copy link
Member

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)
@cgwalters
Copy link
Member Author

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?

@jasonbrooks
Copy link
Collaborator

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?

@cgwalters
Copy link
Member Author

Open to alternatives. ahdev?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants