GNOME/BugDays/20090514

From openSUSE

The code name for this Bug Day is "Community Effort"

What: cleaning up openSUSE 11.1 Blocker/Critical/Major bugs

• Temporary GNOME bug list slated for Community Week
• openSUSE 11.1 is available here

When: 15 May

15 MAY 2009, the last day of Community Week We will start at 1100 EDT and continue until 1700 EDT that evening. See this link to calculate the time for your timezone.

Where: #openSUSE-gnome

On Freenode (irc.freenode.net) in #openSUSE-gnome

Why: it will make life easier

1. Close high severity bugs in 11.1.
2. Have fun being involved in Community Week

How: roll up your sleeves

• We will work on bugs in 5-10 bug blocks that will be announced in-channel. If you wish to work on a bug, please announce it in the channel first to avoid duplication.
  • A list of the bugs for review in progress will be kept by Christopher Hobbs (hobbsc) and whomever is assisting with coordination.
  • The active list of bugs in progress will be viewable through a Gobby session (TBA) for the duration of the BugDay.
• Bugs may also be resolved INVALID, NORESPONSE, etc. as appropriate.
• Bugs which are still valid but for which we are unlikely to commit resources (or which we'd rather have fixed in close coordination with the upstream community) should be tagged with the should_go_upstream keyword
• When upstream bugs already exist for should_go_upstream bugs, the upstream bug's URL should be noted in our bug, which can then be resolved LATER. Someone should get CC'ed on the upstream bug in order to note changes.
• When no upstream bug exists for a should_go_upstream bug, and the bug is still valid in current upstream code, a bug should be filed upstream, and the URL for the new upstream bug should be noted in our bug, which we can then resolve LATER.
• Details of the bug policy are available elsewhere.
• Virtualization might be useful when dealing with large numbers of older distros. Choices include VMWare and VirtualBox