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
=== modified file 'doc/developers/bug-handling.txt'
--- doc/developers/bug-handling.txt 2009-12-02 20:34:07 +0000
+++ doc/developers/bug-handling.txt 2010-01-12 02:28:12 +0000
@@ -136,16 +136,26 @@
136 yet.136 yet.
137Incomplete137Incomplete
138 The bug requires more information from the reporter to make progress.138 The bug requires more information from the reporter to make progress.
139
140 Only set this state if it's impossible or uneconomical to make
141 progress on the bug without that information. The bug will expire if
142 it remains in this state for two months.
139Confirmed143Confirmed
140 The bug report has been seen by a developer and we agree it's a bug.144 The bug report has been seen by a developer and we agree it's a bug.
141 You don't have to reproduce the bug to mark it confirmed. (Generally145 You don't have to reproduce the bug to mark it Confirmed. (Generally
142 it's not a good idea for a developer to spend time reproducing the bug146 it's not a good idea for a developer to spend time reproducing the bug
143 until they're going to work on it.)147 until they're going to work on it.)
144Triaged148Triaged
145 We don't use this status. If it is set, it means the same as149 We don't use this status. If it is set, it means the same as
146 Confirmed.150 Confirmed.
147In Progress151In Progress
148 Someone has started working on this.152 Someone has started working on this. We can deliver the value of the
153 work already done by finishing and shipping the fix.
154
155 The bug keeps this state from the time someone does non-trivial
156 analysis, until the fix is merged to a release or trunk branch (when
157 it is Fix Released), or until they give up on it (back to New or
158 Confirmed) or decide it is Invalid or Incomplete.
149Won't Fix159Won't Fix
150 The behaviour complained about is intentional and we won't fix it.160 The behaviour complained about is intentional and we won't fix it.
151 Needless to say, be thoughtful before using this status, and consider if161 Needless to say, be thoughtful before using this status, and consider if
@@ -154,20 +164,25 @@
154 The reporter was confused, and this is not actually a bug.164 The reporter was confused, and this is not actually a bug.
155 Again, be sensitive in explaining this to the user.165 Again, be sensitive in explaining this to the user.
156Fix Committed166Fix Committed
157 A fix for this bug exists in a branch somewhere. Ideally the bug will167 Don't use this. If set on old bug, it probably means In Progress,
158 be linked to the branch.168 with the fix waiting for review. See Launchpad `bug 163694`_.
159Fix Released169Fix Released
160 The fix for this bug is now in the bzr branch that this task is for.170 The fix for this bug is now in the bzr branch that this task is for.
161 The branch for the default task on a bug is bzr.dev. We use this value171 The branch for the default task on a bug is bzr.dev.
162 even though the fix may not have been been included in a release yet172
163 because all the developer activity around it is complete and we want to173 We use this value even though the fix may not have been been included
164 both avoid bug spam when releases happen, and keep the list of bugs that174 in a release yet because all the developer activity around it is
165 developers see when they look at the bug tracker trimmed to those that175 complete and we want to both avoid bug spam when releases happen, and
166 require action. When setting a bug task to fix released, the bug target176 keep the list of bugs that developers see when they look at the bug
167 milestone should be set to the release the fix will be included in (or177 tracker trimmed to those that require action.
168 was included in, if you are updating an old bug). Don't spend too much time178
169 updating this if you don't immediately know: its not critical that it be179 When setting a bug task to fix released, the bug target milestone
170 set.180 should be set to the release the fix will be included in (or was
181 included in, if you are updating an old bug). Don't spend too much
182 time updating this if you don't immediately know: its not critical
183 that it be set.
184
185.. _`bug 163694`: https://bugs.launchpad.net/malone/+bug/163694
171186
172187
173Bug Importance188Bug Importance