[lsb-discuss] LSB bug processing (policy) question

Denis Silakov dsilakov at gmail.com
Wed Apr 4 13:46:12 UTC 2012

On 04/04/2012 05:20 PM, Wichmann, Mats D wrote:
>     It's not how bug reports are typically handled in my experience
>     with versioned releases. A bug usually stays with the same issue
>     ID throughout its life, regardless of whether it gets pushed to a
>     later version or not. Creating new bugs to effectively duplicate
>     an existing one seems to just be generating noise. I can
>     appreciate that creating a new bug for a later version may allow
>     better statistics, but I'd question how useful such statistics
>     would actually be (but my interests are likely much narrower than
>     those of others on this list).
> I avoided commenting at first, but now that two people have weighed 
> in, it turns out I agree with both:
> (1) as the submitter, it can become much harder to keep track of your 
> bug if it doesn't keep the same ID
> (2) bugzilla's clone function automatically attaches the old bug to 
> the new one (as does the dup resolutuion, fwiw), but does not clone 
> the comments that may have accumulated in the original bug and may be 
> vital to understanding and resolving - and it makes more work if you 
> have to trace back to a different bug.
> (3) for me, the reporting statistics of "bugs that were supposed to be 
> fixed but didn't get fixed in time" wouldn't hold a lot of value

Agree with all these points. Personally, I would prefer to leave our 
current state of art 'as is'.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lsb-discuss/attachments/20120404/e96f05ce/attachment.html>

More information about the lsb-discuss mailing list