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
2009/2/5 (``-_-´´) -- BUGabundo ubu...@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
Olá Sense e a todos.
On Thursday 05 February 2009 18:32:54 Sense Hofstede wrote:
Maybe an Identi.ca stream, maybe partly automatically generated, would
be useful? Or weekly posts on the QA blog?
As much as I like µblogging and RSS feeds, I rather have a choice for email.
--
Hi, I'm
--- On Wed, 2/4/09, (``-_-´´) -- BUGabundo ubu...@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.
Olá Dan e a todos.
On Thursday 05 February 2009 19:16:27 Dan Chen wrote:
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
--- On Thu, 2/5/09, (``-_-´´) -- BUGabundo ubu...@bugabundo.net wrote:
I mean the going away of the old alsa controls that opened
from the audio applet.
So you'd like documented the changes in Desktop components.
Maybe I wasnt clear here:
This is not meant FOR Devs, but for testers and
Olá Dan e a todos.
On Thursday 05 February 2009 19:32:27 Dan Chen wrote:
--- On Thu, 2/5/09, (``-_-´´) -- BUGabundo ubu...@bugabundo.net wrote:
I mean the going away of the old alsa controls that opened
from the audio applet.
So you'd like documented the changes in Desktop components.
We use package changelogs to describe some changes; you can find them in
/usr/share/doc/$package/changelog.*
As for volunteering, I was referring specifically to making the wiki document.
I already expend countless non-job hours working on the packages, so any
additional effort by other
