I think for SRU bug reports, since we already specify a specific format for the bug description, it'd be helpful and simple to add the requirement that the debdiff for consideration / upload should be linked to in the main bug description. I find with larger bugs it's starting to get a bit tedious scrolling through all the bug commentary to figure out which patch is being submitted for consideration.


My inexcusable laziness aside, another benefit is there would be no doubt which is the "right patch" in case multiple attempts were made, etc.


What does everyone else think?

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

John Dong wrote:
> I think for SRU bug reports, since we already specify a specific format for
> the bug description, it'd be helpful and simple to add the requirement that
> the debdiff for consideration / upload should be linked to in the main bug
> description. I find with larger bugs it's starting to get a bit tedious
> scrolling through all the bug commentary to figure out which patch is being
> submitted for consideration.
>
> My inexcusable laziness aside, another benefit is there would be no doubt
> which is the "right patch" in case multiple attempts were made, etc.
>
>
> What does everyone else think?

Sounds like a good idea to me. I think this would also help speeding things up.

I just hope you don't invalidate bugs because they don't have a link in the
description. At least give us a transition period :-)

Best regards,
Emilio

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

On Mon, Dec 15, 2008 at 04:08:11PM +0000, John Dong wrote:
> I think for SRU bug reports, since we already specify a specific format for
> the bug description, it'd be helpful and simple to add the requirement that
> the debdiff for consideration / upload should be linked to in the main bug
> description. I find with larger bugs it's starting to get a bit tedious
> scrolling through all the bug commentary to figure out which patch is being
> submitted for consideration.
>
> My inexcusable laziness aside, another benefit is there would be no doubt
> which is the "right patch" in case multiple attempts were made, etc.
>
>
> What does everyone else think?

Seems sensible to me for bugs with more than a few comments.

Bryce

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

John Dong [2008-12-15 16:08 +0000]:
> I think for SRU bug reports, since we already specify a specific format for
> the bug description, it'd be helpful and simple to add the requirement that
> the debdiff for consideration / upload should be linked to in the main bug
> description.

That seems like busywork for most SRU bugs, but I agree it's a nice
thing to do for bugs with a lot of different attached patches.

Martin

--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

On 12/15/2008 02:15 PM, Martin Pitt wrote:
> John Dong [2008-12-15 16:08 +0000]:
>> I think for SRU bug reports, since we already specify a specific format for
>> the bug description, it'd be helpful and simple to add the requirement that
>> the debdiff for consideration / upload should be linked to in the main bug
>> description.
>
> That seems like busywork for most SRU bugs, but I agree it's a nice
> thing to do for bugs with a lot of different attached patches.

Interestingly, the SRUs I've been involved with for intrepid have had
messes of comments, and the only sane way to point ubuntu-sru (thanks!)
to them is to do precisely what John proposes.

--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel