[openstack-dev] [os-ansible-deployment] [openstack-ansible] Using commit flags appropriately
kevin.carter at RACKSPACE.COM
Thu Jul 16 15:29:41 UTC 2015
+1 - I think we should start doing this immediately.
Racker, Developer, Hacker @ The Rackspace Private Cloud.
From: Ian Cordasco <ian.cordasco at RACKSPACE.COM>
Sent: Thursday, July 16, 2015 10:12 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [os-ansible-deployment] [openstack-ansible] Using commit flags appropriately
Now that the project is starting to grow and has some amount of
documentation. We should really start using flags in our commits more
appropriately, e.g., "UpgradeImpact", "DocImpact", etc.
For example, my own recent change to upgrade our keystone module to use v3
should have also had an "UpgradeImpact" flag but only had a DocImpact flag.
This will help consumers of openstack-ansible in the future and it will
help us if/when we start writing release notes for openstack-ansible.
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev