Changed behaviour of Apport crash bugs
martin.pitt at ubuntu.com
Fri Jul 6 11:44:38 BST 2007
Hello fellow Ubuntu developers,
Until now, crash bugs filed by Apport  had two major problems:
* They potentially contain sensitive information in the core dump and
* They produce a lot of bug email noise; a lot of it is redundant,
and with the new automatic duplicate detection a lot of those bugs
do not need to be looked at at all any more.
Eventually, Launchpad will grow a proper concept of a crash database
to fix that. Until we get that, we need a quick fix for that, which is
why I implemented  now:
* Crash bugs are filed private now, with only ubuntu-core-dev (for
main/restricted) and ubuntu-dev (for universe/multiverse) members
being able to see them initially. After verifying that there is no
sensitive data, the bugs can be marked as public if there is a
reason to do so (like pointing upstreams to it).
* There will be no bug email sent at all until someone marks a bug
I added some detailed explanations to the HowToTriage wiki page ,
which also describes the steps bug triagers should do with Apport
generated crash bugs.
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/ubuntu-devel-announce/attachments/20070706/06bf1c81/attachment.pgp
More information about the ubuntu-devel-announce