Mailing-List: contact clerezza-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: clerezza-dev@incubator.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAHw0Qyma-wSAEyKnhoDU9AzSQ_6MT_LgsVjEQ4jWzceZ5O51mw@mail.gmail.com>
References: 
 <CAOzb7FL1bm6JuC4w17b-uU_ZM7RxyOapk1Mvz9TqoR_j75Ffjw@mail.gmail.com>
	<CAHw0Qyma-wSAEyKnhoDU9AzSQ_6MT_LgsVjEQ4jWzceZ5O51mw@mail.gmail.com>
Date: Tue, 5 Jul 2011 08:01:41 +0000
Message-ID: 
 <CAEWfVJmFoX0drapVQkWnPPyA40h7qG7afBdUCHOzC3t8ibTGWQ@mail.gmail.com>
Subject: Re: Plan for release (was Re: Size of issues/patches)
From: Bertrand Delacretaz <bdelacretaz@apache.org>
To: clerezza-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8

On Tue, Jul 5, 2011 at 7:45 AM, Reto Bachmann-Gmuer
<reto.bachmann@trialox.org> wrote:
> ...I don't see why we should vote on code removal rather than on code
> additions. I think the trunk should be the place were the consensus-code is
> and not a sandbox from where particularly motivated people extract a release
> branch from time to time....

Some projects do it like that - either you consider the trunk as the
current stable and ready-to-release code, or you consider it as the
bleeding edge code from which releases are created by selecting the
stabler parts.

I think both ways work, the Clerezza developers team should just agree
on one or the other.

-Bertrand