~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

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

Committer: Jelmer Vernooij
Date: 2011-05-04 13:09:19 UTC
mfrom: (5820 +trunk)
mto: This revision was merged to the branch mainline in revision 5844.
Revision ID: jelmer@samba.org-20110504130919-dhvgkeyvw04xsuv3

Merge bzr.dev

files modified:
bzrlib/bzrdir.py

bzrlib/smart/request.py

bzrlib/tests/blackbox/test_exceptions.py

bzrlib/tests/test_import_tariff.py

bzrlib/tests/test_selftest.py

bzrlib/tests/test_workingtree.py

bzrlib/workingtree.py

doc/developers/bug-handling.txt

doc/developers/contribution-quickstart.txt

Show diffs side-by-side

added added

removed removed

doc/developers/bug-handling.txt

When you file a bug as a Bazaar developer or active user, if you feel

confident in doing so, make an assessment of status and importance at the

time you file it, rather than leaving it for someone else. It's more

efficient to change the importance if someone else feel's it's higher or

efficient to change the importance if someone else feels it's higher or

lower, than to have someone else edit all bugs.

It's more useful to actually ship bug fixes than to garden the bug

184

time updating this if you don't immediately know: its not critical

185

that it be set.

186

187

.. _`bug 163694`: https://bugs.launchpad.net/malone/+bug/163694

187

.. _`bug 163694`: https://bugs.launchpad.net/launchpad/+bug/163694

188

189

190

Bug Importance

255

separate work to get it into that release.

256

257

258

The News File

258

Release Notes

259

*************

260

261

Most bugs that are fixed should be mentioned in a `NEWS

262

<../en/release-notes/NEWS.html>`_ file entry,

261

Most bugs that are fixed should be mentioned in the `Release Notes

262

<../en/release-notes/>`_ for the forthcoming version,

263

including the bug number.

264

(Exceptions might be bugs that are not at all user visible.)

265

267