Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


On Tue, Jun 23, 2015 at 3:51 PM, Joel Madero <jmadero.dev@gmail.com> wrote:
On 06/23/2015 12:32 PM, Bjoern Michaelsen wrote:
Hi,

On Sun, May 31, 2015 at 01:14:54PM -0700, Joel Madero wrote:
So the time has finally arrived that we are moving forward with _locking
out priority/severity_. This means that *MAB will be retired*.
I'd like to suggest to add this query as a reocurring item for the Robinson and
the rest of the call to look at during the QA section of the ESC call:

 
https://bugs.documentfoundation.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&bug_status=NEEDINFO&bug_status=PLEASETEST&chfield=priority&chfieldfrom=-8d&chfieldto=Now&chfieldvalue=highest&list_id=545001&priority=highest&product=LibreOffice&query_format=advanced&resolution=---

It shows:

- open bugs
- that were changed to priority highest (thus a MAB) in the last 8 days
  (aka ~since the last call)
- and currently are still priority highest (and thus a MAB)

This is for the ESC to both be aware of newly marked important bugs -- and also
to weed out one or another wrongly marked high priority bug. Also, this should
help us keep the total number of high priority bugs both under control and on
the radar.

@Robinson: Can you take that up?

Sure, I'll take a look at that.

Along with this - I created the patch months ago that is sitting in the
test instance to block priority/severity from being changed by
"non-contributors." Beluga and I put in some time adding all devs and QA
members (or at least the vast majority) to a new group in bugzilla so
that they will have the rights without requesting. At this point I'm
just waiting for Robinson to give me some feedback as to what the hold
up is.

I'm happy to deploy the changes to production asap -- perhaps tomorrow
after the ESC call would work well. I just want to make sure that I
have some QA folks available to hammer on the changes and make sure
nothing wonky has happened. I don't think that we'll see any
interference between the patches and the git-integration for the devs,
but that'll be another piece to double-check.

Cheers,
--R

-- 
Robinson Tryon
QA Engineer - The Document Foundation
LibreOffice Community Outreach Herald
qubit@libreoffice.org
802-379-9482 | IRC: colonelqubit on Freenode

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.