The Topic for today is:

1. Changed behaviour of Apport crash bugs (Martin Pitt)

Hello fellow Ubuntu developers,

Until now, crash bugs filed by Apport [1] had two major problems:

* They potentially contain sensitive information in the core dump and
stack traces.

* 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 [2] 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
as public.

I added some detailed explanations to the HowToTriage wiki page [3],
which also describes the steps bug triagers should do with Apport
generated crash bugs.

Thank you,

Martin

[1] https://wiki.ubuntu.com/Apport
[2] https://wiki.ubuntu.com/CrashReporting
[3] https://wiki.ubuntu.com/Bugs/HowToTriage#head-f46ac7bd66be716a03d2d4fb0788725cc9cc7ba0

—
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org

thats all for now!

Here is the hint for today and yesterday: 35 35 20 36 32 20 37 35 20 36 65 20 37 34 20 37 35 20

this is the actual password for Friday July 6th You are so Close to Finding out What the huge Secret is. PS I change the password everyday so the password will not be the same everyday.