Re: Killing off UNCONFIRMED in Bugzilla (renaming status names)
On 23/02/15 19:58, Andre Klapper wrote: On Mon, 2015-02-23 at 19:03 +0100, Andres G. Aragoneses wrote: If the alias feature ends up working, I'd like to add my 2cents here: For projects that opt-out, IMO the statuses should be UNCONFIRMED-CONFIRMED, as other developer has already suggested. I do not want both CONFIRMED and NEW statuses in Bugzilla, especially as you cannot disable one or the other per product. Too much confusion. Ok but my suggestion about OPEN remains. UNCONFIRMED-OPEN doesn't look too confusing. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Killing off UNCONFIRMED in Bugzilla (renaming status names)
On 14/02/15 20:50, Andre Klapper wrote: On Fri, 2015-02-13 at 21:43 +0100, Alexandre Franke wrote: BTW since 4.0 the new default workflow in bugzilla starts with UNCONFIRMED → CONFIRMED. This can be useful for those that keep UNCONFIRMED because sometimes reporters misinterpret NEW as not touched yet. Renaming the default status names in upstream made sense. For existing instances it breaks any bookmarks in your browser for search queries using URL parameters like bug_status=UNCONFIRMED. To me that is enough reason to be reluctant. andre PS: There is some undocumented alias feature in Bugzilla (no idea if it works with URL parameters) if anyone wants to play with that: http://bzr.mozilla.org/bugzilla/4.4/view/head:/template/en/default/global/value-descs.none.tmpl If the alias feature ends up working, I'd like to add my 2cents here: For projects that opt-out, IMO the statuses should be UNCONFIRMED-CONFIRMED, as other developer has already suggested. For the rest, the status NEW should really be renamed to OPEN. NEW has always had a horrible name, why NEW and not OLD? It's kinda confusing (for newcomers) too that oldest open bugs are still in NEW state. Thanks ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Killing off UNCONFIRMED in Bugzilla (renaming status names)
On Mon, Feb 23, 2015 at 1:22 PM, Andres G. Aragoneses kno...@gmail.com wrote: Ok but my suggestion about OPEN remains. UNCONFIRMED-OPEN doesn't look too confusing. UNCONFIRMED/NEW - UNRESOLVED would be my suggestion. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Killing off UNCONFIRMED in Bugzilla (renaming status names)
On 23/02/15 21:38, Michael Catanzaro wrote: On Mon, Feb 23, 2015 at 1:22 PM, Andres G. Aragoneses kno...@gmail.com wrote: Ok but my suggestion about OPEN remains. UNCONFIRMED-OPEN doesn't look too confusing. UNCONFIRMED/NEW - UNRESOLVED would be my suggestion. That suggestion is not clear. Andre has said that the NEW status cannot be different in the case of projects opting out of the UNCONFIRMED removal. So then there can only be 2 status names, not 3 as you suggest. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Killing off UNCONFIRMED in Bugzilla (renaming status names)
On Fri, 2015-02-13 at 21:43 +0100, Alexandre Franke wrote: BTW since 4.0 the new default workflow in bugzilla starts with UNCONFIRMED → CONFIRMED. This can be useful for those that keep UNCONFIRMED because sometimes reporters misinterpret NEW as not touched yet. Renaming the default status names in upstream made sense. For existing instances it breaks any bookmarks in your browser for search queries using URL parameters like bug_status=UNCONFIRMED. To me that is enough reason to be reluctant. andre PS: There is some undocumented alias feature in Bugzilla (no idea if it works with URL parameters) if anyone wants to play with that: http://bzr.mozilla.org/bugzilla/4.4/view/head:/template/en/default/global/value-descs.none.tmpl -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
