Open Stack

OK, I have the post on the new tags bookmarked so I've been sure to use 
them in my latest commits but looking back at the ones I pointed out, they 
were using something different so I suppose that's the issue (although the 
hyper-v one of mine was before those changes went into effect, I think - 
it was merged back on 7/9).

Note that these two use "Fix bug" on a separate line, albeit they aren't 
"fixes bug" as the post mentions.

https://review.openstack.org/#/c/41064/ 
https://review.openstack.org/#/c/39651/  

Anyway, I'll keep a look out for the new tag in commit messages when doing 
reviews.  Does this mean we should be giving a -1 if the tag doesn't apply 
to the new patterns?



Thanks,

MATT RIEDEMANN
Advisory Software Engineer
Cloud Solutions and OpenStack Development

Phone: 1-507-253-7622 | Mobile: 1-507-990-1889
E-mail: mriedem at us.ibm.com


3605 Hwy 52 N
Rochester, MN 55901-1407
United States




From:   Jeremy Stanley <fungi at yuggoth.org>
To:     OpenStack Development Mailing List 
<openstack-dev at lists.openstack.org>, 
Date:   08/10/2013 04:43 PM
Subject:        Re: [openstack-dev] Flakiness with launchpad tracking bug 
status?



On 2013-08-10 13:20:41 -0500 (-0500), Matt Riedemann wrote:
> I've been seeing some flakiness lately with launchpad not tracking
> Gerrit status when a patch is proposed (changing the bug to 'In
> Progress') or merged (changing the bug to 'Fix Committed'). Has
> anyone else experienced this? Note that the bugs even show when a
> patch is proposed, change the assignee and track when it's merged
> in github, but doesn't change the status.
[...]

Yes, this was an announced change in the bug integration hook for
commit message processing a little over a week ago...

<URL: 
http://lists.openstack.org/pipermail/openstack-dev/2013-August/012945.html 
>

In short, some of the old commonly-used patterns were reimplemented
for convenience, but the new parser is not 100% backward compatible
so some wordier bug-related comments will not be picked up
(particularly if they're not all on one line, "bug" is not one of
the first two words or there are additional words after it prior to
the bug number). Best of course is to use the new headers mentioned
there, so you can also benefit from the new partial and related bug
associations.
-- 
Jeremy Stanley

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130810/cb5f56d4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1851 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130810/cb5f56d4/attachment.gif>