Migration of OpenStack Charm development to OpenStack git/gerrit

[James Page]

Just as a reminder that we're still aiming to undertake this migration
today.

On Fri, 19 Feb 2016 at 13:50 James Page <james.page at canonical.com> wrote:
>
>> Hi All
>>
>> As you may or may not be aware, the OpenStack team have been working
>> towards migration of the development process around the OpenStack charms to
>> the OpenStack project.
>>
>> This means we will be moving away from current the bzr/launchpad workflow
>> to a git/gerrit workflow inline with most other OpenStack projects.
>>
>>
>> Bugs will still be managed on launchpad - this just relates to VCS and
>> associated review process.
>>
>> Please take time to read the upstream development documentation prior to
>> the switch over; there are some steps you will need to take to be able to
>> work with the new tools and workflow including signing up for membership of
>> the OpenStack Foundation and getting things set-up in gerrit:
>>
>>  http://docs.openstack.org/infra/manual/developers.html
>> <http://docs.openstack.org/infra/manual/developers.html#development-workflow>
>>
>> The scope of the migration can been seen on the github mirror of the
>> current bzr branches:
>>
>>  https://github.com/openstack-charmers
>>
>> In order to de-risk the migration and allow time to migrate all
>> associated tooling and configurations (such as mojo specs, bundles, amulet
>> tests etc…) to use git, we’ll be putting in place a mirror process which
>> will sync the charms once in their new home on git back to the current set
>> of branches in launchpad; This means that everything that works today
>> should continue to work!
>>
>> Once we’ve completed the switch over, lint and unit tests will be
>> executed on OpenStack infrastructure and amulet tests will continue to be
>> executed within the OSCI lab at Canonical.
>>
>> We will be altering the gating process slightly - initially we’ll run a
>> subset of amulet tests to provide immediate feedback to the
>> contributor/reviewers; the full set of amulet tests will be executed once a
>> reviewer has +2’ed the review prior to final landing.
>>
>> Code will be automatically landed by the OpenStack development process -
>> no need to complete manual merges any longer!
>>
>>
>> We’ll still be maintaining separate development and stable charms -
>> you’ll find the development charm in the master branch in the git
>> repositories, and the stable charm in the stable branch.
>>
>> All of this will be documented here:
>>
>>
>> https://github.com/openstack-charmers/openstack-community/blob/master/README.dev-charms.md
>>
>> The current target for switch over is Monday the 29th February.
>>
>> Regards
>>
>> James
>>
>> pp OpenStack Engineering team
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/openstack-charmers/attachments/20160229/72ad5517/attachment-0001.html>