httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Fritsch ...@sfritsch.de>
Subject Re: [RFC] try to solidify feature adoption criteria
Date Fri, 02 Mar 2012 19:41:17 GMT
On Thursday 01 March 2012, Jeff Trawick wrote:
> On Wed, Feb 29, 2012 at 12:57 PM, Jeff Trawick <trawick@gmail.com> 
wrote:
> > New features are a natural part of the software life-cycle, but
> > they
> 
> One obvious alternative is to simply document that new features of
> any magnitude can be added to trunk at will by any committer. 
> Presence in a stable branch is subject to a level of documentation
> considered acceptable to other committers.  Merging new features
> to an existing stable branch is subject to commit rules for that
> branch.

I would prefer rules that distinguish between adding a feature to 
trunk and including a feature in a stable release.

Like:

Committers may introduce new modules in trunk.

Anyone can call for a vote to have the module removed, requiring a 
passed vote (i.e. three +1s) for removal.

When a release comes near, anyone who doesn't think the module is 
release quality may call a vote. The module needs a passed vote for 
inclusion in the release.

This way a module may mature in trunk. But if it doesn't due to lack 
of interest, it would still need people to actively support it in 
order for it to be released.

> --/--
> 
> Or just drop the documentation requirement.
> 
> --/--
> 
> Not writing down any group think on this invites future conflict.

Mime
View raw message