<font size=2 face="sans-serif">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).</font>
<br>
<br><font size=2 face="sans-serif">Note that these two use "Fix bug"
on a separate line, albeit they aren't "fixes bug" as the post
mentions.</font>
<br>
<br><a href=https://review.openstack.org/#/c/41064/><font size=3 color=blue><u>https://review.openstack.org/#/c/41064/</u></font></a><font size=3>
</font>
<br><a href=https://review.openstack.org/#/c/39651/><font size=3 color=blue><u>https://review.openstack.org/#/c/39651/</u></font></a><font size=3>
</font>
<br>
<br><font size=2 face="sans-serif">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?<br>
</font>
<br><font size=2 face="sans-serif"><br>
</font>
<br><font size=1 face="Arial">Thanks,</font>
<br>
<br><font size=3 color=#8f8f8f face="Arial"><b>MATT RIEDEMANN</b></font><font size=1 face="Arial"><br>
Advisory Software Engineer<br>
Cloud Solutions and OpenStack Development</font>
<table width=680 style="border-collapse:collapse;">
<tr height=8>
<td width=680 colspan=2 style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;">
<hr>
<tr valign=top height=8>
<td width=418 style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;"><font size=1 color=#4181c0 face="Arial"><b>Phone:</b></font><font size=1 color=#5f5f5f face="Arial">
1-507-253-7622</font><font size=1 color=#4181c0 face="Arial"> | <b>Mobile:</b></font><font size=1 color=#5f5f5f face="Arial">
1-507-990-1889</font><font size=1 color=#4181c0 face="Arial"><b><br>
E-mail:</b></font><font size=1 color=#5f5f5f face="Arial"> </font><a href=mailto:mriedem@us.ibm.com target=_blank><font size=1 color=#5f5f5f face="Arial"><u>mriedem@us.ibm.com</u></font></a>
<td width=261 style="border-style:solid;border-color:#000000;border-width:0px 0px 0px 0px;padding:0px 0px;">
<div align=right><img src=cid:_1_097C0F90097C09FC000B5AFB86257BC4 width=83 height=30 alt=IBM><font size=1 color=#5f5f5f face="Arial"><br>
<br>
3605 Hwy 52 N<br>
Rochester, MN 55901-1407<br>
United States</font></div></table>
<br>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Jeremy Stanley <fungi@yuggoth.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">OpenStack Development
Mailing List <openstack-dev@lists.openstack.org>, </font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">08/10/2013 04:43 PM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [openstack-dev]
Flakiness with launchpad tracking bug status?</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>On 2013-08-10 13:20:41 -0500 (-0500), Matt Riedemann
wrote:<br>
> I've been seeing some flakiness lately with launchpad not tracking<br>
> Gerrit status when a patch is proposed (changing the bug to 'In<br>
> Progress') or merged (changing the bug to 'Fix Committed'). Has<br>
> anyone else experienced this? Note that the bugs even show when a<br>
> patch is proposed, change the assignee and track when it's merged<br>
> in github, but doesn't change the status.<br>
[...]<br>
<br>
Yes, this was an announced change in the bug integration hook for<br>
commit message processing a little over a week ago...<br>
<br>
<URL: </font></tt><a href="http://lists.openstack.org/pipermail/openstack-dev/2013-August/012945.html"><tt><font size=2>http://lists.openstack.org/pipermail/openstack-dev/2013-August/012945.html</font></tt></a><tt><font size=2>
><br>
<br>
In short, some of the old commonly-used patterns were reimplemented<br>
for convenience, but the new parser is not 100% backward compatible<br>
so some wordier bug-related comments will not be picked up<br>
(particularly if they're not all on one line, "bug" is not one
of<br>
the first two words or there are additional words after it prior to<br>
the bug number). Best of course is to use the new headers mentioned<br>
there, so you can also benefit from the new partial and related bug<br>
associations.<br>
-- <br>
Jeremy Stanley<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
</font></tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font size=2>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font size=2><br>
<br>
</font></tt>
<br>