Opened 13 years ago
Last modified 13 years ago
#85 closed task
Methodology for handling bugs — at Initial Version
| Reported by: | Elrond | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | infrastructure | Keywords: | |
| Cc: | Parent Tickets: |
Description
Background¶ =========== There are currently a few bugs, that sit at "New", don't have a single comment and are just there. For now this is fine. People know from irc, that their bug will be handled sometime. When the project grows, this sort of bug handling isn't good. It leaves a feeling of "they don't listen, they don't care" to the users. Brainstorming ideas¶ ==================== Maybe some new bug status thingies could be helpful? - "Accepted - Your bug is valid" - "Okay, this is true, we should consider that" - "Yes, we'll fix that, but just not now" Another brainstormy thing: Maybe allow users/developers to care more for bugs. This works nicely in Debian, where everybody can nearly change any bug. Warning notice¶ =============== On the other hand, things should not be overorganized. Other ideas¶ ============ - Have a feed of "New" bugs
Note:
See TracTickets
for help on using tickets.
