Re: Proposal for new commit msg design for engine commits

From: "Eyal Edri" <eedri(a)redhat.com&gt; To: "engine-devel" <engine-devel(a)ovirt.org&gt; Cc: "infra" <infra(a)ovirt.org&gt; Sent: Tuesday, July 9, 2013 12:38:51 PM Subject: Proposal for new commit msg design for engine commits Hi, You all probably know and familiar with 'ovirt-engine' git hook for commit msg template [1]. this helps understand the general area of the patch in the project but it lacks additional info that might be valuable for scaling automatic tests in Jenkins CI. Let me explain: Infra team is working hard on expanding oVirt CI infrastructure and adding more tests in jenkins (per commit/patch). Adding important meta-data per patch can significatly improve the ability to run specific tests for each patch/commit, and not waste valuable resources on Jenkins jobs that are not relevant to the code in the patch. So the idea is to add/expand current metadata per patch, in the form of: (either) 1. expanding current header template to include more data like 'network' , 'setup', 'tools', 'virt'

2. adding a new label with relevant tags for the patch, called e.g 'METADATA: network, rest, virt'