> On 11 July 2012 14:16, Andre Klapper <andre_klap...@gmx.net> wrote: > > KDE Bugzilla uses "RESOLVED UPSTREAM" for such cases, > > Mer Project uses "RESOLVED TRIAGEDUPSTREAM" for such cases.
I need to correct myself: Mer Bugzilla uses TRIAGEDUPSTREAM as a *state*, not as a resolution. Also, MeeGo Bugzilla uses "WAITINGFORUPSTREAM" as a state too. On Wed, 2012-07-11 at 17:11 +0300, Niklas Laxström wrote: > I'm okay with state, but not at all with resolution code. From the > reporters perspective the issue is not fixed when it is reported > upstream. For example if our Gerrit is broken, the issue not resolved > until a fix is applied in our installation. Good point - somebody would have to reopen the ticket after the fix has been committed upstream to get it deployed downstream (=WMF). So instead of using a resolution, a status WAITINGFORUPSTREAM seems to make more sense. Once a fix is available upstream somebody needs to manually reset the bug report status to UNCONF | NEW | ASSIGNED. andre -- Andre Klapper (maemo.org bugmaster & GNOME Bugsquad) http://blogs.gnome.org/aklapper/ _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
