~bzr-pqm/bzr/bzr.dev

* `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>`_.

* `Open bugs by importance <https://bugs.launchpad.net/bzr/+bugs>`_.

* `bzr bugs home page <https://bugs.edge.launchpad.net/bzr>`_.

* `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>`_.

* `Open bugs by importance <https://bugs.edge.launchpad.net/bzr/+bugs>`_.

* `Open bugs most recently changed first

<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=>`_.

<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=>`_.

* `Most commonly duplicated bugs <http://tinyurl.com/bzr-bugs-by-dupes>`_.

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 feels it's higher or

efficient to change the importance if someone else feel's 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/launchpad/+bug/163694

187

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

188

189

190

Bug Importance

228

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

229

230

It's possible to target a bug to a milestone, eg

231

<https://bugs.launchpad.net/bzr/+milestone/1.16>. We use this to help the

231

<https://bugs.edge.launchpad.net/bzr/+milestone/1.16>. We use this to help the

232

release manager know what **must** be merged to make the release.

233

234

Therefore, we don't target bugs that we'd like to have fixed or that could

255

separate work to get it into that release.

256

257

258

Release Notes

258

The News File

259

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

260

261

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

262

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

261

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

262

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

263

including the bug number.

264

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

265

267