release code names (was RE: git migration heads up)

[Kevin Kluge <Ke...@citrix.com>]

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

-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
> 
> On Thu, May 24, 2012 at 4:54 PM, Alena Prokharchyk
> <Al...@citrix.com> wrote:
> > On 5/24/12 7:17 AM, "David Nalley" <da...@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.
> >
> 
> Hi Alena:
> 
> It shouldn't be a problem to merge at a later point (and I am specifically trying
> to keep the number of branches we initially bring over down just for
> complexity's sake.)
> 
> When it's ready to merge you should still be able to do so. No need to rush
> things on your end.
> 
> 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=incubator-cloudstack.git'
> 
> Then you should be able to trivially merge stuff from existing branches to the
> ASF hosted repo (and create new branches there as
> well)
> 
> --David

Re: release code names (was RE: git migration heads up)

[David Nalley <da...@gnsa.us>]

On Thu, May 24, 2012 at 5:19 PM, Kevin Kluge <Ke...@citrix.com> wrote:
> Also, I think we should take the pre-existing release codenames (Bonita, Burbank, and Campo) and reserve them for Citrix commercial releases.   The community is moving to a different release cycle (with presumably different release content) than Citrix had planned, and of course it can come up with new codenames if desired.   This clear assignment will help reduce confusion as we split Citrix and Apache release cycles.  It will require further scrubbing in the bug db and on the wiki as these codenames are referenced there.
>
> -kevin
>

Agreed - there already seems to be consensus (though it's still early
in the conversation) on us breaking the existing versioning scheme and
moving to 4.0.0 as the initial release. We can work on cleanup of all
of those references as we go forward - though I don't necessarily see
it as a blocker to release - and want to really focus on that as our
next 'big goal'.

--David