Last modified: 2013-05-29 12:04:30 UTC
This keyword should be for bugs related to any issues with replicated db's which are not accessible by wikimedia labs project admins, thus may not be fixed by them. Having such a word makes it easy for DBA (like Asher) who are responsible for replicated db's to be filtered as well as for labs admin to filter these bugs out (since they can't do anything about them). Right now there is a bunch of these bugs and I can't make a query that matches all labs-related bugs which I can fix, but doesn't have any DBA related stuff which I can't
Wouldn't a tracking bug, that you could actually cc asher onto work better for this?
First of all thanks for filing this (appreciated). Bug reports that fall into the proposed category so far were bug 48899, bug 48875. If I get it correctly this keyword would only be used for reports filed under the Bugzilla product "Wikimedia Labs"? If that's correct, it sounds like a usecase for a tracking bug (create a ticket, make it block bug 2007 and add the "tracking" keyword to it, and then mark bug 48899 and bug 48875 blocking that new tracking bug). I'd like to keep keywords cross-project (avoid keywords which are only useful for single products and would clutter the list of keywords for anybody not involved in that specific project). This is similar to how the ArticleFeedback-project-only "aftv5-1.5" keywords were removed in the past and turned into tracker bug 39043.
I don't know if you can exclude bugs that contains some tracking bug, but if you can, at some point I think we could just remove all keywords, replace them with tracking bugs and it would also work... but what would be point of doing that when we can just use keywords... This seems to me like the case where keywords are a best option. It is basically same as ops just in this case dba's are supposed to resolve it instead of ops (maybe we should just make the keywords "dba")
(In reply to comment #2) > First of all thanks for filing this (appreciated). > Bug reports that fall into the proposed category so far were bug 48899, bug > 48875. > > If I get it correctly this keyword would only be used for reports filed under > the Bugzilla product "Wikimedia Labs"? > If that's correct, it sounds like a usecase for a tracking bug (create a > ticket, make it block bug 2007 and add the "tracking" keyword to it, and then > mark bug 48899 and bug 48875 blocking that new tracking bug). > I'd like to keep keywords cross-project (avoid keywords which are only useful > for single products and would clutter the list of keywords for anybody not > involved in that specific project). > This is similar to how the ArticleFeedback-project-only "aftv5-1.5" keywords > were removed in the past and turned into tracker bug 39043. I don't know if it falls only under wikimedia labs - the replicated db's may be used even somewhere else within the infrastructure, if they are not, they might be in the future. There are many bugs that are supposed to be there, not just these 2. I was going to flag the remaining soon
Tracking bug sounded more approporiate in this case: bug 48930 Closing.
