Reason For Decision
This field is used to identify the reason behind a decision taken by the TWiki Community in relation to new feature proposals according to the TWikiReleaseManagementProcess.| Name | Type | Tooltip Message |
|---|---|---|
| None | option | No decision taken yet |
| NoCommittedDeveloper | option | No developer is currently committed to implement or drive the feature. |
| ConsensusReached | option | Enough information and agreement exists to be able to start documenting and coding. No concern raised so no release meeting decision is needed |
| AcceptedBy7DayFeedbackPeriod | option | Proposal was either not commented, only positive comments were given, or concern raised were resolved |
| AcceptedByReleaseMeeting | option | Proposal accepted at release meeting. Please add a ref to release meeting minutes in RelatedTopics field |
| RejectedByReleaseMeeting | option | Proposal rejected at release meeting. Please add a ref to release meeting minutes in RelatedTopics field |
| RejectedByCoreVeto | option | The proposal was rejected by at least two vetos from core team members. Used very rarely |
| -----(LEGACY)----- | option | |
| AcceptedBy14DayRule | option | Legacy, do not use for new feature proposals |
- Set ALLOWTOPICCHANGE = TWikiAdminGroup
Discussion and Feedback
This topic is only editable by the TWikiAdminGroup. Please use ChangeProposal for any discussion / feedback.
Topic revision: r3 - 2011-12-11 - GeorgeTrubisky
Home 
Site map
Blog web
Create New Topic
Index
Search
Advanced search
My topics of interest
Changes
Major changes only
All tags
Notifications
RSS Feed
Statistics
Preferences
Community 
Readme first
Developers News
How you can help
Community roles
#twiki IRC
Jerusalem Release
Feature Proposals
Bugs Changes
Categories 
Account 
Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.Copyright © 1999-2012 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.