28
28
* `Open bugs most recently changed first
29
29
<https://bugs.edge.launchpad.net/bzr/+bugs?field.searchtext=&orderby=-date_last_updated&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=>`_.
31
* `Most commonly duplicated bugs <http://tinyurl.com/bzr-bugs-by-dupes>`_.
53
51
report, but they generally care more about getting bugs fixed.
55
53
The aim of investigating bugs before starting concentrated work on them is
58
56
* determine if they are critical or high priority (and
59
57
should displace existing work)
140
138
The bug requires more information from the reporter to make progress.
142
Only set this state if it's impossible or uneconomical to make
143
progress on the bug without that information. The bug will expire if
144
it remains in this state for two months.
146
The bug report has been seen by a developer and we agree it's a bug.
147
You don't have to reproduce the bug to mark it Confirmed. (Generally
140
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. (Generally
148
142
it's not a good idea for a developer to spend time reproducing the bug
149
143
until they're going to work on it.)
151
145
We don't use this status. If it is set, it means the same as
154
Someone has started working on this. We can deliver the value of the
155
work already done by finishing and shipping the fix.
157
The bug keeps this state from the time someone does non-trivial
158
analysis, until the fix is merged to a release or trunk branch (when
159
it is Fix Released), or until they give up on it (back to New or
160
Confirmed) or decide it is Invalid or Incomplete.
148
Someone has started working on this.
162
150
The behaviour complained about is intentional and we won't fix it.
163
151
Needless to say, be thoughtful before using this status, and consider if
166
154
The reporter was confused, and this is not actually a bug.
167
155
Again, be sensitive in explaining this to the user.
169
Don't use this. If set on old bug, it probably means In Progress,
170
with the fix waiting for review. See Launchpad `bug 163694`_.
157
A fix for this bug exists in a branch somewhere. Ideally the bug will
158
be linked to the branch.
172
160
The fix for this bug is now in the bzr branch that this task is for.
173
The branch for the default task on a bug is bzr.dev.
175
We use this value even though the fix may not have been been included
176
in a release yet because all the developer activity around it is
177
complete and we want to both avoid bug spam when releases happen, and
178
keep the list of bugs that developers see when they look at the bug
179
tracker trimmed to those that require action.
181
When setting a bug task to fix released, the bug target milestone
182
should be set to the release the fix will be included in (or was
183
included in, if you are updating an old bug). Don't spend too much
184
time updating this if you don't immediately know: its not critical
187
.. _`bug 163694`: https://bugs.launchpad.net/malone/+bug/163694
161
The branch for the default task on a bug is bzr.dev. We use this value
162
even though the fix may not have been been included in a release yet
163
because all the developer activity around it is complete and we want to
164
both avoid bug spam when releases happen, and keep the list of bugs that
165
developers see when they look at the bug tracker trimmed to those that
166
require action. When setting a bug task to fix released, the bug target
167
milestone should be set to the release the fix will be included in (or
168
was included in, if you are updating an old bug). Don't spend too much time
169
updating this if you don't immediately know: its not critical that it be
274
257
authenticating to servers
277
260
candidate for backporting to an update of the previous release
283
266
should be possible to finish in an hour or two
286
269
bugs about the High-Performance Smart Server, i.e. bzr+ssh://, etc.
289
272
bugs for causes of VFS methods of the smart server
292
275
bugs about interactions with launchpad (typically this means bzrlib.plugins.launchpad).
295
278
problems using locales other than English
298
281
problems where we use too much memory for some reason
301
284
fixing this would need a new disk format
304
287
bugs about performance problems.
307
290
needs changes to the test framework
310
293
virtual filesystem for http, sftp, etc
313
296
should be very easy to fix (10-20 minutes) and easily landed: typically just spelling errors and the like
316
299
bugs relating to the bzr user interface, e.g. confusing error messages.
319
bugs that mainly affects Windows. Also there is cygwin and win98 tags for marking specific bugs.
302
bugs that mainly affects Windows. Also there is cygwin and win98 tags for marking specific bugs.
321
304
You can see the full list of tags in use at
322
305
<https://bugs.edge.launchpad.net/bzr/+bugs>. As of September 2008 the
323
list is on the right.
306
list is on the right.
added
removed
doc/developers/bug-handling.txt
