Django

Code

Ticket #4942 (closed: fixed)

Opened 1 year ago

Last modified 1 year ago

Addition to the bug reporting guidelines

Reported by: Nicola Larosa <nico@teknico.net> Assigned to: jacob
Milestone: Component: Documentation
Version: SVN Keywords: bug guideline
Cc: Triage Stage: Ready for checkin
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

Patch adding the following text to docs/contributing.txt: 

    * **Don't** post to `django-developers`_ to announce that you have logged a
      bug. The core developers and ticket triage team keep a handle on the new
      tickets as they are submitted.

      You only need to start a django-developers discussion if there is some
      sort of design issue to resolve (for example, if you want to fix the bug,
      and want advice on the correct solution to a problem).

Attachments

contributing.txt.diff (0.8 kB) - added by Nicola Larosa <nico@teknico.net> on 07/21/07 03:20:39.
Patch mentioned in description

Change History

07/21/07 03:20:39 changed by Nicola Larosa <nico@teknico.net>

  • attachment contributing.txt.diff added.

Patch mentioned in description

07/21/07 05:13:28 changed by Simon G. <dev@simon.net.nz>

  • needs_better_patch changed.
  • stage changed from Unreviewed to Design decision needed.
  • needs_tests changed.
  • needs_docs changed.

Hmm... a little bit blunt :) Are we really getting that much traffic in django-dev along these lines? and do we really want to scare off contributors?

08/06/07 09:10:34 changed by Nicola Larosa <nico@teknico.net>

It's almost verbatim what was said in this post, and seems to reflect the current orientation of most developers.

08/10/07 01:41:23 changed by Simon G. <dev@simon.net.nz>

  • stage changed from Design decision needed to Ready for checkin.

08/12/07 05:47:11 changed by mtredinnick

  • status changed from new to closed.
  • resolution set to fixed.

(In [5872]) Fixed #4942 -- Added an explanation that we see tickets as they are filed, automatically. Based on a suggestion from Nicola Larosa.

Add/Change #4942 (Addition to the bug reporting guidelines)




Change Properties
Action