[openstack-dev] Policy for linking bug or bp in commit message

Ihar Hrachyshka ihrachys at redhat.com
Fri Jun 13 13:16:12 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 29/05/14 17:33, Yuriy Taraday wrote:
> On Wed, May 28, 2014 at 3:54 AM, Joe Gordon <joe.gordon0 at gmail.com>
> wrote:
> 
>> On Fri, May 23, 2014 at 1:13 PM, Nachi Ueno <nachi at ntti3.com>
>> wrote:
>> 
>>> (2) Avoid duplication of works I have several experience of
>>> this.  Anyway, we should encourage people to check listed bug
>>> before writing patches.
>>> 
>> 
>> That's a very good point, but I don't think requiring a bug/bp
>> for every patch is a good way to address this. Perhaps there is
>> another way.
>> 
> 
> We can require developer to either link to bp/bug or explicitly
> add "Minor-fix" line to the commit message. I think that would
> force commit author to at least think about whether commit worth
> submitting a bug/bp or not.
> 

I like the idea. The best of both approaches (strict requirement and
place for maneuver in case of tiny fixes).

> 
> 
> _______________________________________________ OpenStack-dev
> mailing list OpenStack-dev at lists.openstack.org 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTmvmcAAoJEC5aWaUY1u57LKIH+QECvDXWHeT3bwxfT9SlTOYl
jAmQv1wfURDJxS7akFsczw7z0u9cCEQTFH7rDBXk0qb45sm+yfTzACfwOJ5FThiT
1+oGkJJUnrT6sZQlp9abFGCF+LGfbWd3fi7FUg0JSl4u/z3W38ToY7IR1gqj6Z7r
+GQ/zebiU709VUjKDfjsL4a8zkPBQGWUwdFjR5l9P6nJCNjfH4GUjisoglvQGvKM
NVRWHnedBDliPEZTuqhZaKF+II2xDAtgWystPmdpQIGMUeOJefOHcVs7yYv6pLjD
GLhxKl44LYN4rKWnGGeHWMa//vadpHZNVdvmdvMZa9wi/ZXqHFLIWVDgMkjxWfw=
=Eghb
-----END PGP SIGNATURE-----



More information about the OpenStack-dev mailing list