Bug days take place on irc.gnome.org in #evolution from 1500 GMT to 0100 GMT (the next day).
If you decide to participate, we'll give you 10 (ten) nice bugs reports to work on; those reports may be be within one and maybe more of the following categories:
Bugs that have been a long time in the database but aren't still fixed for any reason. You can check them in http://bugzilla.ximian.com/old-bugs-needing-love.cgi?num=x (Please ask us about the current value of x)
These bugs were triaged and added a keyword that simply put means “I think I've seen this report before, but can't find it in bugzilla”. In other words 'It's dèja vu all over again'. Here, check in http://bugzilla.ximian.com/probabledups-needing-love.cgi?num=x "
Features requested by the community. Some of them can be essential for the perfect mailer, some others are requests suited for a handful of users, and some are plain crackpot: as one Evo developer said: 'I have one simple request.... and that is to have messages with freakin' laser beams attached to their headers.'
Triaging wishlist reports sometimes requires a lot more attention, since it's requirements' analysis. So phrasing, keywords and suggested actions are important.
These are in http://bugzilla.ximian.com/wishlist-bugs-needing-love.cgi?num=x.
Reports arising from eventual crashes in Evolution. Sometimes they actually have been reproduced, but other times crashes were due to particular configurations, once-in-a-lifetime events. However, from time to time some problems were solved and someone simply forgot to close the report, or more than one problem was solved at once and the second report wasn't properly closed
Check for these in http://bugzilla.ximian.com/crash-bugs-needing-love.cgi?num=x
For all bugs:
Is it working now?
This is a simple answer to a bug. 'It works for me / Now works'. Then report needs to be closed.
Are they already properly triaged (Be aware that this triage page is specific for GNOME and some of the links point to GNOME Bugzilla while we are dealing with Ximian Bugzilla)
This means that they have already been assigned at least
A component (This means it isn't assigned to 'triage', but any of Evolution components
A target milestone (even if it's 'Future'). This means that it has been acknowledged as a software problem.
Is it a duplicate?
Well, finding duplicates is not an easy task as it seems at first. We'll talk a little more when talking about probable dups.
Don't understand what is this report about...!
No problem, simply let it alone :)
Now, specific things to check about each group:
Old Bugs:
If it doesn't work and it's properly triaged, it must remain as it is.
BUT:
If target milestone is in the past (Anything that's not 1.4.x, Future, contrib or reschedule) then we have to update milestone. Please let us know!
Probable duplicates.
Query the database with keywords from description, If the report has a backtrace, try to use the code near the crash point. Look for similar backtraces and the set of actions that led to the crash.
If there's no backtrace then try to search for the most descriptive words, as 'laser beams headers'
Be careful, some descriptions are very much alike, but point to different problems.
If you find the perfect match, please let us know.
Crashers
Try to reproduce it
If you can reproduce it, the report should stay. Check then if it's a duplicate.
Wishlist
Basically, check if the requested enhancement is there now. If it's there, then we must close it.
Check if it is a duplicates
So basically that all. Have fun!