Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of dave2wave@comcast.net
 designates 76.96.27.211 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: [DISCUSS] Re: [VOTE] Branching Strategy and SCM
From: Dave Fisher <dave2wave@comcast.net>
In-Reply-To: 
 <CAEFz_vtSiKFfw0TaUVQWvB7+ksU6LbGCVvwiaEjPPS_g-x2KCA@mail.gmail.com>
Date: Mon, 13 Aug 2012 14:38:29 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7225CD7-58A3-4CE0-95FB-5877100839CC@comcast.net>
References: <CC4EAF57.446B9%aharui@adobe.com>
 <391032D7-4A8C-40B6-875A-E921DD627125@comcast.net>
 <CAEFz_vtSiKFfw0TaUVQWvB7+ksU6LbGCVvwiaEjPPS_g-x2KCA@mail.gmail.com>
To: flex-dev@incubator.apache.org


On Aug 13, 2012, at 1:43 PM, Omar Gonzalez wrote:

> On Mon, Aug 13, 2012 at 1:39 PM, Dave Fisher <dave2wave@comcast.net> =
wrote:
>=20
>> My opinion/vote is (4) - no guts, no glory - work in trunk and learn =
to
>> co-operate.
>>=20
>> The vote is more about the Classic model than it is about Git  vs. =
SVN.
>>=20
>> To me svn tag =3D=3D git branch.
>>=20
>> Regards,
>> Dave
>=20
>=20
> People that use Git a lot would strongly disagree with "svn tag =3D=3D =
git
> branch". For starters, SVN tags are supposed to not ever be edited, =
and Git
> branches are used for almost all new code addition/changes in the =
"nvie"
> model, so they're from from =3D=3D.

I'm more thinking this from what happens in the central repository and =
what gets marked up in the history from a few comparisons I've done.

When you branch in git you are marking where you are in the main repos, =
correct? If you never push it back the central repos never really cares =
about your branch, correct? So to the repository a branch is like a tag.

My opinion is that git is just putting off the work of integrating =
diverse changes into a single release. I feel the same about the 3-Tier =
plan. It is just putting ALL the work of deciding what is in a release =
to a Release Manager.

Really the Apache Way is for the Committers and the PPMC to share this =
responsibility. As this podling must know, you never, ever know when =
someone will exit.

But go ahead and go the way you want, it is up to you all.

Really what is the worst that can happen if someone plays in trunk and =
makes a mistake?

Regards,
Dave

>=20
> -omar