← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/developers/bug-handling.txt

Merge fix for bug #583667 targeted at 2.2

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/bug-handling.txt
19
19
Links
20
20
*****
21
21
 
22
 
* `bzr bugs home page <https://bugs.edge.launchpad.net/bzr>`_.
23
 
 
24
 
* `Critical bugs <https://bugs.edge.launchpad.net/bzr/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed>`_.
25
 
 
26
 
* `Open bugs by importance <https://bugs.edge.launchpad.net/bzr/+bugs>`_.
 
22
* `bzr bugs home page <https://bugs.launchpad.net/bzr>`_.
 
23
 
 
24
* `Critical bugs <https://bugs.launchpad.net/bzr/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed>`_.
 
25
 
 
26
* `Open bugs by importance <https://bugs.launchpad.net/bzr/+bugs>`_.
27
27
 
28
28
* `Open bugs most recently changed first
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=>`_.
 
29
  <https://bugs.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=>`_.
30
30
 
31
31
* `Most commonly duplicated bugs <http://tinyurl.com/bzr-bugs-by-dupes>`_.
32
32
 
228
228
***************
229
229
 
230
230
It's possible to target a bug to a milestone, eg
231
 
<https://bugs.edge.launchpad.net/bzr/+milestone/1.16>.  We use this to help the
 
231
<https://bugs.launchpad.net/bzr/+milestone/1.16>.  We use this to help the
232
232
release manager know what **must** be merged to make the release.
233
233
 
234
234
Therefore, we don't target bugs that we'd like to have fixed or that could
313
313
    virtual filesystem for http, sftp, etc
314
314
 
315
315
trivial
316
 
    should be very easy to fix (10-20 minutes) and easily landed: typically just spelling errors and the like
 
316
    should be very easy to fix (10-20 minutes) and easily landed: typically 
 
317
    just spelling errors and the like
317
318
 
318
319
ui
319
320
    bugs relating to the bzr user interface, e.g. confusing error messages.
320
321
 
321
322
win32
322
 
    bugs that mainly affects Windows. Also there is cygwin and win98 tags for marking specific bugs.
 
323
    bugs that mainly affects Windows. Also there is cygwin and win98 tags for 
 
324
    marking specific bugs.
323
325
 
324
326
You can see the full list of tags in use at
325
 
<https://bugs.edge.launchpad.net/bzr/+bugs>.  As of September 2008 the
326
 
list is on the right.
 
327
<https://bugs.launchpad.net/bzr/+bugs>.  As of September 2008 the
 
328
list is on the right. 
327
329
 
328
330
.. vim: ft=rst