← Back to team overview

launchpad-dev team mailing list archive

high bugs - doing a bit of a review

 

Forwarding to the team since I failed first time.

On Thursday, November 18, 2010, Graham Binns <graham@xxxxxxxxxxxxx> wrote:
> On Thursday, November 18, 2010, Curtis Hovey <curtis.hovey@xxxxxxxxxxxxx> wrote:
>> On Fri, 2010-11-19 at 04:02 +1300, Robert Collins wrote:
>>> I want to get a better idea of what we've classified as high - as such
>>> I'm wandering through them all, and I may touch/downgrade whatever
>>> some of your pet bugs : if I do, and you disagree, please do put them
>>> to how you want them. I won't be downgrading them when the status is
>>> fresh etc : I'm not aiming to create any makework for folk, and I
>>> won't dispute if you toggle something back (or lower it further, etc).
>>
>> We only work on High bugs.
>
> This isn't true for the Bugs team, at least when we do story work.
>
>> I believe all high bugs should be targeted to
>> a milestone to show we are planning to work on it in the near future. If
>> a high bug is not ready to code, we are getting it ready to code, so
>> targeting to an feature/series milestone is often the right thing to do.
>> (If I could untarget from a series, I would suggest targeting to a
>> series).
>>
>
> Does that make sense with our new continuous deployment strategy?
> AFAICT the notion of a release / milestone now only applies to DB
> changes and other things that can't be continuously deployed.
>
> --
> Graham Binns
> http://grahambinns.com
>


-- 
Graham Binns
http://grahambinns.com



References