Good idea, I'd only ask that you post back here when you have something up in the wiki so we can remember to review it. This is more for me so I have this in mind when doing reviews, i.e. does the change fall into this category but doesn't tag it. Thinking maybe DB migration issues, backwards incompatible API changes (which is I think what started this discussion), etc.
Thanks, MATT RIEDEMANN Advisory Software Engineer Cloud Solutions and OpenStack Development Phone: 1-507-253-7622 | Mobile: 1-507-990-1889 E-mail: [email protected] 3605 Hwy 52 N Rochester, MN 55901-1407 United States From: Russell Bryant <[email protected]> To: OpenStack Development Mailing List <[email protected]>, Cc: Dan Smith <[email protected]> Date: 10/14/2013 06:38 PM Subject: [openstack-dev] [Nova] UpgradeImpact commit message tag I was talking to Dan Smith today about a patch series I was starting to work on. These changes affect people doing continuous deployment, so we came up with the idea of tagging the commits with "UpgradeImpact", similar to how we use DocImpact for changes that affect docs. This seems like a good convention to start using for all changes that affect upgrades in some way. Any comments/suggestions/objections? If not, I'll get this documented on: https://wiki.openstack.org/wiki/GitCommitMessages#Including_external_references -- Russell Bryant _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<<image/gif>>
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
