Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of omuppi1@gmail.com designates
 209.85.217.175 as permitted sender)
MIME-Version: 1.0
Sender: omuppi1@gmail.com
In-Reply-To: <CC4FF44B.44846%aharui@adobe.com>
References: 
 <CAGgUee0O5sGH2xeibMXcjOU_nDPpeHQuZvbKNbPRNONvAKqrhw@mail.gmail.com>
 <CC4FF44B.44846%aharui@adobe.com>
From: Om <bigosmallm@gmail.com>
Date: Tue, 14 Aug 2012 12:37:56 -0700
Message-ID: 
 <CACK5iZdOtV95SaX7QY3iQHWjTRDr=T97e6-iwmHUga5OTAoDYQ@mail.gmail.com>
Subject: Re: Discuss: Branching Strategy and SCM
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=f46d04071259461fe604c73ef43f

--f46d04071259461fe604c73ef43f
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

> > Alex but couldn't we simply make "[VOTE]/[DISCUSS] - [MERGE]" mandatory
> > once we want to merge something to Develop branch?
> >
> > Jo=E3o Fernandes
> Yes, but in order to vote, I have to get your branch and build it and tes=
t
> it in order to vote.  40 committers, 40 branches at minimum.  I'd be
> interested in hearing from the mentors how they "promote" stuff from bran=
ch
> to trunk.   I was hoping it would be easier:  Instead of a vote, you just
> check it into "develop" and we veto if we don't like it.  Then fewer folk=
s
> have to go look at it.  But that means it might not be quite ready to go =
to
> production and need to be filtered out before release if we can't get it =
to
> production quality in time.
>
>
It should be up to a committer to decide when a feature should go from a
feature branch to develop.  We should be able to trust a committer's
judgement for such things.  It will be up to the release manager +
discussion on the mailing list to accept what is in develop to cut into a
release branch.

Om

--f46d04071259461fe604c73ef43f--