Re: Mailing list behaviour was: Candidate questions/musings
On Wed, Mar 24, 2004 at 03:34:35PM +1100, Anand Kumria wrote: > Converting people to daily-digest mode is something that both Pascal and > I talked about recently. Considering the amount of acrimony various > participants have had, seen recently on debian-vote, and the fact that > some of the public (and private) intervention managed to cool things down > (a tiny amount). > > I think intervening and/or moving people to a daily-digest posting > method will be worthwhile. I'd much prefer a kinder, gentler Debian > development process -- that doesn't mean there can't be disagreements > though. We just need to be civil. Do you have a written proposal for how exactly this would work? -- G. Branden Robinson|If a man ate a pound of pasta and a Debian GNU/Linux |pound of antipasto, would they [EMAIL PROTECTED] |cancel out, leaving him still http://people.debian.org/~branden/ |hungry? -- Scott Adams signature.asc Description: Digital signature
Potential BTS improvements
I'm not quite sure what list I should be posting this to. There doesn't seem to be a list specifically for discussion about the bug tracking system (though there are plenty of operational bts lists). As I understand it, we're about to see an upgrade to the bug tracking system where closing a bug would be associated with a package version. This is a good thing. Here's some other possible improvements: [1] Allow bug reporters to become "active users". An active user would periodically receive automated messages about the status of their bug report, and we would be required to respond in a timely fashion or would drop them regular user status on that bug. [If the user wants to submit a public key, that can be used as their identity -- otherwise their identity is simply their email address, and without a public key, we should require round-trip confirmation on any information from that user.] This would allow us to say: if a bug report was introduced by an active user, then that bug report can only be closed by that user. To offset problems this might introduce, bugs which are tagged unreproducible would NOT be considered release critical unless a large number of active users had reported the bug*. The size of this number would be a judgement call on the part of the release manager. * because bugs can be merged, it's possible to have more than one person who reported the same bug. If this becomes a significant issue we might want to streamline this aspect of bug reporting. The important point, however, is distinguishing between "can't reproduce because of user error" and "real bug which can't be reproduced for some other reason". We might need to introduce some additional tags to indicate that a bug is believed to have been fixed and that we're waiting on confirmation. [2] Instead of simply opening and closing a bug, we should track which releases the bug appeared in, and which releases it's fixed in. Some of this is already supported in a sort of optional fashion (with tags). A lot of this can be automated (we know which package version has the fix, and can know which releases the package version appears in). It should be possible to orphan/nmu a package for a specific release, once a fix has appeared for some other release. [This is different orphaning the package entirely -- it's a statement on the part of the package maintainer that the release in question won't be supported.] Notes: The active user concept is somewhat influenced by what I read at http://www.joelonsoftware.com/articles/fog29.html All of the above fits under the "We won't hide problems" aspect of our social contract -- but there are a lot of critical details I've skimmed over. Comments? Thanks, -- Raul
Re: Potential BTS improvements
On Thu, Mar 25, 2004 at 02:04:22PM -0500, Raul Miller wrote: > I'm not quite sure what list I should be posting this to. There doesn't > seem to be a list specifically for discussion about the bug tracking > system (though there are plenty of operational bts lists). debian-debbugs > As I understand it, we're about to see an upgrade to the bug tracking > system where closing a bug would be associated with a package version. > This is a good thing. [...] > [2] Instead of simply opening and closing a bug, we should track which > releases the bug appeared in, and which releases it's fixed in. This will be part of the above. Cheers, -- Colin Watson [EMAIL PROTECTED]
Re: Mailing list behaviour was: Candidate questions/musings
On Wed, Mar 24, 2004 at 03:34:35PM +1100, Anand Kumria wrote: Converting people to daily-digest mode is something that both Pascal and I talked about recently. Considering the amount of acrimony various participants have had, seen recently on debian-vote, and the fact that some of the public (and private) intervention managed to cool things down (a tiny amount). I think intervening and/or moving people to a daily-digest posting method will be worthwhile. I'd much prefer a kinder, gentler Debian development process -- that doesn't mean there can't be disagreements though. We just need to be civil. I prefer my fellow Debian brothers to develop rhinocerous hides. :-) -- Eukleia: Jonathan Walther Address: 13685 Hilton Road, Surrey, BC V3R5J8 (Canada) Contact: 604-951-4142 (between 7am and 10pm, PST) Website: http://reactor-core.org signature.asc Description: Digital signature
Re: Mailing list behaviour was: Candidate questions/musings
to, 2004-03-25 kello 23:25, Jonathan Walther kirjoitti: > I prefer my fellow Debian brothers to develop rhinocerous hides. :-) I, however, have shed mine and don't intend to grow a new one. I'd rather be passive and a lurker. -- http://liw.iki.fi/liw/log/
Re: Potential BTS improvements
On Thu, Mar 25, 2004 at 02:04:22PM -0500, Raul Miller wrote: >... > [2] Instead of simply opening and closing a bug, we should track which > releases the bug appeared in, and which releases it's fixed in. Some of >... > Comments? Note that this requires (besides the technical infrastructure) additional work by the maintainers: Example: Segfault reported against the version in unstable. Bug fixed in unstable. Is the ancient version of this package in testing affected? I'm not saying that version tracking is useless, but to be usefull it requires additional work by the maintainers. > Thanks, > Raul cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
