Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of Kevin.Kluge@citrix.com
 designates 66.165.176.89 as permitted sender)
From: Kevin Kluge <Kevin.Kluge@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>
Date: Thu, 24 May 2012 14:19:13 -0700
Subject: release code names (was RE: git migration heads up)
Thread-Topic: release code names (was RE: git migration heads up)
Thread-Index: Ac058qCcQKlGh4jfQkKky/Y+d70SSg==
Message-ID: 
 <61AE1E2837A06D4A8E98B796183842D40116B90AED74@SJCPMAILBOX01.citrite.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Also, I think we should take the pre-existing release codenames (Bonita, Bu=
rbank, and Campo) and reserve them for Citrix commercial releases.   The co=
mmunity is moving to a different release cycle (with presumably different r=
elease content) than Citrix had planned, and of course it can come up with =
new codenames if desired.   This clear assignment will help reduce confusio=
n as we split Citrix and Apache release cycles.  It will require further sc=
rubbing in the bug db and on the wiki as these codenames are referenced the=
re.

-kevin

> -----Original Message-----
> From: David Nalley [mailto:david@gnsa.us]
> Sent: Thursday, May 24, 2012 2:02 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: git migration heads up
>=20
> On Thu, May 24, 2012 at 4:54 PM, Alena Prokharchyk
> <Alena.Prokharchyk@citrix.com> wrote:
> > On 5/24/12 7:17 AM, "David Nalley" <david@gnsa.us> wrote:
> >
> >>Just an FYI:
> >>
> >>Mohammad and I are going to freeze github/git.cloud.com's 3.0.x and
> >>master branches this weekend while we attempt to migrate them to the
> >>ASF repo. The ASF repo will remain frozen until we can conclude a vote
> >>(I understand that the PPMC must certify/accept the code drop), after
> >>which the ASF repo should become the canonical repo for the project.
> >>
> >
> >
> >
> > I have a question about the branch I'm currently working on -
> > vpc-3.0.x (checkins for Burbank VAps feature go there). This branch is
> > supposed to be merged to 3.0.x/master in about 2 weeks.
> >
> > Should we merge vpc-3.0.x to apache repo as well at this point?
> >
> > Thanks,
> > -Alena.
> >
>=20
> Hi Alena:
>=20
> It shouldn't be a problem to merge at a later point (and I am specificall=
y trying
> to keep the number of branches we initially bring over down just for
> complexity's sake.)
>=20
> When it's ready to merge you should still be able to do so. No need to ru=
sh
> things on your end.
>=20
> you'll add a new remote to your existing local git config - we'll say you=
 run
> something like 'git remote add asf https://git-wip-
> us.apache.org/repos/asf?p=3Dincubator-cloudstack.git'
>=20
> Then you should be able to trivially merge stuff from existing branches t=
o the
> ASF hosted repo (and create new branches there as
> well)
>=20
> --David