Bulk changes are complete.  Bug emails have been turned back on.  Hopefully no one&#39;s inbox has been flooded.<br><br>Summary of changes:<br><ul><li>Moved &#39;patch status&#39; values into their new corresponding Status values</li>
<ul><li>Note that &quot;patch pushed&quot; is mapped to &quot;Pushed to Master&quot; now<br></li></ul><li>Created two new statuses:</li><ul><li>In Discussion:  for things with deeper ramifications that we need to discuss as a community before committing to the codebase</li>
<li>Pushed to Stable:  a status to be used by the Release Maintainer to indicate that a patch is now in the stable release.  Workflow should follow this from after &quot;Pushed to Master&quot;</li></ul><li>Created patch status workflows to match, well, our workflow.  You can&#39;t set a bug report directly to Passed QA unless it&#39;s been Signed Off, etc.<br>
</li><li>Obsoleted &#39;patch status&#39; and it&#39;s dependency on Importance<br></li></ul>Work remaining to be done:<br><ul><li>Shared reports need to be updated.  Since I&#39;m not the creator of these, I cannot edit them for everyone else.  Most of the key ones are owed by either Paul P. or Chris C.</li>
<li>New reports for other statuses, like &quot;In Discussion&quot;, &quot;Pushed to Stable&quot; or &quot;Does not apply&quot;</li><li>Updating community and personal documentation to reflect the new change in patch submission paperwork.  I&#39;m hoping that we&#39;ll now be able to auto-set the Status with git-bz, for example, which will streamline our process as developers.<br>
<br></li><li>Updating bugs that have already been pushed to stable from the defauled &quot;Pushed to Master&quot; value (or, better yet, they could be closed... hint hint)</li><li>Restoring lost Importance data on Needs Signoff, Signed Off, Passed QA and other statuses.  There is a history link for changes to a bug report, available in the right column above the &quot;see also&quot; and &quot;change sponsored?&quot; fields, but doing this cleanup will likely need to be manual.</li>
</ul><br>Please let me know if any other complications have arisen because of this change.  Discussion of additional fields to add can be put into separate threads, for easy readability.<br><br>Cheers,<br><br><br>-Ian<br>
<br><div class="gmail_quote">On Sat, Jan 14, 2012 at 7:52 PM, Ian Walls <span dir="ltr">&lt;<a href="mailto:ian.walls@bywatersolutions.com">ian.walls@bywatersolutions.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Everyone,<br><br><br>As I mentioned in my previous thread about updating Bugzilla to better make use of the Status field, I&#39;ll be taking bug emails offline for a period of time while I make bulk changes to the statuses.  This is to prevent everyone from being horribly spammed.  I will reactivate the emails once the changes are complete.<br>

<br>I&#39;ll try to be on IRC for the duration of this maintenance job, in case anyone has any emergency questions.<br><br>Cheers,<br><br><br>-Ian<br clear="all"><font color="#888888"><br>-- <br>Ian Walls<br>Lead Development Specialist<br>
ByWater Solutions<br>
ALA Midwinter Booth #2048<br>Phone # <a href="tel:%28888%29%20900-8944" value="+18889008944" target="_blank">(888) 900-8944</a><br><a href="http://bywatersolutions.com" target="_blank">http://bywatersolutions.com</a><br>
<a href="mailto:ian.walls@bywatersolutions.com" target="_blank">ian.walls@bywatersolutions.com</a><br>
Twitter: @sekjal<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Ian Walls<br>Lead Development Specialist<br>ByWater Solutions<br>ALA Midwinter Booth #2048<br>Phone # (888) 900-8944<br><a href="http://bywatersolutions.com" target="_blank">http://bywatersolutions.com</a><br>
<a href="mailto:ian.walls@bywatersolutions.com" target="_blank">ian.walls@bywatersolutions.com</a><br>Twitter: @sekjal<br>