On Fri, Aug 10, 2012 at 4:38 PM, Evan Dandrea <e...@ubuntu.com> wrote:
> On Thu, Aug 9, 2012 at 9:46 AM, Sebastien Bacher <seb...@ubuntu.com>wrote: > >> * did you say that fixed bugs should be colored differently in that >> version? >> > > Not fixed bugs, but problem pages that you've already visited. I'll try to > find time this weekend to land the branch that makes problems that are > likely to be fixed (they have yet to show up in the most recent version of > the package) greyed out but still clickable. > As promised, I sorted this over the weekend and thanks to some quick work by jjo, it's now live: http://errors.ubuntu.com In the most common problems table: - If a linked bug report is marked as completed, the entire row will be greyed out (but still clickable). - If there is no linked bug report or the linked bug report is not marked as completed, but the version in Last seen column is *not* the most recent, just the Last seen column will be greyed out. This implies that because we have not seen a newer version with the problem, it is no longer present. - If the linked bug is marked as completed, but the Last seen column contains the most recent published version of the package, the Last seen column will be marked red. This is to indicate a *possible* regression. I'm still playing with this. Because Invalid bugs are also interpreted as complete, and because we only consider a bug complete when all of its bug tasks are complete, this is currently wrong in a few places. I was more interested in seeing how it presented, however. I have another deployment in the pipeline that speeds this request up by paying attention to the etags used by Launchpad and feeding it gzipped data.
-- Ubuntu-release mailing list Ubuntu-release@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-release