Difference between revisions of "HowTo:POV-Ray Feature Requests"
Jump to navigation
Jump to search
(some additional points compiled from the newsgroup) |
m (rmv line break) |
||
| Line 10: | Line 10: | ||
* If discussion of a feature request has resulted in a summary or conclusion that differs from the original request, a new feature request should not be made. Instead, the existing one should be changed. This implies contributing ideas to the feature request discussion, and then coming up with a single coherent idea, not leaving it at two half-finish ideas. | * If discussion of a feature request has resulted in a summary or conclusion that differs from the original request, a new feature request should not be made. Instead, the existing one should be changed. This implies contributing ideas to the feature request discussion, and then coming up with a single coherent idea, not leaving it at two half-finish ideas. | ||
| − | * Closely-related feature requests should be grouped together; e.g. requests for Windows UI enhancements with | + | * Closely-related feature requests should be grouped together; e.g. requests for Windows UI enhancements with respect to the editor could such as "Delete", "Reload" and "Rename" commands could reasonably be put into a single request (all at once or via editing a bug later). |
| − | respect to the editor could such as "Delete", "Reload" and "Rename" commands could reasonably be put into a single request (all at once or via editing a bug later). | ||
* There is a feature to allow other users and/or developers to comment on bugs & feature requests on bugtracker, but this is primarily intended for providing additional information, or feedback on the current status. For proper discussions, it lacks the necessary publicity. (When was the last time you just browsed the bugtracker just to see if there was some interesting discussion going on in some of the entries?) The POV-Ray community is strongest in the newsgroups. | * There is a feature to allow other users and/or developers to comment on bugs & feature requests on bugtracker, but this is primarily intended for providing additional information, or feedback on the current status. For proper discussions, it lacks the necessary publicity. (When was the last time you just browsed the bugtracker just to see if there was some interesting discussion going on in some of the entries?) The POV-Ray community is strongest in the newsgroups. | ||
Revision as of 21:01, 25 June 2010
We all want to see POV-Ray improved, and from time to time it may occur to us that there's a feature that we would like to see, or something we'd like to see improved. The legitimate place for feature requests is Bugtracker.
To see a list of current feature requests, whether open or closed, visit this link.
When making feature requests, a word of advice:
Please do read HowTo:Make A Bug Report and How to Report Bugs Effectively before submitting any entries to the bugtracker, and do heed the advice presented there. There is a reason the first is referenced at the top of each and every bugtracker page, and the second in turn is referenced in by the first: By following those rules - or at least keeping them in mind as you file bug reports - you make life a lot easier for the people you expect to fix the issues.
Some other points raised in the newsgroup:
- If discussion of a feature request has resulted in a summary or conclusion that differs from the original request, a new feature request should not be made. Instead, the existing one should be changed. This implies contributing ideas to the feature request discussion, and then coming up with a single coherent idea, not leaving it at two half-finish ideas.
- Closely-related feature requests should be grouped together; e.g. requests for Windows UI enhancements with respect to the editor could such as "Delete", "Reload" and "Rename" commands could reasonably be put into a single request (all at once or via editing a bug later).
- There is a feature to allow other users and/or developers to comment on bugs & feature requests on bugtracker, but this is primarily intended for providing additional information, or feedback on the current status. For proper discussions, it lacks the necessary publicity. (When was the last time you just browsed the bugtracker just to see if there was some interesting discussion going on in some of the entries?) The POV-Ray community is strongest in the newsgroups.