Tags:
create new tag
, view all tags

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 seven day feedback period 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)

Topic Summary Committed Developer Concern
Number of topics: 0

-- Contributors: KennethLavrsen, PeterThoeny - 2010-03-20

Discussion

 
Topic revision: r4 - 2010-03-21 - PeterThoeny
 
Twitter Delicious Facebook Digg Google Bookmarks E-mail LinkedIn Reddit StumbleUpon    
  • Download TWiki
TWiki logo Powered by Perl Hosted by OICcam.com 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.