> How about "#unbreak-before-it-hits-production"?

How about "#unbreak-before-it-hits-production"? Seriously. Once it does hit production, is it interesting that it was found on the beta cluster at some point in the past? Maybe for statistics of "we could fix before it hit production and didn't" ;) -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com ‪“We're living in pieces, I want to live in peace.” – T. Moore‬ 2015-10-05 21:07 GMT+03:00 Greg Grossmeier <greg(a)wikimedia.org>rg>: > ....in Phabricator. > > See this task for more background: > https://phabricator.wikimedia.org/T114486 > > Summary of what the problem was: > We routinely have tasks reported and included in the #Beta-Cluster > project that are software defects found when testing on Beta Cluster. > The fact that we found those issues on Beta Cluster is AWESOME and > GREAT. But they aren't issues with Beta Cluster the service and muddy up > the workboard (and any future potential reporting). > > Now: > * Issues with the infrastructure of Beta Cluster? Use > #Beta-Cluster-infrastructure > > * Did you find a bug in software that was deployed to the Beta Cluster? > Use #Beta-Cluster-reproducible > > If you aren't sure, you can just use #Beta-Cluster (which is an > additional hashtag to #Beta-Cluster-infrastructure) and we'll take care > of it. > > Greg > > > -- > | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | > | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D | > > _______________________________________________ > QA mailing list > QA(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/qa > _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l