[openstack-dev] [fuel][puppet] Switching fuel-library to consume stable/mitaka
ibelikov at mirantis.com
Tue Mar 22 20:40:02 UTC 2016
> Additionally we will want to ensure that the fuel-ci will work for the upstream stable/mitaka branches as it currently isn't working since we haven't cut a stable/mitaka branch for Fuel yet. Igor Belikov has been notified of the current issues and is looking into a fix.
I rolled out the fix to Fuel CI and retriggered tests for the change, thanks for catching this quickly. We don’t plan to tie Fuel CI for puppet-openstack to Fuel branching dates, so Fuel CI will test changes to both master and stable/mitaka branches of puppet-openstack modules using master of fuel-library for now. There still might be some issues with stable/mitaka testing, so feel free to poke me or anyone in #fuel-infra and we’ll try to iron this out as quickly as possible.
Fuel CI Engineer
ibelikov at mirantis.com
> On 22 Mar 2016, at 22:42, Alex Schultz <aschultz at mirantis.com> wrote:
> Hey everyone,
> Emilien is in the process of cutting the stable/mitaka branches for all of the upstream puppet modules. As Fuel approaches SCF, we will want to switch from the master branches we are currently tracking to leverage the stable/mitaka branches. In talking with some other folks, I believe the plan is the following switch fuel-library to leverage stable/mitaka branches prior to SCF. Once we open master backup for Newton activities, we will switch the fuel-library master branch back to tracking the upstream master branches while leaving our stable/mitaka branch pointed to the upstream stable/mitaka branches.
> As far as these activities are concerned, I believe Ivan Berezovskiy will be providing a patch to do the switch to stable/mitaka. Additionally we will want to ensure that the fuel-ci will work for the upstream stable/mitaka branches as it currently isn't working since we haven't cut a stable/mitaka branch for Fuel yet. Igor Belikov has been notified of the current issues and is looking into a fix.
> Please raise any concerns or items that also need to be addressed.
>  https://review.openstack.org/#/c/295976/ <https://review.openstack.org/#/c/295976/>__________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev