-
Notifications
You must be signed in to change notification settings - Fork 155
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
[next-devel] manifest: add fedora-candidate-compose to list of repos #2706
[next-devel] manifest: add fedora-candidate-compose to list of repos #2706
Conversation
Before we merge this, I think we clear up first whether the repo should always be in the manifest or only during a certain period. Maybe let's have a quick high-bandwidth chat about it. |
Late in the Fedora major release process adding this repo will allow us to pull in candidate RPMs that are proposed to fix release blocking or freeze exception issues. We will be able to test out these proposed fixes sooner and also be more prepared for releasing our final `next` release once the release is deemed "Go". See coreos#2705
539d10f
to
b50f47b
Compare
Updated the commit message here. |
FTR: @dustymabe and I discussed this OOB and we agreed that outside of this time period (lead up to GA), we will go back to using the official Fedora repos only. |
Since (as expected) this hasn't changed any packages in the compose:
I'll go ahead and merge this. skipping the rest of CI |
Slight clarification. I think it should be: "outside of this time period (when |
Late in the Fedora major release process adding this repo will
allow us to pull in candidate RPMs that are proposed to fix
release blocking or freeze exception issues. We will be able to
test out these proposed fixes sooner and also be more prepared
for releasing our final
next
release once the release isdeemed "Go".
See #2705