Nautilus

Differences between revisions 16 and 17
Revision 16 as of 2010-01-28 16:30:19
Size: 4123
Editor: ck752853-a
Comment: Fixed typo in mark-up
Revision 17 as of 2010-02-05 21:58:00
Size: 4340
Editor: ck752853-a
Comment: Added the status of today
Deletions are marked like this. Additions are marked like this.
Line 48: Line 48:
||2010-02-05 21:55||{'need_forwarding': 0, 'per_status': {'In Progress': 3, 'Confirmed': 1, 'Invalid': 2480, 'New': 41, 'Fix Committed': 0, 'Triaged': 602, 'Fix Released': 759, 'Incomplete': 172, "Won't Fix": 17}}||

On this page the adoption of Nautilus is tracked.

Overview

Source package

nautilus

Upstream bug tracker

http://bugzilla.gnome.org/

Tasks

Because there are so many bugs filed against Nautilus we divide the different tasks between people.

  • More than one people can be assigned to one task. However, before adding yourself to the table, please contact the BugSquad maillist first.

  • It is NOT required to be on this list if you want to triage bugs reported against Nautilus.

task

assignee

New Bugs

Yazen Ghannam, Bruno Girin malev

Confirmed Bugs

Sense Hofstede

Forwarding upstream

Sense Hofstede, Bruno Girin

Old bugs

Sense Hofstede

A short explanation of the different tasks:

New Bugs

You look after 'New Bugs' and process them appropriately.

Required

  • A Launchpad account

Look at the Untriaged bugs section of Bugs/HowToTriage for an explanation of the required actions for this task.

Confirmed Bugs

You check for Confirmed bugs that are not being looked after or that need to be set to Triaged and do with them whatever is needed.

Look at the Confirmed bugs section of Bugs/HowToTriage for an explanation of the required actions for this task.

Required

Forwarding upstream

You forward bugs upstream. These reports need to contain enough information to be useful to the developers, we don't want to force them to start the triaging process over again. You could start with bugs that are marked as needing forwarding or go through the Triaged bugs yourself.

Required

  • A Launchpad account
  • An account for the upstream bug tracker

Look at theForwarding upstream section of Bugs/HowToTriage for an explanation of the required actions for this task.

Old Bugs

This is a bit of a special kind of task since it's not limited to any specific kind of stage of the triaging process like the tasks above. Instead you focus on bug reports that have been lingering around for a while. You:

  • Verify if the bug can still be reproduced on supported releases
  • Triage the bug

After a while you should be finished with this task since thisadoption team keeps the package tidy and clean. However, it might be wise to still keep an eye out for bugs that are forgotten.

Required

  • A Launchpad account

Guidelines

Please keep the follow these guidelines when triaging:

  • When a bug is ready to be forwarded upstream, but it's not your task, please open an empty upstream task; that will make it show up as such. Bugs/Upstream explains how to do this.

Status

date

score entry

2010-01-18 15:08

{'Confirmed': 2, 'Invalid': 2272, 'New': 37, 'Fix Committed': 2, 'Triaged': 578, 'Fix Released': 754, 'Incomplete': 162, "Won't Fix": 16}

2010-01-21 16:15

{'need_forwarding': 5, 'per_status': {'In Progress': 3, 'Confirmed': 0, 'Invalid': 2279, 'New': 34, 'Fix Committed': 1, 'Triaged': 583, 'Fix Released': 754, 'Incomplete': 158, "Won't Fix": 16}}

2010-01-28 16:18

{'need_forwarding': 5, 'per_status': {'In Progress': 3, 'Confirmed': 3, 'Invalid': 2463, 'New': 37, 'Fix Committed': 0, 'Triaged': 593, 'Fix Released': 756, 'Incomplete': 166, "Won't Fix": 17}}

2010-02-05 21:55

{'need_forwarding': 0, 'per_status': {'In Progress': 3, 'Confirmed': 1, 'Invalid': 2480, 'New': 41, 'Fix Committed': 0, 'Triaged': 602, 'Fix Released': 759, 'Incomplete': 172, "Won't Fix": 17}}

BugSquad/AdoptPackage/Nautilus (last edited 2010-04-20 15:27:58 by ck752853-a)