8 Aug 11:50
Feature request administration
From: Frank Niessink <frank@...>
Subject: Feature request administration
Newsgroups: gmane.comp.sysutils.pim.taskcoach.devel
Date: 2008-08-08 09:53:50 GMT
Subject: Feature request administration
Newsgroups: gmane.comp.sysutils.pim.taskcoach.devel
Date: 2008-08-08 09:53:50 GMT
Hi, I've updated the canned messages for feature requests on Sourceforge. It is a bit weird if Jerome sets a feature request to pending with a message signed by 'Frank'I took the opportunity to reorganize the feature administration a bit: - Priority 1 is used for features that are implemented: set a feature request to priority 1 when you commit the feature and use the 'feature implemented' canned message to notify the submitter - New features get a default priority of 2: when a new feature is requested use the 'thanks for submitting a feature request' canned message and set the priority to 2. - Priority 3 is used for features with multiple requesters; when other people than the original submitter voice their support for the feature, the priority is increased to 3, no canned message needed. - Priority 4 is used for features where a donation is offered. - Priotity 5 and higher are reserved for future use
When a new version of TC is released, all related feature requests get the 'feature available' canned message and the request status is set to 'pending'. The tracker robot will automatically close the feature request if the submitter does not comment within two weeks. Cheers, Frank ------------------------------------ Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/taskcoach-dev/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/taskcoach-dev/join (Yahoo! ID required) <*> To change settings via email: mailto:taskcoach-dev-digest@... mailto:taskcoach-dev-fullfeatured@... <*> To unsubscribe from this group, send an email to: taskcoach-dev-unsubscribe@... <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
I took the opportunity to reorganize the feature administration a bit:
- Priority 1 is used for features that are implemented: set a feature
request to priority 1 when you commit the feature and use the 'feature
implemented' canned message to notify the submitter
- New features get a default priority of 2: when a new feature is
requested use the 'thanks for submitting a feature request' canned
message and set the priority to 2.
- Priority 3 is used for features with multiple requesters; when other
people than the original submitter voice their support for the
feature, the priority is increased to 3, no canned message needed.
- Priority 4 is used for features where a donation is offered.
- Priotity 5 and higher are reserved for future use
RSS Feed