GNOME/BugDays/20080307

From openSUSE

The code name for this Bug Day is "Bug Munching"

Contents

What: cleaning up openSUSE 10.2 Bugs

When: 7 March

Friday, 7th of March 2008, which is next to our weekly meeting, so more people are expected to show up

Where: #openSUSE-gnome

FreeNode #openSUSE-gnome

Why: should enable us to focus on current and factory bugs as we move forward

  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

  • While all participants are in, anybody can start working on a bug as long as they have announced it on #openSUSE-gnome, that is to avoid duplication and the waste of everybody's time
  • Bugs which have been fixed in subsequent versions of openSUSE can be resolved FIXED.
  • 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.
  • 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 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