Opened 18 years ago
Closed 18 years ago
#4942 closed (fixed)
Addition to the bug reporting guidelines
| Reported by: | Owned by: | Jacob | |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | bug guideline | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
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 (1)
Change History (5)
by , 18 years ago
| Attachment: | contributing.txt.diff added |
|---|
comment:1 by , 18 years ago
| Triage Stage: | Unreviewed → Design decision needed |
|---|
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?
comment:2 by , 18 years ago
It's almost verbatim what was said in this post, and seems to reflect the current orientation of most developers.
comment:3 by , 18 years ago
| Triage Stage: | Design decision needed → Ready for checkin |
|---|
comment:4 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Patch mentioned in description