hi guys,
RHEL 7.2 was released a few days back and we've been busy sorting through the code and working on the downstream CentOS Linux release ( its going to likely be released in November and will be called 7.1511 ).
I'd like to make that content available on ci.centos.org ahead of public release. And there are a couple of ways to do this :
1) either we update the provisioning service, so all requests for a centos linux 7 machine will give you a 7.1511 build ( its 7.1503 at the moment ), with all the updates etc posted in sync that way. This also means that mirror.centos.org inside the ci infra will look DIFFERENT from mirror.centos.org the real users see, since it will be setup to look like the next release.
2) we make the content available in a new set of repos, called CentOS.next or something; and the ci users are able to optionally tweak their build scripts etc to include or not include these new changes.
3) we dont make this content available before its publicly released.
of all those bits, I like (1) best; (2) only delays the content from hitting the ci infra by a week or 10 days. We dont usually take longer than that from when the builds are done to when the distro update is released. (3) just means that if there are changes, failures or breakages in the ci tested code, we only find out at the same time as the users - which isnt nice.
thoughts ?