[Libreoffice-qa] Bug Fixed in 4.2 branch, broken in 4.1 daily, status thoughts?

[Joel Madero]

Hm, just one thing is missing. In this case we know it's fixed but have no
idea what patch fixed it - as far as I know everyone marks these as WFM in
general and only marks as FIXED if we know what commit fixed the issue.

Am I missing something here?


Warm Regards,
Joel


On Wed, Jun 19, 2013 at 7:56 AM, Bjoern Michaelsen <
bjoern.michaelsen at canonical.com> wrote:

> On Wed, Jun 19, 2013 at 10:43:34AM -0400, Robinson Tryon wrote:
> > On Wed, Jun 19, 2013 at 6:09 AM, Bjoern Michaelsen
> > <bjoern.michaelsen at canonical.com> wrote:
> >
> > > So, if we use bugzilla as intended, a bug that is fixed, but not in a
> released
> > > version yet should be "RESOLVED/FIXED". Once that the release
> containing the
> > > fix is out it should go to "CLOSED/FIXED". Note the same happens on
> launchpad,
> > > albeit with better named bugstates: "Fix Committed" (aka RESOLVED) and
> "Fix
> > > Released" (aka CLOSED).
> >
> > Sounds like a great improvement to the strings in Bugzilla. Can we buy
> > Tollef a fruit basket or a nice dinner or something? It would be very
> > helpful if we could start to chew through our long list of tweaks...
>
> I guess, renaming bugstates is something we should have our own bugzilla
> for.
> Also note that even with the launchpad bug state names, people sometimes
> get it
> wrong -- although less so.
>
>
> > Why are we so hesitant about sending out emails on bug-status-change?
> > Is it because the entire cc list gets pinged, not just OP?
>
> Essentially yes. Its a change of workflow and http://xkcd.com/1172/applies.
>
> Best,
>
> Bjoern
>



-- 
*Joel Madero*
LibreOffice QA Volunteer
jmadero.dev at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/libreoffice-qa/attachments/20130619/ecbfb7e4/attachment.html>