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

[Sense Hofstede]

2009/2/5 (``-_-´´) -- BUGabundo <ubuntu at bugabundo.net>:
> Hi.
> Ever since 6.10 Beta 1, I've been a alpha/beta tester of all Ubuntu releases.
> Like me, there are several other users that at same point start testing the development branches.
>
> But the main difficulty I have in keeping track during the development are the changes that occur.
> I usually track the ReleaseNotes  and TechnicalOverview, and now we have _public_ meetings reports (which helps a tad more).
> 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.
>
>
> This would increase the notice of testers to changes, that easily slip into the cracks, and also help tracking regressions when filling bugs.
> Waiting for your comments and suggestions.
>
> --
> Hi, I'm BUGabundo, and I am Ubuntu (whyubuntu.com)
> (``-_-´´)       http://LinuxNoDEI.BUGabundo.net
> Linux user #443786    GPG key 1024D/A1784EBB
> My new micro-blog @ http://BUGabundo.net
> ps. My emails tend to sound authority and aggressive. I'm sorry in advance. I'll try to be more assertive as time goes by...
>
> --
> Ubuntu-devel-discuss mailing list
> Ubuntu-devel-discuss at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
>
>
It would indeed be a good idea to have a good overview of the made
changes in versions that are undergoing tests. Testers would know what
to check.
Maybe an Identi.ca stream, maybe partly automatically generated, would
be useful? Or weekly posts on the QA blog?

Regards,
-- 
Sense Hofstede
<http://www.qense.nl/>