[00:19] wgrant: WTB reviews: https://code.launchpad.net/~stevenk/launchpad/spec-names-are-not-unique-vocab/+merge/190849 and https://code.launchpad.net/~stevenk/launchpad/unmute-tooltip/+merge/190857 [00:22] StevenK: Done. [03:24] wgrant: Something about QA? [03:24] Oh, forgot about that one [03:24] Doing [04:05] StevenK: done [04:54] lifeless: So, bug 1050173, Resolution: accepted is now Fix Released? The code currently maps closed/accepted to Fix Commited, and closed/fixed to Fix Released. [04:54] <_mup_> Bug #1050173: bugwatches set to accepted closed in python.org roundup maps to 'fix committed' not 'fix released' [04:55] lifeless: http://docs.python.org/devguide/triaging.html#resolution still mentions 'fixed' [05:45] StevenK: TTBOMK there is no 'fix released' concept in roundup [05:45] StevenK: those bugs will stay open forever if you try to model that [05:45] StevenK: http://bugs.python.org/issue1638033 + https://bugs.launchpad.net/python/+bug/96878 for instance [05:45] <_mup_> Bug #96878: Launchpad session cookie is accessible from Javascript [05:46] StevenK: 'accepted' is not listed in the devguide, but it's what bugs are set to in roundup AFAICT. Go figure. [05:47] StevenK: I would say both accepted and fixed should map to FR. [05:48] lifeless: I'd be curious to see what percentage of bugs are closed/accepted versus closed/fixed. [05:49] StevenK: public data, you can generate that :) [05:55] lifeless: Except that you can't search by Resolution: accepted :-) [05:56] Is accepted a resolution? [05:57] http://bugs.python.org/issue1638033 => Status: closed Resolution: accepted [05:59] I'm tempted to JFDI closed/accepted to Fix Released as lifeless says. === Gwaihir_ is now known as Gwaihir