Feature Proposals Ready For Release Meeting

A Feature proposal is ready for release meeting per release process when

• Proposals that have a committed developer willing to drive the proposal to implementation. There is no requirement how soon and a developer is later allowed to uncommit if it later turns out that he does not have the time.
• Proposals have had at least one concern raised by any person with a twiki.org access
• The community has had enough time to end the discussion, but could not reach full consensus
• It is normally a Customer Advocate that decides that a feature is ready for a release meeting.

Note that the 14-days rule clock stop ticking when anyone that are registered as a user on twiki.org raises any concern and it does not ever start again! Then acceptance is either by consensus or by release meeting decision.

This topic is now cached (refresh)

-- Contributors: KennethLavrsen - 24 Apr 2007

Discussion