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)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: Understanding Git
From: Justin Mclean <justin@classsoftware.com>
In-Reply-To: 
 <CAEFz_vsApLi6hLgKziKDw4qGtwOMBr=Bme0Lnde_dtGZUwsjnw@mail.gmail.com>
Date: Fri, 23 Nov 2012 07:39:10 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C00CE3A-4298-4196-9617-BDD1E491B999@classsoftware.com>
References: 
 <CAEFz_vsApLi6hLgKziKDw4qGtwOMBr=Bme0Lnde_dtGZUwsjnw@mail.gmail.com>
To: flex-dev@incubator.apache.org

Hi,

> I just wanted to make sure that everyone on this list knows that if =
they
> have any questions regarding the usage of Git and Git workflows that I
> would be more than happy to help anyone that has those questions.

Seems a of of the conversation is still around accepting pull requests, =
without github there will be no pull requests right?

The concern I have is the process around making a release. Can you =
expand on how we would:
a) Cherry pick what changes we need from the develop branch into a =
release branch?
b) Tag a release?
c) Merge the selected changes contained in a release into trunk?

Thanks,
Justin=