This is an automatically generated e-mail. To reply, visit: http://reviewboard-tflink.rhcloud.com/r/2/ |
On March 4th, 2013, 3:45 p.m. UTC, Martin Krizek wrote:
blockerbugs/__init__.py (Diff revision 3) 7 import bugzillaFor what?
Good catch - that isn't supposed to be there anymore
On March 4th, 2013, 3:45 p.m. UTC, Martin Krizek wrote:
blockerbugs/templates/base_nav.html (Diff revision 3) 23 <li><a {{navactive('milestone', '18final') }} href="{{ url_for('main.display_buglist', num=18, release_name='final') }}">Fedora 18 Final</a></li>23 <li><a {{navactive('milestone', '19final') }} href="{{ url_for('main.display_buglist', num=19, release_name='final') }}">Fedora 19 Final</a></li>Not necessary anymore with t332 in develop.
Yeah, I forgot that t332 made it to develop already - will update the diff.
On March 4th, 2013, 3:45 p.m. UTC, Martin Krizek wrote:
blockerbugs/templates/propose_bug.html (Diff revision 3) 145 <a href="https://fedoraproject.org/wiki/Fedora_19_Final_Release_Criteria">final</a>)Maybe an overkill but we could load the release number dynamically?
Yeah, that shouldn't be too hard to do. The URL structure may change in the future but we can deal with that if/when it happens
On March 4th, 2013, 3:45 p.m. UTC, Martin Krizek wrote:
blockerbugs/util/bz_interface.py (Diff revision 3) 49 url = 'https://bugzilla.redhat.com/xmlrpc.cgi'So I gather you rather not load the app to load the url from the config, right?
In that particular code - yeah, I'd rather avoid it. There are no direct dependencies on the blockerbugs code in there and I'd rather keep it that way. The rest of the BBA should be passing in a bugzilla url when the interface object is created and getting that URL from config, though
- Tim
On March 1st, 2013, 6:19 a.m. UTC, Tim Flink wrote:
Review request for blockerbugs.
By Tim Flink.
Updated March 1, 2013, 6:19 a.m.
Bugs:
334
Repository:
blockerbugs
Description
Testing
Diffs
|