handle 0-day and stable blockers
ClosedPublic

Authored by adamwill on Dec 15 2015, 12:01 AM.

Details

Summary

As per discussion on test@, we'll be using a couple of new magic
whiteboard strings to identify two sets of 'special' blockers:
Accepted0Day and AcceptedPreviousRelease. The first are bugs that
must be fixed in the 0-day update set for the new release. The
second are bugs that must be fixed in updates for the previous
stable release(s) before the new release goes out. This commit
allows blockerbugs to handle them, displaying them as two new
groups on the Bug List and IRC Format pages.

Test Plan

Check that the new blocker types are correctly detected
and listed and the app works as before in all other respects.

Diff Detail

Repository
rBLKR blockerbugs
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
adamwill retitled this revision from to handle 0-day and stable blockers.Dec 15 2015, 12:01 AM
adamwill updated this object.
adamwill edited the test plan for this revision. (Show Details)
adamwill added reviewers: tflink, mkrizek.
adamwill updated this revision to Diff 1786.Dec 15 2015, 12:21 AM

add tests for new blocker types, add data to basicbuginfo

mkrizek requested changes to this revision.EditedDec 15 2015, 1:35 PM

Overall it looks good to me but since the patch changes database schema we need alembic migration script. It should be pretty straight-forward, see alembic/versions/ for inspiration.

This revision now requires changes to proceed.Dec 15 2015, 1:35 PM
adamwill updated this revision to Diff 1791.Dec 15 2015, 7:58 PM

add a database revision for the new bug columns

adamwill updated this revision to Diff 1792.Dec 15 2015, 8:09 PM

set False as the default for new blocker types on db upgrade

The code is fine for the most part but I'm not thrilled about how cluttered the pages look after adding two more lists to them which are probably going to be empty 90% of the time.

I'm trying to think of a way to improve this without adding an unreasonable amount of work, any thoughts?

How about this?

--- a/blockerbugs/templates/blocker_list.html
+++ b/blockerbugs/templates/blocker_list.html
@@ -56,7 +56,7 @@ text: '<a href="' + $(this).contents().filter('a').attr('href') + '" title="More
 <div class="row">
     <div class="twelve columns" id="blockertables">
         {% for buglist in ['Proposed Blockers','Accepted Blockers', 'Accepted 0-day Blockers', 'Accepted Previous Release Blockers', 'Proposed Freeze Exceptions', 'Accepted Freeze Exceptions'] %}
-        <h2>{% if buglists[buglist] %}{{ buglists[buglist] | length }}{% else %}No{% endif %} {% if (buglists[buglist] | length) == 1 %}{{ buglist[:-1]}}{% else %}{{ buglist }}{% endif %}</h2>
+        {% if buglists[buglist] %}<h2>{{ buglists[buglist] | length }} {% if (buglists[buglist] | length) == 1 %}{{ buglist[:-1]}}{% else %}{{ buglist }}{% endif %}</h2>
         <table id="{{ buglist | tagify }}" cellspacing="1" class="tablesorter">
             <thead>
                 <tr>
@@ -94,7 +94,10 @@ text: '<a href="' + $(this).contents().filter('a').attr('href') + '" title="More
                     </tr>
                     {% endfor %}
             </tbody>
-        </table>
+        </table>{% endif %}
+        {% endfor %}
+        {% for buglist in ['Proposed Blockers','Accepted Blockers', 'Accepted 0-day Blockers', 'Accepted Previous Release Blockers', 'Proposed Freeze Exceptions', 'Accepted Freeze Exceptions'] %}
+            {% if not buglists[buglist] %}<h4>No {{ buglist }}</h4>{% endif %}
         {% endfor %}
     </div> <!-- end of 12 columns -->
 </div> <!-- end of row -->
adamwill updated this revision to Diff 1899.Feb 8 2016, 10:55 AM

make the blocker list HTML a bit more efficient

tflink accepted this revision.Feb 22 2016, 5:20 PM
mkrizek accepted this revision.Feb 22 2016, 7:18 PM
This revision is now accepted and ready to land.Feb 22 2016, 7:18 PM
This revision was automatically updated to reflect the committed changes.