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


Hi,

On Thu, Oct 03, 2013 at 04:58:34PM +0100, Michael Meeks wrote:
* Stopping the BSA from auto-setting 'regression' keyword (Markus)
    + quality of 'regression' bugs has declined significantly, too many
      unconfirmed/needinfo bugs for calc.
        + bit de-motivating, to see 30% of bugs in needinfo -> because not a regression
    + in favour of removing it (Kohei)
        + used to have a special query, to pick up bugs with 'regression' keyword
        + # of bugs with 'regression' was approaching # of open calc bugs many in error.
    + a QA person should have looked at it before it is marked.
    + nice if BSA - make these suggestions - might be a regression, but not
      pollute the tags, QA person has to confirm it is (Robinson)
        => not making searches unusable.
AI: + ask Rob to turn 'regression' status off (Robinson)

Given the "QA person has to confirm it is" requirement, how about not
completely turning this of, but make the BSA e.g. add "possibleregression" to
whiteboard status?
That would:
- keep queries to 'regression' keyword clean for devs
- allows QA guys to query for 'possibleregression' and confirm/reject them
  (thus fasttracking real regressions to devs)

Sorry for reiterating ideas if this was already suggested in the call.

Best,

Bjoern, walking back to his tiny black-red-gold flag and looking very reunited

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.