[Mono-list] Mono Bug Day

[Daniel Morgan]

There are two email lists that will help:
- mono-bugs 
- mono-patches
 
If you subscribe to these mail lists, you will be able to get email about a new bug or a change in a bug or its status.  Also, mono-patches will allow you to peer review others code.
 
Maybe a Pre-Release Days instead of Bug Day would be more appropriate for Mono.  We could help with docs, update status info on the mono wiki, test building the pre-release tarballs, test a pre-release of the installers, etc...  And of course, make sure any serious bugs are squashed so we can have an outstanding stable release.
 
However, any pre-release tarballs, RPMs, or installers would not be downloadable from the Downloads page.  Maybe only available as ftp and the word prerelease is in the tarball or installer's filename.
 
Just some ideas...
 
I'll be waiting to see your wiki page.

"Paul F. Johnson" <paul at all-the-johnsons.co.uk> wrote:
Hi,

> >What needs to be done?
> > 
> >
> I think that putting the following couple of pages together on the Wiki :
> 
> - General informations on bug days :
> 
> * What is a bug day ?
> * Who can attempt ?

This would need to be split and preferably, peer mentored. For example, user
"a" may write and compile some code which clearly shows (say) MWF is broken
for spot colours. This is submitted and a peer proofs the code to see that
it's not user "a" who has made a boo-boo before submitting as a real bug.

> * When does it take place ?

Logistically, the third is the biggest one given the diversity of places
people are (I'm in the UK for instance while Peter (say) is out by 6 hours
from GMT). I'd suggest that the bug "day" would need to be split into two half
days for when the developers are around.

> - Detailed informations on what to do during a bug day :
> 
> This can be split in two parts : bug squashing and bug triaging :
> 
> * As for bug triaging :
> * How to find bug reports that are most important to triage ?
> * How to triage a bug report ?

All bugs are important, just some more than others. I remember finding one
very small bug in an application called TechWriterPro (it's a RISC OS app)
which when investigated, proved to be massive and set back the release
schedule by a month.

> * As for bug squashing :
> * How to find bug confirmed bug reports that are most important to fix ?
> * How to fix a bug ?

Ideally, the developers, though others should never be discouraged. This is
were the peer review comes into it's own - bugs which aren't bugs never get
past the reviewer.

> along with an IRC channel and a mailing-list to announce special events 
> (like special bug days before a release, etc.) could be a good step 
> forward :-).

Definitely!

> What do you think about this ? I can give some time to help organize 
> these bug squashing/triaging thing. I can write the wiki pages too .
> However, I think we should discuss about conventions used by mono 
> developers for the bugzilla system (like what version or milestone a bug 
> report should be assigned to, etc.) before doing it.

Sounds a very good set of ideas. Would this bug day be best set on a saturday
or sunday though? Whatever happens, I'm happy to give over as much time as I
can. I am using mono more and more now (especially as it forms the basis of
some of my research project) - I can give back this way :-)

TTFN

Paul
(watching MS.NET deinstall while thrashing the HD)
-- 
"Logic, my dear Zoe, is merely the ability to be wrong with authority" - Dr
Who


_______________________________________________
Mono-list maillist - Mono-list at lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-list/attachments/20050826/a40668dd/attachment.html