[tomboy-list] Scheduling a Bug Day

[Sandy Armstrong]

On Sat, May 2, 2009 at 11:23 AM, Michael Fletcher
<m.fletcher at theplanet.ca> wrote:
> I think we should plan how we will tackle this bugday before it begins.

Yes, definitely.  I'm not comfortable scheduling a bug day without a
solid plan first.

> Perhaps set priorities like
>
> 1. Test/apply bugs scheduled to 0.15.
> 2. Triage bugs scheduled to 0.15.
> 3. Triage the remaining UNCONFIRMED bugs and schedule them to Future or 0.15.
>
> A wiki page with planning notes and bugzilla queries would help this
> along.  Ooops.  Did I just volunteer myself ???

That is a great idea.  Some things we could do:

* Test outstanding patches, leave comments on those that no longer
apply, follow-up on those that do
* Get rid of as many UNCONFIRMED bugs as possible
* Schedule them, as Mike suggests
* Consider going as far as creating milestones for each upcoming
0.15.x release, and scheduling bugs for each milestone?
* Mark gnome-love (if you have a clue about how hard it would be to
work on a given bug)
* And, of course, looking at old bugs with no recent updates to see if
they're still valid

Would love to just point people at a wiki page with simple
instructions, and have everything go smoothly.

Once we know what we're doing, let's schedule a day.  :-)  And yes,
let's do it soon!

Sandy