ubuntu-bugcontrol team mailing list archive

[Mathew Hodson <mathew.hodson@xxxxxxxxx>]

If I thought the change was too high risk or not severe enough to
justify a SRU, I would probably leave a note, but I wouldn't change the
status, because I think it is the SRU team that ultimately decides.

I would change the development task back to Confirmed if the original
fix never worked in the first place. If there was an error with the
patch, I would leave a note and try to fix it if I could. Status to
Triaged if everything looked good.

If the process wasn't followed correctly or there was information
missing, I would try to fix it up and add the necessary test case or
whatever is needed.

On 15-08-12 06:17 PM, Thomas Ward wrote:
> See below.
> 
> 
> 
> *Sent from my iPhone.  Please excuse any typos, as they are likely to happen by accident.*
> 
>> On Aug 12, 2015, at 18:08, Mathew Hodson <mathew.hodson@xxxxxxxxx> wrote:
>>> On 15-08-12 03:06 PM, Brian Murray wrote:
>>>> On Tue, Aug 11, 2015 at 05:11:16PM -0400, Mathew Hodson wrote:
>>>> <SNIP!>
>>>>
>>>> I am particularly interested in bugs that would be a good
>>>> candidate for or are going through the SRU process.
>>>
>>> How do you go about determining which bug reports are good
>>> candidates for a Stable Release Update? More specifically how do
>>> you find these types of bugs in Launchpad.
>>
>> If I find bugs that already have a Trusty task, I will add the SRU
>> template so that they are more likely to get picked up. I also keep an
>> eye out for bugs with a lot of heat or that I have seen complaints
>> about on other websites.
>>
>> Mostly I check
>> http://people.canonical.com/~ubuntu-archive/pending-sru.html and make
>> sure the tags and status are correct and try to verify if I am able.
> 
> So, one question from me on this:  What if it is marked as SRU, but the bug doesn't qualify, or the fixes don't work, or one of the edge cases where it is poorly prepared?
> 
> Or to put this question more simply, how do you identify if a bug is actually SRU-able?  What do you do when it isn't?  And what do you do when/if a bug as-is isn't SRU-ready?
> 
> (Actually curious for your response on this before I vote)
> 
> ------
> Thomas
>