Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of foamdino@gmail.com designates
 209.85.218.218 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=oDopCWL+NSB05iYw1s0GVklOO+tCQQ3NpzfUVfJRjSJvC4ikoqAUIoXkmJ2zJLf3fE
         +S5e3N4/VNizmNaj6kf8nbhdfE9S5n17o7E9OvT/8diSnXQfep3NmX6AauDysjHUv9Py
         0PIs3BCqbUHIIXA1QuWYEp6vM02PeWXdNQMzI=
MIME-Version: 1.0
In-Reply-To: <e282921e0906011542m2ed29d84pb7bb314b7433a7f8@mail.gmail.com>
References: <e282921e0906011200v5e51e6ccud582de66fe8c8988@mail.gmail.com>
	 <DD32F45D-0317-42DB-8BA7-D7244C219E8E@apache.org>
	 <e2111bbb0906011241m4f74177es6a145c6dd93a572e@mail.gmail.com>
	 <946693F3-D8F6-4D36-9A78-45047F330559@apache.org>
	 <e2111bbb0906011532k857a600u9f95846314abfca6@mail.gmail.com>
	 <e282921e0906011542m2ed29d84pb7bb314b7433a7f8@mail.gmail.com>
Date: Tue, 2 Jun 2009 10:22:48 +0100
Message-ID: <ab8e556c0906020222v1d5b4078tcf28a55cb6d4bbf0@mail.gmail.com>
Subject: Re: changing branch commit merge block procedure
From: Kevin Jackson <foamdino@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

> 0.9.1 has been sitting there ready to go for some time, we should get
> put it through the release procedure now to keep as much stability as
> possible.

With my apache hat on, my experience as a release manager is that the
release branch is taken from the trunk when the community (dev@ and
PMC) decide we want to release.

Then the release is made with the minimum of lag, at ant we follow
something along these lines:
- community decides they need a release
- release manager / scapegoat chosen ;)
- release plan decided
- committers rush to get their patches into trunk for release x
- release manager makes the release branch from trunk and the release
is effectively frozen at that point, committers free to commit to
trunk
- an alpha release is made
- community tests and reports any showstoppers (usually 2 week window)
- possible point releases are made incorporating fixes to showstoppers
(release managers call)
- beta release made (again 2 week window to report issues)
- final release made and reported on freshmeat etc, website updated

I realise that this won't be exactly the same on every project, but I
thought this may be helpful (I wish we could be this rigourous at work
;)

Kev