ChangeProposals that need a rethink

These ChangeProposals (FeatureRequests, BugReports, DocRequests & CodeRefactors) are not suitable for Core without more work/lobbying. This state might be arrived at if the implementation is flawed, or the description of the proposal is inadequate, or in some other explained way the change just doesn't "make the grade" for inclusion in the next release.

Under the new ChangeProposal workflow, if a bug is rejected because it is not deemed a bug (i.e. "It's a feature") it can have it's TopicClassification changed to FeatureRequest and be refactored into a proposal for a new feature/fuctionality. If you do this please either copy the content of FeatureRequestTopicTemplate or alternatively use the form on FeatureRequest with a fictitious topic name submitting the form and then instead of saving the topic, copy the content and paste it into the old topic and refactor the original content under the new headings.

Similarly if the bug report or feature request was submitted because of a misunderstanding due to insufficient documentation it could be changed to a DocRequest (Again use the form on the topic or copy the DocRequestTopicTemplate).

Related Topcis

• FeatureNotSuitable: for a list of features, including old WebForm feature request
• BugRejected: for a list of reports de-classified as bugs, including old WebForm bug reports