> Hi, > > In RDO we are preparing for the incoming Ocata release. This means > we'll create a new RDO Trunk builder "centos-ocata" in the next few > days (It will be ready for next week). This builder will get content > from stable/ocata branches of projects as they become available and > fallback to master for those not branched yet. The repos created by > this worker will be published under > https://trunk.rdoproject.org/centos7-ocata/ (which will not longer be > a link to https://trunk.rdoproject.org/centos7-master/). >
Hi all, The centos-ocata builder has been successfully bootstrapped, and its repositories are available at https://trunk.rdoproject.org/centos7-ocata/ Regards, Javier > According to the feedback received during the last release cycle, we > are changing the way we do the transition this time so that > repositories content will be more accurate to what is expected at any > point in the cycle. Repos under centos-master will allways follow > master branch and centos-ocata will get stable/ocata as soon as repos > get the branch created. > > This has some implications from the upstream projects point of view: > > - Projects using repositories under > https://trunk.rdoproject.org/centos7-ocata/ will start getting > packages for content delivered in stable/ocata branches instead of > master. Repos in https://trunk.rdoproject.org/centos7-master/ will > keep getting packages for content in master branch. > - Anyone currently pinning to a specific hash repo under > https://trunk.rdoproject.org/centos7-ocata/ should move it to use > https://trunk.rdoproject.org/centos7-master/ as soon as possible. Note > that pinning to a specific hash is not recommended practice. > - With current job definitions, link current-tripleo promoted by > upstream TripleoCI will promote repos with content from master > branches and not stable/ocata after creating the ocata builder. We > think this is not the desired situation during RC period and we must > keep promotion of current-tripleo link for stable/ocata until > cycle-trailing projects are tagged. This will require some changes in > both Tripleo-CI and RDO-CI, please let us know your thoughs so that we > can agree on the best way to implement this and start working on it. > > Best regards, > > Alfredo > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev