Bazaar

Merge lp:~mbp/bzr/doc into lp:bzr

  1. doc
  2. Merge into bzr.dev
Proposed by Martin Pool
Status: Merged
Approved by: John A Meinel
Approved revision: no longer in the source branch.
Merged at revision: not available
Proposed branch: lp:~mbp/bzr/doc
Merge into: lp:bzr
Diff against target: 70 lines (+29/-14)
1 file modified
doc/developers/bug-handling.txt (+29/-14)
To merge this branch: bzr merge lp:~mbp/bzr/doc
Reviewer Review Type Date Requested Status
John A Meinel Approve
Review via email: mp+17186@code.launchpad.net
To post a comment you must log in.
Revision history for this message
Martin Pool (mbp) wrote :

See thread 'stop using fix-committed': this deprecates that bug status and expands on some related things.

Revision history for this message
John A Meinel (jameinel) wrote :

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:
> Martin Pool has proposed merging lp:~mbp/bzr/doc into lp:bzr.
>
> Requested reviews:
> bzr-core (bzr-core)
>
>
> See thread 'stop using fix-committed': this deprecates that bug status and expands on some related things.
>

Fits what the thread says, and I think states it well.

 review: approve
 merge: approve

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktL8M0ACgkQJdeBCYSNAAPBkACdEl2U/tnJLsFKoDdaWua4ZP09
+FIAoJ/LLGnucY/+Qwnoh1S+MGxfCFow
=M/ZB
-----END PGP SIGNATURE-----

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/developers/bug-handling.txt'
2--- doc/developers/bug-handling.txt 2009-12-02 20:34:07 +0000
3+++ doc/developers/bug-handling.txt 2010-01-12 02:28:12 +0000
4@@ -136,16 +136,26 @@
5 yet.
6 Incomplete
7 The bug requires more information from the reporter to make progress.
8+
9+ Only set this state if it's impossible or uneconomical to make
10+ progress on the bug without that information. The bug will expire if
11+ it remains in this state for two months.
12 Confirmed
13 The bug report has been seen by a developer and we agree it's a bug.
14- You don't have to reproduce the bug to mark it confirmed. (Generally
15+ You don't have to reproduce the bug to mark it Confirmed. (Generally
16 it's not a good idea for a developer to spend time reproducing the bug
17 until they're going to work on it.)
18 Triaged
19 We don't use this status. If it is set, it means the same as
20 Confirmed.
21 In Progress
22- Someone has started working on this.
23+ Someone has started working on this. We can deliver the value of the
24+ work already done by finishing and shipping the fix.
25+
26+ The bug keeps this state from the time someone does non-trivial
27+ analysis, until the fix is merged to a release or trunk branch (when
28+ it is Fix Released), or until they give up on it (back to New or
29+ Confirmed) or decide it is Invalid or Incomplete.
30 Won't Fix
31 The behaviour complained about is intentional and we won't fix it.
32 Needless to say, be thoughtful before using this status, and consider if
33@@ -154,20 +164,25 @@
34 The reporter was confused, and this is not actually a bug.
35 Again, be sensitive in explaining this to the user.
36 Fix Committed
37- A fix for this bug exists in a branch somewhere. Ideally the bug will
38- be linked to the branch.
39+ Don't use this. If set on old bug, it probably means In Progress,
40+ with the fix waiting for review. See Launchpad `bug 163694`_.
41 Fix Released
42 The fix for this bug is now in the bzr branch that this task is for.
43- The branch for the default task on a bug is bzr.dev. We use this value
44- even though the fix may not have been been included in a release yet
45- because all the developer activity around it is complete and we want to
46- both avoid bug spam when releases happen, and keep the list of bugs that
47- developers see when they look at the bug tracker trimmed to those that
48- require action. When setting a bug task to fix released, the bug target
49- milestone should be set to the release the fix will be included in (or
50- was included in, if you are updating an old bug). Don't spend too much time
51- updating this if you don't immediately know: its not critical that it be
52- set.
53+ The branch for the default task on a bug is bzr.dev.
54+
55+ We use this value even though the fix may not have been been included
56+ in a release yet because all the developer activity around it is
57+ complete and we want to both avoid bug spam when releases happen, and
58+ keep the list of bugs that developers see when they look at the bug
59+ tracker trimmed to those that require action.
60+
61+ When setting a bug task to fix released, the bug target milestone
62+ should be set to the release the fix will be included in (or was
63+ included in, if you are updating an old bug). Don't spend too much
64+ time updating this if you don't immediately know: its not critical
65+ that it be set.
66+
67+.. _`bug 163694`: https://bugs.launchpad.net/malone/+bug/163694
68
69
70 Bug Importance