After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 744312 - Kill unconfirmed state for most products
Kill unconfirmed state for most products
Status: RESOLVED FIXED
Product: bugzilla.gnome.org
Classification: Infrastructure
Component: products and taxonomy
unspecified
Other Windows
: High normal
: ---
Assigned To: Olav Vitters
Bugzilla Maintainers
: 658470 (view as bug list)
Depends on:
Blocks: 138046
 
 
Reported: 2015-02-11 09:34 UTC by Olav Vitters
Modified: 2015-02-28 14:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Olav Vitters 2015-02-11 09:34:22 UTC
Almost every product does not make use of UNCONFIRMED.

We should:
1. Ask on desktop-devel-list which products use that state (IIRC gimp)
2. Change all UNCONFIRMEDs to NEW (mass change, SQL will miss out on some needed things). Make sure to not change it for products which use it!
3. Change the "Enable the UNCONFIRMED status in this product" for all products (SQL)
4. Change the "Enable the UNCONFIRMED status in this product" back for the few products which actually need it
Comment 1 André Klapper 2015-02-14 21:42:13 UTC
Related discussion:
https://mail.gnome.org/archives/desktop-devel-list/2015-February/msg00129.html
Comment 2 Michael Schumacher 2015-02-14 23:36:18 UTC
Questions:

1. What issue is this change supposed to address?

If it starts with "The user might...!!!!1!", then:

2. Has the upstream change mentioned in https://mail.gnome.org/archives/desktop-devel-list/2015-February/msg00142.html been taken into account for this decision?
Comment 3 André Klapper 2015-02-15 01:06:39 UTC
(In reply to Michael Schumacher from comment #2)
> 1. What issue is this change supposed to address?

The numerous "Why has this not been confirmed yet?!" comments by Bugzilla users that I've seen over the last years in bug reports of those products in GNOME Bugzilla where no developer or maintainers cares about UNCONF vs NEW (in my impression that's the majority). No need to create confusion by using two things for the very same thing.

> 2. Has the upstream change mentioned in
> https://mail.gnome.org/archives/desktop-devel-list/2015-February/msg00142.
> html been taken into account for this decision?

See my reply on the mailing list.
Comment 4 André Klapper 2015-02-27 15:04:37 UTC
*** Bug 658470 has been marked as a duplicate of this bug. ***
Comment 5 Olav Vitters 2015-02-27 16:14:42 UTC
FYI: I probably only do this on Sat.

Various people asked all kinds of other things. I think we should take one step at a time. First kill UNCO for most, then look at the rest of the workflow.

IMO ASSIGNED -> IN_PROGRESS (or something) makes sense.
Comment 6 Olav Vitters 2015-02-28 14:58:36 UTC
mysql> update products SET allows_unconfirmed = 0 where products.name not in ('gnome-contacts', 'gnome-calendar', 'planner', 'gnome-music', 'gedit', 'gtksourceview', 'latexila', 'Pitivi', 'GIMP', 'gimp-web', 'banshee');Query OK, 592 rows affected (0.02 sec)
Rows matched: 604  Changed: 592  Warnings: 0


mysql> UPDATE bugs bugs inner join products on bugs.product_id = products.id SET bug_status = 'NEW', everconfirmed = 1 where products.name not in ('gnome-contacts', 'gnome-calendar', 'planner', 'gnome-music', 'gedit', 'gtksourceview', 'latexila', 'Pitivi', 'GIMP', 'gimp-web', 'banshee') and bug_status = 'UNCONFIRMED';
Query OK, 26725 rows affected (2.11 sec)
Rows matched: 26725  Changed: 26725  Warnings: 0