1 (non binding) On Wed, Aug 8, 2012 at 5:40 PM, Kéven Boily <kbo...@tribalnova.com> wrote:
> The way I see it branches should be used by a dedicated dev (or group) for > one new feature/bugfix that's still in developpement or not completely > implemented (incomplete). When they are done they are merged into the > (unstable, untested) trunk. Any released version outside the trunk (not > necessarely stable, can be beta) should be tagged. > * > Kéven Boily* > Développeur > *tribalnova* > 4398, boul. Saint-Laurent, bureau 310 > Montréal, Québec H2W 1Z5 > kbo...@tribalnova.com > www.tribalnova.com > > > > On Wed, Aug 8, 2012 at 11:33 AM, Alex Harui <aha...@adobe.com> wrote: > > > Hi Folks, > > > > I have proposed using an interim unstable branch for changes, reserving > > trunk for stuff we’re sure we want to ship, and keeping trunk > > “ready-to-ship” at all times. Others (and other projects at Apache) > prefer > > working directly in trunk. I don’t think we have the testing > > infrastructure and modularity to support that and keeping trunk > > “ready-to-ship”. Maybe we’ll 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 > > >
