Difference between revisions of "Bugzilla"
(even more politely) |
(→Stock messages: For explaining why we ask questions even though the original report might be very old) |
||
| Line 33: | Line 33: | ||
Feel free to file other bugs or enhancement requests that you find, though. | Feel free to file other bugs or enhancement requests that you find, though. | ||
| + | |||
| + | === For explaining why we ask questions even though the original report might be very old === | ||
| + | Thanks a lot for your feedback. You are right, it was not nice from gnucash to not reply to your initial report for quite some time. We are very sorry for that. However, at the sporadic occasions when some of us check *all* currently open bugreports (even though this part of gnucash used to be in someone else's responsibility) we only have the choice to either continue not to reply, or add a reply even though the original report is already several months old (or years). In your case, we have decided it is better to reply late than not to reply at all. Thank you very much for bearing the imponderables of a large volunteer project such as ours. | ||
Revision as of 09:02, 16 February 2011
Bugzilla is a repository of bugs and enhancement requests maintained by the Gnome Project and used by the GnuCash project. There is a specific GnuCash "product" subsection which allows you to specifically search for GnuCash bugs. You can use the following quick links to perform actions on the GnuCash Bugs Database:
Strongly recommended:
Other links into bugzilla:
- Search the entire GNOME bug database
- Search for open GnuCash bugs and enhancements
- Search for open GnuCash bugs and enhancements, restricted to post-1.8 or unspecified versions
- You might probably read the FAQ section about bug reporting before you continue ...
- Open a new GnuCash bug or enhancement Request; when reporting a crash, see Stack Trace and Tracefile for information on how to produce a stack trace for your bug report.
For people, which like to help us e.g. on bug triage, are some additional informations in QA/BugzillaAdministration.
Contents
Stock messages
Feel free to copy this messages into the comment when closing bugs for certain reasons that occur regularly.
When closing an old bug as OBSOLETE
Thank you for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. The GnuCash developers are no longer working on that version, so either this bug has already been fixed or unfortunately there will not be any bug fixes for the version that you use. The current stable version of gnucash is 2.4.0 now.
In the (hopefully unlikely) case you discover the same bug in the very latest stable version, do not hesitate to REOPEN it again. Also, feel free to file other bugs or enhancement requests that you find. Thank you very much!
When refusing an enhancement request as WONTFIX or priority=low
Thank you for taking the time to explain your enhancement request.
The described enhancement is a good proposal and would be an advantage for the software. However, as a volunteer-driven project with limited resources, the GnuCash developers have their own priorities about the features which are most likely being worked on in the near future. In that sense, the current GnuCash developers decided not to work on your proposed feature in the next 4-6 months. In case you would like to have this feature implemented in any case, you have the following option: 1. Start to program in gnucash yourself - see http://wiki.gnucash.org/wiki/Development . 2. Convince someone who is not yet part of the GnuCash team to join the team and implement your feature. 3. Pay some of the GnuCash developers to implement your feature - ask on the mailing list gnucash-devel@gnucash.org in that case. Thank you very much.
Feel free to file other bugs or enhancement requests that you find, though.
For explaining why we ask questions even though the original report might be very old
Thanks a lot for your feedback. You are right, it was not nice from gnucash to not reply to your initial report for quite some time. We are very sorry for that. However, at the sporadic occasions when some of us check *all* currently open bugreports (even though this part of gnucash used to be in someone else's responsibility) we only have the choice to either continue not to reply, or add a reply even though the original report is already several months old (or years). In your case, we have decided it is better to reply late than not to reply at all. Thank you very much for bearing the imponderables of a large volunteer project such as ours.
