[RFC] Improve communication with testing users about master key changes in development branches

[Dan Chen]

--- On Wed, 2/4/09, (``-_-´´) -- BUGabundo <ubuntu at bugabundo.net> wrote:

> Still, and understand I dont want to impose any more work
> to the already busy scribblers, but it would be nice to have
> either an email announcement, or a wiki page with ALL
> changes of policy, UI, package adding/removal.
> 
> Stuff like the changes PulseAudio in jaunty is an example
> of what would fit into this.

There have not been significant policy, UI, or package additions/
removals to base PulseAudio or ALSA userspace components in
jaunty. To what are you referring specifically?

> This would increase the notice of testers to changes, that
> easily slip into the cracks, and also help tracking
> regressions when filling bugs.

The kernel team has a similar page. However, the problem is one
of low signal to noise - lots of bugs being filed, many dozens
being duplicates, with people often chiming in with tangential
information.

I offer that the high priority bugs are very visible, and an
additional wiki page will not change how the developers
prioritise. It would be immensely helpful for an initial glance,
and perhaps drive-bys would find it useful.

Thanks,