GNOME/BugDays/20080611

From openSUSE

The code name for this Bug Day is "Finishing Up"

What: cleaning up openSUSE 10.3 bugs

• Continue with our effort to close GNOME related bugs from openSUSE 10.3 that are fixed for 11.0
• Clean up enhancements from 10.3 that are included in 11.0
• openSUSE 10.3 is available here

When: 11 June

11 Jun 2008, which is the day prior to our weekly meeting. We will start at 0900 EST and continue until sometime 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 irrelevant bugs in order to make it easier to find relevant bugs.
2. Draw attention to bugs which are still relevant.

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 Gobby for the duration of the BugDay.
  • See GNOME/BugDays/20080611/Progress after the meeting for a list of bugs that we managed to review during the event.
• Bugs may also be resolved INVALID, NORESPONSE, etc. as appropriate.
• Bugs which are still valid in 10.3 and sufficiently important may be moved to the openSUSE 10.3 or 11.0 product.
  • Please mark the OS field in bugzilla with the original distro the bug was found in
• 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