Re: [Xen-devel] Fwd: Re: [Xen-users] bugzilla.xensource.com

["Henning Sprang" <henning_sprang@xxxxxx>]

On 1/30/07, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
> If you're volunteering to do some cleanup and co-ordination of the
> bugzilla that would be awesome! Its not a fun job, but you'd be making a
> very important contribution. You'd probably deserve a medal or
> something...
Somebody has to do it - I am thankful some people get into the nifty
hardware-level details, so helping with higher level programming on
tools and with these coordination things seems a good idea that
actually might help better than only ranting about the state :)


One thing I probably can't do what I see is currently wrong: the
"version" selection show only versions until 3.0.2. It should thought
about if there should be a selection only for each released version
plus unstable, or also for the -testing trees made availale at
xenbits.xensource.com.

Another thing I can't do on my own is that I really think at least
some developers should read the buglist, and basically every new
feature and function should be registered at least as a wishlist bug -
also meaning, when somebody has finished a feature and commmitted it
to some public tree, he has to close the associated bug.  Ideally,
nothing should happen that isn't registered there.

Maybe this gets a bit hard to handle as you probably have things you
want to work on without letting too many people know it so your
commercial products can surprise commercial users and competitors at
least a bit - but i think that's how it should work in general. I also
believe you make a better reputation with creating real open software
with a real open development and high quality than focusing on
surprises :)

> I'd really like to get the bugzilla into a state where the information
> it contains is up to date, the reports are detailed, and the
> prioritisation is reliable. Hence, folk will find it useful as a tool.
> Posting a weekly report of major open issues to xen-devel would be good
> too, so we can see how we're doing.
>
> I'd start by looking at any issue dormant for more than three months and
> close it unless you know it still to be live.
You suggest this should happen even without further testing?
That sounds actually really easy - there :)
Normally I'd try to be so accurate to actualy test if I can reproduce
each one before closing it.

Maybe at least major and critical ones should checked that way, and
bugs conatinaing patches should not be closed until it is known that
the patch has been applied or the bug otherwise been fixed, so no
contributions get lost.

On to work, I will start slowly these days by deeper looking into it,
getting my hands real dirty about next week when an important project
is (hopefully) finished.

@daniele: if you want to join, let's see how we can coordinate. I
don't mind doing it here, publicly, but for fast more direct
communication I hang around on irc (lazyb0y on freenode and oftc) and
have a jabber account - henning@xxxxxxxxxxxxx

Henning

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel