Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <CC47D4C4.44248%aharui@adobe.com>
References: <CC47D4C4.44248%aharui@adobe.com>
Date: Wed, 8 Aug 2012 14:52:30 -0400
Message-ID: 
 <CALorpXdRE7h87d6HG6B_=yDxs7zH2f++ntGtUyzmoYU4Xvb8Hw@mail.gmail.com>
Subject: Re: [POLL] Use Unstable Branch
From: Nicholas Kwiatkowski <nicholas@spoon.as>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=00151748e0eee976d404c6c59c42

--00151748e0eee976d404c6c59c42
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

1

I love the idea of having the trunk always available to ship.  Makes the
testing and QA process a lot smoother, IMHO.

-Nick

On Wed, Aug 8, 2012 at 11:33 AM, Alex Harui <aharui@adobe.com> wrote:

> Hi Folks,
>
> I have proposed using an interim unstable branch for changes, reserving
> trunk for stuff we=92re sure we want to ship, and keeping trunk
> =93ready-to-ship=94 at all times.  Others (and other projects at Apache) =
prefer
> working directly in trunk.  I don=92t think we have the testing
> infrastructure and modularity to support that and keeping trunk
> =93ready-to-ship=94.  Maybe we=92ll get there someday.
>
> Please vote:
>
>  1.  Use unstable branch for now.
>  2.  Make all changed directly in trunk.
>
> Thanks,
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>

--00151748e0eee976d404c6c59c42--