Steve Langasek <vor...@debian.org> wrote: > Package: bugs.debian.org > > The legend on http://bugs.debian.org/release-critical/ is very difficult to > scan; to figure out which line is which in the graph, you have to read the > entire block of text. Using colors in the legend that match the graph > itself would make it easier to pinpoint the bits of info you're looking for. >
I didn't find the script that generates the index.html page, so I patched the index.html. It gives at least an idea of what we (at least I) 'd like to see on the page. (patch attached). Please consider applying it. Regards, -- Mehdi Dogguy
--- index.html.old 2011-06-10 21:03:31.000000000 +0200 +++ index.html.new 2011-06-10 21:02:58.000000000 +0200 @@ -20,12 +20,16 @@ <div align="center"><img src="graph.png" alt="Graph of RC bugs"></div> -<p>The red line graphs all bugs with release-critical severities; the green -line graphs the number of bugs that are actually a concern for the next -release (excluding ignored bugs, bugs on packages not in testing, and bugs -whose tags and/or versioning information indicate that they don't apply to -testing), and the blue line graphs the number of bugs that are a concern -for the <em>current</em> stable release.</p> +<ul> + <li><font color="red">All bugs with release-critical + severities</font>,</li> + <li><font color="green">bugs affecting the next release</font> + (excluding ignored bugs, bugs on packages not in testing, and bugs + whose tags and/or versioning information indicate that they don't + apply totesting),</li> + <li>and <font color="blue">bugs affecting the <em>current</em> + stable release</font>.</li> +</ul> <h2>Recent changes</h2> <STRONG>3</STRONG> release-critical bugs were closed and <STRONG>2</STRONG> were opened.<P>
