You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafodion.apache.org by "Varnau, Steve (Trafodion)" <st...@hp.com> on 2015/05/27 21:09:52 UTC
Migrating code to Apache git -- multiple repos
Mentors,
I'm looking for some guidance on source code set-up.
We currently use several git repos for trafodion (https://github.com/trafodion):
trafodion/core - bulk of product code, tests, etc
trafodion/dcs - product and test code for connectivity services
trafodion/install - installation scripts
trafodion/phoenix_test - test suite adapted from apache/phoenix customized to trafodion
Our initial incubation repo set up is at: https://git-wip-us.apache.org/repos/asf/incubator-trafodion.git
Assuming the trafodion/core history will go into incubator-trafodion, do we also need additional repos?
Perhaps:
incubator-trafodion-dcs
incubator-trafodion-install
incubator-trafodion-test
-Steve
Re: Migrating code to Apache git -- multiple repos
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Fri, Jun 19, 2015 at 1:04 PM, Stack <st...@duboce.net> wrote:
> On Fri, Jun 19, 2015 at 12:51 PM, Chen, Alice (Trafodion) <alice.chen@hp.com
>> Also do we need to do anything to document that the code has been pushed
>> from GitHub to the ASF Git repository?
>>
>>
> Not that I know of (Roman?)
Makes two of us.
Thanks,
Roman.
Re: Migrating code to Apache git -- multiple repos
Posted by Stack <st...@duboce.net>.
On Fri, Jun 19, 2015 at 12:51 PM, Chen, Alice (Trafodion) <alice.chen@hp.com
> wrote:
> Hello,
>
> With Steve's help I've pushed our code to the ASF Git repository.
Hurray!
> We would like GitHub hooks to be set up and Steve has file
> https://issues.apache.org/jira/browse/INFRA-9852 for this. Since it
> looks like GitHub will be sending lots of emails we thought it would be
> better to have all those messages mirrored to another mailing list
> codereview@trafodion.incubator.org . Could someone please request this
> mailing list for us?
>
>
I tried. Seems to be an issue. Added notes to INFRA-9852.
> Also do we need to do anything to document that the code has been pushed
> from GitHub to the ASF Git repository?
>
>
Not that I know of (Roman?)
> I've also updated https://issues.apache.org/jira/browse/INFRA-9701 with
> instructions on how to import our LaunchPad Bugs/Blueprints.
>
>
Sweet.
St.Ack
> Cheers,
> Alice
>
>
>
> -----Original Message-----
> From: Varnau, Steve (Trafodion)
> Sent: Friday, June 19, 2015 10:07 AM
> To: dev@trafodion.incubator.apache.org
> Subject: RE: Migrating code to Apache git -- multiple repos
>
> I'm too late to be the Apache Steve. But I will work with Alice to start
> the gears turning on code, jira, etc.
>
> -Steve
>
> > -----Original Message-----
> > From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of
> > Stack
> > Sent: Friday, June 19, 2015 09:56
> > To: dev@trafodion.incubator.apache.org
> > Subject: Re: Migrating code to Apache git -- multiple repos
> >
> > Ahem. Thanks for the comma Dave.
> > St.Ack
> >
> > On Fri, Jun 19, 2015 at 8:47 AM, Birdsall, Dave <da...@hp.com>
> > wrote:
> >
> > > I think he meant, "Apache, Steve?" (interesting how a missing comma
> > > can change the meaning)
> > >
> > > -----Original Message-----
> > > From: Pierre Smits [mailto:pierre.smits@gmail.com]
> > > Sent: Friday, June 19, 2015 8:43 AM
> > > To: dev@trafodion.incubator.apache.org
> > > Subject: Re: Migrating code to Apache git -- multiple repos
> > >
> > > For sure not to Apache STeVe, as that is a totally different project.
> > >
> > > Best regards,
> > >
> > > Pierre
> > >
> > > Op vrijdag 19 juni 2015 heeft Stack <st...@duboce.net> het volgende
> > > geschreven:
> > >
> > > > 1. and 2. below have been done by Dave (see
> > > > http://www.apache.org/licenses/exports/).
> > > >
> > > > The VOTE on accepting the HP grant passed.
> > > >
> > > > Time to push from https://github.com/svarnau/traf-merged to Apache
> > > Steve?
> > > >
> > > > St.Ack
> > > >
> > > >
> > > > On Wed, Jun 10, 2015 at 2:53 PM, Deyager, Kevin
> > > > <kevin.deyager@hp.com <javascript:;>>
> > > > wrote:
> > > >
> > > > > Hi Stack,
> > > > >
> > > > > I am finalizing the SGA with an HP attorney. I am still hopeful
> > > > > we can get this executed and submitted by the end of the week to
> > > > > secretary@apache.org <javascript:;>.
> > > > >
> > > > > After that, before we can submit code, we need to deal with
> > > > > cryptography
> > > > > by:
> > > > >
> > > > > (1) updating the Exports page here (
> > > > > http://www.apache.org/licenses/exports/) as follows:
> > > > >
> > > > > Product Name: Apache Trafodion
> > > > > Versions: Development
> > > > > ECCN: 5D002
> > > > > Controlled Source:
> > > > > ASF (git://git.apache.org/incubator-trafodion.git) -- Designed
> > > > > for use with encryption library Oracle (
> > > > http://www.oracle.com/technetwork/java/javase/downloads/index.html
> > > > )
> > > > > -- Designed for use with Java Cryptography Extensions (JCE) The
> > > > > OpenSLL Project (http://www.openssl.org/source/) -- Publically
> > > > > available SSL encryption library
> > > > >
> > > > > And then:
> > > > >
> > > > > (2) sending the email to notify the US government.
> > > > >
> > > > > I assume Dave Birdsall can edit the file on the Apache site and
> > > > > send the email, being a committer and part of the Trafodion PMC,
> > > > > if I am reading this correctly.
> > > > >
> > > > > The next activity is we open a JIRA and submit.
> > > > >
> > > > > We'd really like to get that code over early next week, if
> > possible.
> > > > > Is there any other steps or gotchas?
> > > > >
> > > > > Regards,
> > > > > -- Kevin
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: saint.ack@gmail.com <javascript:;>
> > > > > [mailto:saint.ack@gmail.com
> > > > <javascript:;>] On Behalf Of Stack
> > > > > Sent: Wednesday, June 10, 2015 9:53 AM
> > > > > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > > Subject: Re: Migrating code to Apache git -- multiple repos
> > > > >
> > > > > Thanks Kevin
> > > > >
> > > > > Any updates?
> > > > >
> > > > > Am I right in thinking this the (only?) barrier to our being
> > > > > able to move over the code to apache?
> > > > >
> > > > > Thanks,
> > > > > St.Ack
> > > > >
> > > > > On Fri, May 29, 2015 at 8:55 PM, Deyager, Kevin
> > > > > <kevin.deyager@hp.com
> > > > <javascript:;>>
> > > > > wrote:
> > > > >
> > > > > > Hi Michael,
> > > > > >
> > > > > > I am working the SGA. And yes, things can work a bit slowly
> > > > > > in big companies...
> > > > > >
> > > > > > Kevim
> > > > > >
> > > > > > On May 29, 2015 7:51 PM, Stack <stack@duboce.net
> > > > > > <javascript:;>>
> > > > wrote:
> > > > > > HPers!
> > > > > >
> > > > > > You'll have to live w/ Steve's reorg going forward. You good
> > > > > > w/ the
> > > > > 'mess'
> > > > > > he's made (smile)?
> > > > > >
> > > > > > Before I try build myself, where are the build instructions?
> > > > > >
> > > > > > On the software grant, who is on that? This often takes way
> > > > > > more time than folks would expect.
> > > > > >
> > > > > > Thanks,
> > > > > > St.Ack
> > > > > >
> > > > > >
> > > > > > On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik
> > > > > > <roman@shaposhnik.org <javascript:;>>
> > > > > > wrote:
> > > > > >
> > > > > > > Great progress! I'll definitely take a look Mon/Tue next week!
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Roman.
> > > > > > >
> > > > > > > On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> > > > > > > <steve.varnau@hp.com <javascript:;>> wrote:
> > > > > > > > I have pushed more changes to my traf-merged repo.
> > > > > > > >
> > > > > > > > * renamed "test" directory to "tests/phx"
> > > > > > > > * added "wms" component (master branch only, as it has not
> > > > > > > > been
> > > > > > released)
> > > > > > > > * added 1.x.x_<component> release tags for applicable
> > > > > > > > components
> > > > > > > >
> > > > > > > > I did not bother with the 0.x.x release tags.
> > > > > > > >
> > > > > > > > Feedback, please.
> > > > > > > >
> > > > > > > > -Steve
> > > > > > > >
> > > > > > > >> -----Original Message-----
> > > > > > > >> From: Varnau, Steve (Trafodion)
> > > > > > > >> Sent: Thursday, May 28, 2015 15:42
> > > > > > > >> To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > > > > >> Subject: RE: Migrating code to Apache git -- multiple
> > > > > > > >> repos
> > > > > > > >>
> > > > > > > >> I have a combined repo on github for folks to take a look
> > at.
> > > > > > > >>
> > > > > > > >> https://github.com/svarnau/traf-merged
> > > > > > > >>
> > > > > > > >> The full history of all the repos is there for the three
> > > > > > > >> release
> > > > > > > >> branches: master, stable/1.0, stable/1.1
> > > > > > > >>
> > > > > > > >> I restructured the various repos into sub-directories for
> > > > > > > >> each of the three branches. Install has only a master
> > > > > > > >> branch, so it does not exist in the stable branches.
> > > > > > > >>
> > > > > > > >> Next I need to put in some key tags. Since the same
> > > > > > > >> release tag names were used across repos, combining the
> > > > > > > >> repos caused tags to
> > > > > conflict.
> > > > > > > >> I'll have to re-name them by repo.
> > > > > > > >>
> > > > > > > >> -Steve
> > > > > > > >>
> > > > > > > >> > -----Original Message-----
> > > > > > > >> > From: Varnau, Steve (Trafodion)
> > > > > > > >> > Sent: Wednesday, May 27, 2015 16:52
> > > > > > > >> > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > > > > >> > Subject: RE: Migrating code to Apache git -- multiple
> > > > > > > >> > repos
> > > > > > > >> >
> > > > > > > >> > Thanks, guys. You've answered my questions. I'll work
> > > > > > > >> > up a combined repo structure that we can review.
> > > > > > > >> >
> > > > > > > >> > -Steve
> > > > > > > >> >
> > > > > > > >> > > -----Original Message-----
> > > > > > > >> > > From: shaposhnik@gmail.com <javascript:;> [mailto:
> > > > shaposhnik@gmail.com <javascript:;>] On
> > > > > > Behalf
> > > > > > > >> > > Of Roman Shaposhnik
> > > > > > > >> > > Sent: Wednesday, May 27, 2015 15:54
> > > > > > > >> > > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > > > > >> > > Subject: Re: Migrating code to Apache git -- multiple
> > > > > > > >> > > repos
> > > > > > > >> > >
> > > > > > > >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve
> > > > > > > >> > > (Trafodion) <steve.varnau@hp.com <javascript:;>> wrote:
> > > > > > > >> > > > Sorry, I guess we can merge repos while retaining
> > history.
> > > > > > > >> > > > I
> > > > > > just
> > > > > > > >> > > > had
> > > > > > > >> > > not done so before.
> > > > > > > >> > >
> > > > > > > >> > > I can help with that -- I've done it before.
> > > > > > > >> > >
> > > > > > > >> > > > Is that the preferred route?
> > > > > > > >> > >
> > > > > > > >> > > Yes.
> > > > > > > >> > >
> > > > > > > >> > > > The mechanics for migrating the trafodion code is
> > > > > > > >> > > > for a
> > > > > > committer
> > > > > > > >> > > > to push the current code into the newly created repo?
> > > > > > > >> > > > (When we are ready to pull that switch.)
> > > > > > > >> > >
> > > > > > > >> > > I'd suggest NOT involving INFRA in the mechanics of
> > > > > > > >> > > repo
> > > > > > migration.
> > > > > > > >> > > At this point it is not simple enough and that will
> > > > > > > >> > > be kind of
> > > > > > tough
> > > > > > > >> > > to communicate to ASF INFRA.
> > > > > > > >> > >
> > > > > > > >> > > What I suggest is this: create a brand new staging
> > > > > > > >> > > repo on
> > > GH.
> > > > > > Merge
> > > > > > > >> > > all the code there. Review the result. And once it
> > > > > > > >> > > looks good do everybody just do a git push to ASF repo.
> > > > > > > >> > >
> > > > > > > >> > > Sounds reasonable?
> > > > > > > >> > >
> > > > > > > >> > > Thanks,
> > > > > > > >> > > Roman.
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Pierre Smits
> > >
> > > *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud-
> > > Based Manufacturing, Professional Services and Retail & Trade
> > > http://www.orrtiz.com
> > >
>
RE: Migrating code to Apache git -- multiple repos
Posted by "Chen, Alice (Trafodion)" <al...@hp.com>.
Hello,
With Steve's help I've pushed our code to the ASF Git repository. We would like GitHub hooks to be set up and Steve has file https://issues.apache.org/jira/browse/INFRA-9852 for this. Since it looks like GitHub will be sending lots of emails we thought it would be better to have all those messages mirrored to another mailing list codereview@trafodion.incubator.org . Could someone please request this mailing list for us?
Also do we need to do anything to document that the code has been pushed from GitHub to the ASF Git repository?
I've also updated https://issues.apache.org/jira/browse/INFRA-9701 with instructions on how to import our LaunchPad Bugs/Blueprints.
Cheers,
Alice
-----Original Message-----
From: Varnau, Steve (Trafodion)
Sent: Friday, June 19, 2015 10:07 AM
To: dev@trafodion.incubator.apache.org
Subject: RE: Migrating code to Apache git -- multiple repos
I'm too late to be the Apache Steve. But I will work with Alice to start the gears turning on code, jira, etc.
-Steve
> -----Original Message-----
> From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of
> Stack
> Sent: Friday, June 19, 2015 09:56
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Migrating code to Apache git -- multiple repos
>
> Ahem. Thanks for the comma Dave.
> St.Ack
>
> On Fri, Jun 19, 2015 at 8:47 AM, Birdsall, Dave <da...@hp.com>
> wrote:
>
> > I think he meant, "Apache, Steve?" (interesting how a missing comma
> > can change the meaning)
> >
> > -----Original Message-----
> > From: Pierre Smits [mailto:pierre.smits@gmail.com]
> > Sent: Friday, June 19, 2015 8:43 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: Re: Migrating code to Apache git -- multiple repos
> >
> > For sure not to Apache STeVe, as that is a totally different project.
> >
> > Best regards,
> >
> > Pierre
> >
> > Op vrijdag 19 juni 2015 heeft Stack <st...@duboce.net> het volgende
> > geschreven:
> >
> > > 1. and 2. below have been done by Dave (see
> > > http://www.apache.org/licenses/exports/).
> > >
> > > The VOTE on accepting the HP grant passed.
> > >
> > > Time to push from https://github.com/svarnau/traf-merged to Apache
> > Steve?
> > >
> > > St.Ack
> > >
> > >
> > > On Wed, Jun 10, 2015 at 2:53 PM, Deyager, Kevin
> > > <kevin.deyager@hp.com <javascript:;>>
> > > wrote:
> > >
> > > > Hi Stack,
> > > >
> > > > I am finalizing the SGA with an HP attorney. I am still hopeful
> > > > we can get this executed and submitted by the end of the week to
> > > > secretary@apache.org <javascript:;>.
> > > >
> > > > After that, before we can submit code, we need to deal with
> > > > cryptography
> > > > by:
> > > >
> > > > (1) updating the Exports page here (
> > > > http://www.apache.org/licenses/exports/) as follows:
> > > >
> > > > Product Name: Apache Trafodion
> > > > Versions: Development
> > > > ECCN: 5D002
> > > > Controlled Source:
> > > > ASF (git://git.apache.org/incubator-trafodion.git) -- Designed
> > > > for use with encryption library Oracle (
> > > http://www.oracle.com/technetwork/java/javase/downloads/index.html
> > > )
> > > > -- Designed for use with Java Cryptography Extensions (JCE) The
> > > > OpenSLL Project (http://www.openssl.org/source/) -- Publically
> > > > available SSL encryption library
> > > >
> > > > And then:
> > > >
> > > > (2) sending the email to notify the US government.
> > > >
> > > > I assume Dave Birdsall can edit the file on the Apache site and
> > > > send the email, being a committer and part of the Trafodion PMC,
> > > > if I am reading this correctly.
> > > >
> > > > The next activity is we open a JIRA and submit.
> > > >
> > > > We'd really like to get that code over early next week, if
> possible.
> > > > Is there any other steps or gotchas?
> > > >
> > > > Regards,
> > > > -- Kevin
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: saint.ack@gmail.com <javascript:;>
> > > > [mailto:saint.ack@gmail.com
> > > <javascript:;>] On Behalf Of Stack
> > > > Sent: Wednesday, June 10, 2015 9:53 AM
> > > > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > Subject: Re: Migrating code to Apache git -- multiple repos
> > > >
> > > > Thanks Kevin
> > > >
> > > > Any updates?
> > > >
> > > > Am I right in thinking this the (only?) barrier to our being
> > > > able to move over the code to apache?
> > > >
> > > > Thanks,
> > > > St.Ack
> > > >
> > > > On Fri, May 29, 2015 at 8:55 PM, Deyager, Kevin
> > > > <kevin.deyager@hp.com
> > > <javascript:;>>
> > > > wrote:
> > > >
> > > > > Hi Michael,
> > > > >
> > > > > I am working the SGA. And yes, things can work a bit slowly
> > > > > in big companies...
> > > > >
> > > > > Kevim
> > > > >
> > > > > On May 29, 2015 7:51 PM, Stack <stack@duboce.net
> > > > > <javascript:;>>
> > > wrote:
> > > > > HPers!
> > > > >
> > > > > You'll have to live w/ Steve's reorg going forward. You good
> > > > > w/ the
> > > > 'mess'
> > > > > he's made (smile)?
> > > > >
> > > > > Before I try build myself, where are the build instructions?
> > > > >
> > > > > On the software grant, who is on that? This often takes way
> > > > > more time than folks would expect.
> > > > >
> > > > > Thanks,
> > > > > St.Ack
> > > > >
> > > > >
> > > > > On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik
> > > > > <roman@shaposhnik.org <javascript:;>>
> > > > > wrote:
> > > > >
> > > > > > Great progress! I'll definitely take a look Mon/Tue next week!
> > > > > >
> > > > > > Thanks,
> > > > > > Roman.
> > > > > >
> > > > > > On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> > > > > > <steve.varnau@hp.com <javascript:;>> wrote:
> > > > > > > I have pushed more changes to my traf-merged repo.
> > > > > > >
> > > > > > > * renamed "test" directory to "tests/phx"
> > > > > > > * added "wms" component (master branch only, as it has not
> > > > > > > been
> > > > > released)
> > > > > > > * added 1.x.x_<component> release tags for applicable
> > > > > > > components
> > > > > > >
> > > > > > > I did not bother with the 0.x.x release tags.
> > > > > > >
> > > > > > > Feedback, please.
> > > > > > >
> > > > > > > -Steve
> > > > > > >
> > > > > > >> -----Original Message-----
> > > > > > >> From: Varnau, Steve (Trafodion)
> > > > > > >> Sent: Thursday, May 28, 2015 15:42
> > > > > > >> To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > > > >> Subject: RE: Migrating code to Apache git -- multiple
> > > > > > >> repos
> > > > > > >>
> > > > > > >> I have a combined repo on github for folks to take a look
> at.
> > > > > > >>
> > > > > > >> https://github.com/svarnau/traf-merged
> > > > > > >>
> > > > > > >> The full history of all the repos is there for the three
> > > > > > >> release
> > > > > > >> branches: master, stable/1.0, stable/1.1
> > > > > > >>
> > > > > > >> I restructured the various repos into sub-directories for
> > > > > > >> each of the three branches. Install has only a master
> > > > > > >> branch, so it does not exist in the stable branches.
> > > > > > >>
> > > > > > >> Next I need to put in some key tags. Since the same
> > > > > > >> release tag names were used across repos, combining the
> > > > > > >> repos caused tags to
> > > > conflict.
> > > > > > >> I'll have to re-name them by repo.
> > > > > > >>
> > > > > > >> -Steve
> > > > > > >>
> > > > > > >> > -----Original Message-----
> > > > > > >> > From: Varnau, Steve (Trafodion)
> > > > > > >> > Sent: Wednesday, May 27, 2015 16:52
> > > > > > >> > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > > > >> > Subject: RE: Migrating code to Apache git -- multiple
> > > > > > >> > repos
> > > > > > >> >
> > > > > > >> > Thanks, guys. You've answered my questions. I'll work
> > > > > > >> > up a combined repo structure that we can review.
> > > > > > >> >
> > > > > > >> > -Steve
> > > > > > >> >
> > > > > > >> > > -----Original Message-----
> > > > > > >> > > From: shaposhnik@gmail.com <javascript:;> [mailto:
> > > shaposhnik@gmail.com <javascript:;>] On
> > > > > Behalf
> > > > > > >> > > Of Roman Shaposhnik
> > > > > > >> > > Sent: Wednesday, May 27, 2015 15:54
> > > > > > >> > > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > > > >> > > Subject: Re: Migrating code to Apache git -- multiple
> > > > > > >> > > repos
> > > > > > >> > >
> > > > > > >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve
> > > > > > >> > > (Trafodion) <steve.varnau@hp.com <javascript:;>> wrote:
> > > > > > >> > > > Sorry, I guess we can merge repos while retaining
> history.
> > > > > > >> > > > I
> > > > > just
> > > > > > >> > > > had
> > > > > > >> > > not done so before.
> > > > > > >> > >
> > > > > > >> > > I can help with that -- I've done it before.
> > > > > > >> > >
> > > > > > >> > > > Is that the preferred route?
> > > > > > >> > >
> > > > > > >> > > Yes.
> > > > > > >> > >
> > > > > > >> > > > The mechanics for migrating the trafodion code is
> > > > > > >> > > > for a
> > > > > committer
> > > > > > >> > > > to push the current code into the newly created repo?
> > > > > > >> > > > (When we are ready to pull that switch.)
> > > > > > >> > >
> > > > > > >> > > I'd suggest NOT involving INFRA in the mechanics of
> > > > > > >> > > repo
> > > > > migration.
> > > > > > >> > > At this point it is not simple enough and that will
> > > > > > >> > > be kind of
> > > > > tough
> > > > > > >> > > to communicate to ASF INFRA.
> > > > > > >> > >
> > > > > > >> > > What I suggest is this: create a brand new staging
> > > > > > >> > > repo on
> > GH.
> > > > > Merge
> > > > > > >> > > all the code there. Review the result. And once it
> > > > > > >> > > looks good do everybody just do a git push to ASF repo.
> > > > > > >> > >
> > > > > > >> > > Sounds reasonable?
> > > > > > >> > >
> > > > > > >> > > Thanks,
> > > > > > >> > > Roman.
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > --
> > Pierre Smits
> >
> > *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud-
> > Based Manufacturing, Professional Services and Retail & Trade
> > http://www.orrtiz.com
> >
RE: Migrating code to Apache git -- multiple repos
Posted by "Varnau, Steve (Trafodion)" <st...@hp.com>.
I'm too late to be the Apache Steve. But I will work with Alice to start the gears turning on code, jira, etc.
-Steve
> -----Original Message-----
> From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of
> Stack
> Sent: Friday, June 19, 2015 09:56
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Migrating code to Apache git -- multiple repos
>
> Ahem. Thanks for the comma Dave.
> St.Ack
>
> On Fri, Jun 19, 2015 at 8:47 AM, Birdsall, Dave <da...@hp.com>
> wrote:
>
> > I think he meant, "Apache, Steve?" (interesting how a missing comma
> > can change the meaning)
> >
> > -----Original Message-----
> > From: Pierre Smits [mailto:pierre.smits@gmail.com]
> > Sent: Friday, June 19, 2015 8:43 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: Re: Migrating code to Apache git -- multiple repos
> >
> > For sure not to Apache STeVe, as that is a totally different project.
> >
> > Best regards,
> >
> > Pierre
> >
> > Op vrijdag 19 juni 2015 heeft Stack <st...@duboce.net> het volgende
> > geschreven:
> >
> > > 1. and 2. below have been done by Dave (see
> > > http://www.apache.org/licenses/exports/).
> > >
> > > The VOTE on accepting the HP grant passed.
> > >
> > > Time to push from https://github.com/svarnau/traf-merged to Apache
> > Steve?
> > >
> > > St.Ack
> > >
> > >
> > > On Wed, Jun 10, 2015 at 2:53 PM, Deyager, Kevin
> > > <kevin.deyager@hp.com <javascript:;>>
> > > wrote:
> > >
> > > > Hi Stack,
> > > >
> > > > I am finalizing the SGA with an HP attorney. I am still hopeful
> > > > we can get this executed and submitted by the end of the week to
> > > > secretary@apache.org <javascript:;>.
> > > >
> > > > After that, before we can submit code, we need to deal with
> > > > cryptography
> > > > by:
> > > >
> > > > (1) updating the Exports page here (
> > > > http://www.apache.org/licenses/exports/) as follows:
> > > >
> > > > Product Name: Apache Trafodion
> > > > Versions: Development
> > > > ECCN: 5D002
> > > > Controlled Source:
> > > > ASF (git://git.apache.org/incubator-trafodion.git) -- Designed for
> > > > use with encryption library Oracle (
> > > http://www.oracle.com/technetwork/java/javase/downloads/index.html)
> > > > -- Designed for use with Java Cryptography Extensions (JCE) The
> > > > OpenSLL Project (http://www.openssl.org/source/) -- Publically
> > > > available SSL encryption library
> > > >
> > > > And then:
> > > >
> > > > (2) sending the email to notify the US government.
> > > >
> > > > I assume Dave Birdsall can edit the file on the Apache site and
> > > > send the email, being a committer and part of the Trafodion PMC,
> > > > if I am reading this correctly.
> > > >
> > > > The next activity is we open a JIRA and submit.
> > > >
> > > > We'd really like to get that code over early next week, if
> possible.
> > > > Is there any other steps or gotchas?
> > > >
> > > > Regards,
> > > > -- Kevin
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: saint.ack@gmail.com <javascript:;>
> > > > [mailto:saint.ack@gmail.com
> > > <javascript:;>] On Behalf Of Stack
> > > > Sent: Wednesday, June 10, 2015 9:53 AM
> > > > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > Subject: Re: Migrating code to Apache git -- multiple repos
> > > >
> > > > Thanks Kevin
> > > >
> > > > Any updates?
> > > >
> > > > Am I right in thinking this the (only?) barrier to our being able
> > > > to move over the code to apache?
> > > >
> > > > Thanks,
> > > > St.Ack
> > > >
> > > > On Fri, May 29, 2015 at 8:55 PM, Deyager, Kevin
> > > > <kevin.deyager@hp.com
> > > <javascript:;>>
> > > > wrote:
> > > >
> > > > > Hi Michael,
> > > > >
> > > > > I am working the SGA. And yes, things can work a bit slowly in
> > > > > big companies...
> > > > >
> > > > > Kevim
> > > > >
> > > > > On May 29, 2015 7:51 PM, Stack <stack@duboce.net <javascript:;>>
> > > wrote:
> > > > > HPers!
> > > > >
> > > > > You'll have to live w/ Steve's reorg going forward. You good w/
> > > > > the
> > > > 'mess'
> > > > > he's made (smile)?
> > > > >
> > > > > Before I try build myself, where are the build instructions?
> > > > >
> > > > > On the software grant, who is on that? This often takes way more
> > > > > time than folks would expect.
> > > > >
> > > > > Thanks,
> > > > > St.Ack
> > > > >
> > > > >
> > > > > On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik
> > > > > <roman@shaposhnik.org <javascript:;>>
> > > > > wrote:
> > > > >
> > > > > > Great progress! I'll definitely take a look Mon/Tue next week!
> > > > > >
> > > > > > Thanks,
> > > > > > Roman.
> > > > > >
> > > > > > On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> > > > > > <steve.varnau@hp.com <javascript:;>> wrote:
> > > > > > > I have pushed more changes to my traf-merged repo.
> > > > > > >
> > > > > > > * renamed "test" directory to "tests/phx"
> > > > > > > * added "wms" component (master branch only, as it has not
> > > > > > > been
> > > > > released)
> > > > > > > * added 1.x.x_<component> release tags for applicable
> > > > > > > components
> > > > > > >
> > > > > > > I did not bother with the 0.x.x release tags.
> > > > > > >
> > > > > > > Feedback, please.
> > > > > > >
> > > > > > > -Steve
> > > > > > >
> > > > > > >> -----Original Message-----
> > > > > > >> From: Varnau, Steve (Trafodion)
> > > > > > >> Sent: Thursday, May 28, 2015 15:42
> > > > > > >> To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > > > >> Subject: RE: Migrating code to Apache git -- multiple repos
> > > > > > >>
> > > > > > >> I have a combined repo on github for folks to take a look
> at.
> > > > > > >>
> > > > > > >> https://github.com/svarnau/traf-merged
> > > > > > >>
> > > > > > >> The full history of all the repos is there for the three
> > > > > > >> release
> > > > > > >> branches: master, stable/1.0, stable/1.1
> > > > > > >>
> > > > > > >> I restructured the various repos into sub-directories for
> > > > > > >> each of the three branches. Install has only a master
> > > > > > >> branch, so it does not exist in the stable branches.
> > > > > > >>
> > > > > > >> Next I need to put in some key tags. Since the same release
> > > > > > >> tag names were used across repos, combining the repos
> > > > > > >> caused tags to
> > > > conflict.
> > > > > > >> I'll have to re-name them by repo.
> > > > > > >>
> > > > > > >> -Steve
> > > > > > >>
> > > > > > >> > -----Original Message-----
> > > > > > >> > From: Varnau, Steve (Trafodion)
> > > > > > >> > Sent: Wednesday, May 27, 2015 16:52
> > > > > > >> > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > > > >> > Subject: RE: Migrating code to Apache git -- multiple
> > > > > > >> > repos
> > > > > > >> >
> > > > > > >> > Thanks, guys. You've answered my questions. I'll work up
> > > > > > >> > a combined repo structure that we can review.
> > > > > > >> >
> > > > > > >> > -Steve
> > > > > > >> >
> > > > > > >> > > -----Original Message-----
> > > > > > >> > > From: shaposhnik@gmail.com <javascript:;> [mailto:
> > > shaposhnik@gmail.com <javascript:;>] On
> > > > > Behalf
> > > > > > >> > > Of Roman Shaposhnik
> > > > > > >> > > Sent: Wednesday, May 27, 2015 15:54
> > > > > > >> > > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > > > >> > > Subject: Re: Migrating code to Apache git -- multiple
> > > > > > >> > > repos
> > > > > > >> > >
> > > > > > >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve
> > > > > > >> > > (Trafodion) <steve.varnau@hp.com <javascript:;>> wrote:
> > > > > > >> > > > Sorry, I guess we can merge repos while retaining
> history.
> > > > > > >> > > > I
> > > > > just
> > > > > > >> > > > had
> > > > > > >> > > not done so before.
> > > > > > >> > >
> > > > > > >> > > I can help with that -- I've done it before.
> > > > > > >> > >
> > > > > > >> > > > Is that the preferred route?
> > > > > > >> > >
> > > > > > >> > > Yes.
> > > > > > >> > >
> > > > > > >> > > > The mechanics for migrating the trafodion code is for
> > > > > > >> > > > a
> > > > > committer
> > > > > > >> > > > to push the current code into the newly created repo?
> > > > > > >> > > > (When we are ready to pull that switch.)
> > > > > > >> > >
> > > > > > >> > > I'd suggest NOT involving INFRA in the mechanics of
> > > > > > >> > > repo
> > > > > migration.
> > > > > > >> > > At this point it is not simple enough and that will be
> > > > > > >> > > kind of
> > > > > tough
> > > > > > >> > > to communicate to ASF INFRA.
> > > > > > >> > >
> > > > > > >> > > What I suggest is this: create a brand new staging repo
> > > > > > >> > > on
> > GH.
> > > > > Merge
> > > > > > >> > > all the code there. Review the result. And once it
> > > > > > >> > > looks good do everybody just do a git push to ASF repo.
> > > > > > >> > >
> > > > > > >> > > Sounds reasonable?
> > > > > > >> > >
> > > > > > >> > > Thanks,
> > > > > > >> > > Roman.
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > --
> > Pierre Smits
> >
> > *ORRTIZ.COM <http://www.orrtiz.com>*
> > Services & Solutions for Cloud-
> > Based Manufacturing, Professional
> > Services and Retail & Trade
> > http://www.orrtiz.com
> >
Re: Migrating code to Apache git -- multiple repos
Posted by Stack <st...@duboce.net>.
Ahem. Thanks for the comma Dave.
St.Ack
On Fri, Jun 19, 2015 at 8:47 AM, Birdsall, Dave <da...@hp.com>
wrote:
> I think he meant, "Apache, Steve?" (interesting how a missing comma can
> change the meaning)
>
> -----Original Message-----
> From: Pierre Smits [mailto:pierre.smits@gmail.com]
> Sent: Friday, June 19, 2015 8:43 AM
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Migrating code to Apache git -- multiple repos
>
> For sure not to Apache STeVe, as that is a totally different project.
>
> Best regards,
>
> Pierre
>
> Op vrijdag 19 juni 2015 heeft Stack <st...@duboce.net> het volgende
> geschreven:
>
> > 1. and 2. below have been done by Dave (see
> > http://www.apache.org/licenses/exports/).
> >
> > The VOTE on accepting the HP grant passed.
> >
> > Time to push from https://github.com/svarnau/traf-merged to Apache
> Steve?
> >
> > St.Ack
> >
> >
> > On Wed, Jun 10, 2015 at 2:53 PM, Deyager, Kevin <kevin.deyager@hp.com
> > <javascript:;>>
> > wrote:
> >
> > > Hi Stack,
> > >
> > > I am finalizing the SGA with an HP attorney. I am still hopeful we
> > > can get this executed and submitted by the end of the week to
> > > secretary@apache.org <javascript:;>.
> > >
> > > After that, before we can submit code, we need to deal with
> > > cryptography
> > > by:
> > >
> > > (1) updating the Exports page here (
> > > http://www.apache.org/licenses/exports/) as follows:
> > >
> > > Product Name: Apache Trafodion
> > > Versions: Development
> > > ECCN: 5D002
> > > Controlled Source:
> > > ASF (git://git.apache.org/incubator-trafodion.git) -- Designed for
> > > use with encryption library Oracle (
> > http://www.oracle.com/technetwork/java/javase/downloads/index.html)
> > > -- Designed for use with Java Cryptography Extensions (JCE) The
> > > OpenSLL Project (http://www.openssl.org/source/) -- Publically
> > > available SSL encryption library
> > >
> > > And then:
> > >
> > > (2) sending the email to notify the US government.
> > >
> > > I assume Dave Birdsall can edit the file on the Apache site and send
> > > the email, being a committer and part of the Trafodion PMC, if I am
> > > reading this correctly.
> > >
> > > The next activity is we open a JIRA and submit.
> > >
> > > We'd really like to get that code over early next week, if possible.
> > > Is there any other steps or gotchas?
> > >
> > > Regards,
> > > -- Kevin
> > >
> > >
> > > -----Original Message-----
> > > From: saint.ack@gmail.com <javascript:;> [mailto:saint.ack@gmail.com
> > <javascript:;>] On Behalf Of Stack
> > > Sent: Wednesday, June 10, 2015 9:53 AM
> > > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > Subject: Re: Migrating code to Apache git -- multiple repos
> > >
> > > Thanks Kevin
> > >
> > > Any updates?
> > >
> > > Am I right in thinking this the (only?) barrier to our being able to
> > > move over the code to apache?
> > >
> > > Thanks,
> > > St.Ack
> > >
> > > On Fri, May 29, 2015 at 8:55 PM, Deyager, Kevin
> > > <kevin.deyager@hp.com
> > <javascript:;>>
> > > wrote:
> > >
> > > > Hi Michael,
> > > >
> > > > I am working the SGA. And yes, things can work a bit slowly in
> > > > big companies...
> > > >
> > > > Kevim
> > > >
> > > > On May 29, 2015 7:51 PM, Stack <stack@duboce.net <javascript:;>>
> > wrote:
> > > > HPers!
> > > >
> > > > You'll have to live w/ Steve's reorg going forward. You good w/
> > > > the
> > > 'mess'
> > > > he's made (smile)?
> > > >
> > > > Before I try build myself, where are the build instructions?
> > > >
> > > > On the software grant, who is on that? This often takes way more
> > > > time than folks would expect.
> > > >
> > > > Thanks,
> > > > St.Ack
> > > >
> > > >
> > > > On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik
> > > > <roman@shaposhnik.org <javascript:;>>
> > > > wrote:
> > > >
> > > > > Great progress! I'll definitely take a look Mon/Tue next week!
> > > > >
> > > > > Thanks,
> > > > > Roman.
> > > > >
> > > > > On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> > > > > <steve.varnau@hp.com <javascript:;>> wrote:
> > > > > > I have pushed more changes to my traf-merged repo.
> > > > > >
> > > > > > * renamed "test" directory to "tests/phx"
> > > > > > * added "wms" component (master branch only, as it has not
> > > > > > been
> > > > released)
> > > > > > * added 1.x.x_<component> release tags for applicable
> > > > > > components
> > > > > >
> > > > > > I did not bother with the 0.x.x release tags.
> > > > > >
> > > > > > Feedback, please.
> > > > > >
> > > > > > -Steve
> > > > > >
> > > > > >> -----Original Message-----
> > > > > >> From: Varnau, Steve (Trafodion)
> > > > > >> Sent: Thursday, May 28, 2015 15:42
> > > > > >> To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > > >> Subject: RE: Migrating code to Apache git -- multiple repos
> > > > > >>
> > > > > >> I have a combined repo on github for folks to take a look at.
> > > > > >>
> > > > > >> https://github.com/svarnau/traf-merged
> > > > > >>
> > > > > >> The full history of all the repos is there for the three
> > > > > >> release
> > > > > >> branches: master, stable/1.0, stable/1.1
> > > > > >>
> > > > > >> I restructured the various repos into sub-directories for
> > > > > >> each of the three branches. Install has only a master branch,
> > > > > >> so it does not exist in the stable branches.
> > > > > >>
> > > > > >> Next I need to put in some key tags. Since the same release
> > > > > >> tag names were used across repos, combining the repos caused
> > > > > >> tags to
> > > conflict.
> > > > > >> I'll have to re-name them by repo.
> > > > > >>
> > > > > >> -Steve
> > > > > >>
> > > > > >> > -----Original Message-----
> > > > > >> > From: Varnau, Steve (Trafodion)
> > > > > >> > Sent: Wednesday, May 27, 2015 16:52
> > > > > >> > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > > >> > Subject: RE: Migrating code to Apache git -- multiple repos
> > > > > >> >
> > > > > >> > Thanks, guys. You've answered my questions. I'll work up a
> > > > > >> > combined repo structure that we can review.
> > > > > >> >
> > > > > >> > -Steve
> > > > > >> >
> > > > > >> > > -----Original Message-----
> > > > > >> > > From: shaposhnik@gmail.com <javascript:;> [mailto:
> > shaposhnik@gmail.com <javascript:;>] On
> > > > Behalf
> > > > > >> > > Of Roman Shaposhnik
> > > > > >> > > Sent: Wednesday, May 27, 2015 15:54
> > > > > >> > > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > > >> > > Subject: Re: Migrating code to Apache git -- multiple
> > > > > >> > > repos
> > > > > >> > >
> > > > > >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve
> > > > > >> > > (Trafodion) <steve.varnau@hp.com <javascript:;>> wrote:
> > > > > >> > > > Sorry, I guess we can merge repos while retaining history.
> > > > > >> > > > I
> > > > just
> > > > > >> > > > had
> > > > > >> > > not done so before.
> > > > > >> > >
> > > > > >> > > I can help with that -- I've done it before.
> > > > > >> > >
> > > > > >> > > > Is that the preferred route?
> > > > > >> > >
> > > > > >> > > Yes.
> > > > > >> > >
> > > > > >> > > > The mechanics for migrating the trafodion code is for a
> > > > committer
> > > > > >> > > > to push the current code into the newly created repo?
> > > > > >> > > > (When we are ready to pull that switch.)
> > > > > >> > >
> > > > > >> > > I'd suggest NOT involving INFRA in the mechanics of repo
> > > > migration.
> > > > > >> > > At this point it is not simple enough and that will be
> > > > > >> > > kind of
> > > > tough
> > > > > >> > > to communicate to ASF INFRA.
> > > > > >> > >
> > > > > >> > > What I suggest is this: create a brand new staging repo on
> GH.
> > > > Merge
> > > > > >> > > all the code there. Review the result. And once it looks
> > > > > >> > > good do everybody just do a git push to ASF repo.
> > > > > >> > >
> > > > > >> > > Sounds reasonable?
> > > > > >> > >
> > > > > >> > > Thanks,
> > > > > >> > > Roman.
> > > > >
> > > >
> > >
> >
>
>
> --
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
RE: Migrating code to Apache git -- multiple repos
Posted by "Birdsall, Dave" <da...@hp.com>.
I think he meant, "Apache, Steve?" (interesting how a missing comma can change the meaning)
-----Original Message-----
From: Pierre Smits [mailto:pierre.smits@gmail.com]
Sent: Friday, June 19, 2015 8:43 AM
To: dev@trafodion.incubator.apache.org
Subject: Re: Migrating code to Apache git -- multiple repos
For sure not to Apache STeVe, as that is a totally different project.
Best regards,
Pierre
Op vrijdag 19 juni 2015 heeft Stack <st...@duboce.net> het volgende
geschreven:
> 1. and 2. below have been done by Dave (see
> http://www.apache.org/licenses/exports/).
>
> The VOTE on accepting the HP grant passed.
>
> Time to push from https://github.com/svarnau/traf-merged to Apache Steve?
>
> St.Ack
>
>
> On Wed, Jun 10, 2015 at 2:53 PM, Deyager, Kevin <kevin.deyager@hp.com
> <javascript:;>>
> wrote:
>
> > Hi Stack,
> >
> > I am finalizing the SGA with an HP attorney. I am still hopeful we
> > can get this executed and submitted by the end of the week to
> > secretary@apache.org <javascript:;>.
> >
> > After that, before we can submit code, we need to deal with
> > cryptography
> > by:
> >
> > (1) updating the Exports page here (
> > http://www.apache.org/licenses/exports/) as follows:
> >
> > Product Name: Apache Trafodion
> > Versions: Development
> > ECCN: 5D002
> > Controlled Source:
> > ASF (git://git.apache.org/incubator-trafodion.git) -- Designed for
> > use with encryption library Oracle (
> http://www.oracle.com/technetwork/java/javase/downloads/index.html)
> > -- Designed for use with Java Cryptography Extensions (JCE) The
> > OpenSLL Project (http://www.openssl.org/source/) -- Publically
> > available SSL encryption library
> >
> > And then:
> >
> > (2) sending the email to notify the US government.
> >
> > I assume Dave Birdsall can edit the file on the Apache site and send
> > the email, being a committer and part of the Trafodion PMC, if I am
> > reading this correctly.
> >
> > The next activity is we open a JIRA and submit.
> >
> > We'd really like to get that code over early next week, if possible.
> > Is there any other steps or gotchas?
> >
> > Regards,
> > -- Kevin
> >
> >
> > -----Original Message-----
> > From: saint.ack@gmail.com <javascript:;> [mailto:saint.ack@gmail.com
> <javascript:;>] On Behalf Of Stack
> > Sent: Wednesday, June 10, 2015 9:53 AM
> > To: dev@trafodion.incubator.apache.org <javascript:;>
> > Subject: Re: Migrating code to Apache git -- multiple repos
> >
> > Thanks Kevin
> >
> > Any updates?
> >
> > Am I right in thinking this the (only?) barrier to our being able to
> > move over the code to apache?
> >
> > Thanks,
> > St.Ack
> >
> > On Fri, May 29, 2015 at 8:55 PM, Deyager, Kevin
> > <kevin.deyager@hp.com
> <javascript:;>>
> > wrote:
> >
> > > Hi Michael,
> > >
> > > I am working the SGA. And yes, things can work a bit slowly in
> > > big companies...
> > >
> > > Kevim
> > >
> > > On May 29, 2015 7:51 PM, Stack <stack@duboce.net <javascript:;>>
> wrote:
> > > HPers!
> > >
> > > You'll have to live w/ Steve's reorg going forward. You good w/
> > > the
> > 'mess'
> > > he's made (smile)?
> > >
> > > Before I try build myself, where are the build instructions?
> > >
> > > On the software grant, who is on that? This often takes way more
> > > time than folks would expect.
> > >
> > > Thanks,
> > > St.Ack
> > >
> > >
> > > On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik
> > > <roman@shaposhnik.org <javascript:;>>
> > > wrote:
> > >
> > > > Great progress! I'll definitely take a look Mon/Tue next week!
> > > >
> > > > Thanks,
> > > > Roman.
> > > >
> > > > On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> > > > <steve.varnau@hp.com <javascript:;>> wrote:
> > > > > I have pushed more changes to my traf-merged repo.
> > > > >
> > > > > * renamed "test" directory to "tests/phx"
> > > > > * added "wms" component (master branch only, as it has not
> > > > > been
> > > released)
> > > > > * added 1.x.x_<component> release tags for applicable
> > > > > components
> > > > >
> > > > > I did not bother with the 0.x.x release tags.
> > > > >
> > > > > Feedback, please.
> > > > >
> > > > > -Steve
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: Varnau, Steve (Trafodion)
> > > > >> Sent: Thursday, May 28, 2015 15:42
> > > > >> To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > >> Subject: RE: Migrating code to Apache git -- multiple repos
> > > > >>
> > > > >> I have a combined repo on github for folks to take a look at.
> > > > >>
> > > > >> https://github.com/svarnau/traf-merged
> > > > >>
> > > > >> The full history of all the repos is there for the three
> > > > >> release
> > > > >> branches: master, stable/1.0, stable/1.1
> > > > >>
> > > > >> I restructured the various repos into sub-directories for
> > > > >> each of the three branches. Install has only a master branch,
> > > > >> so it does not exist in the stable branches.
> > > > >>
> > > > >> Next I need to put in some key tags. Since the same release
> > > > >> tag names were used across repos, combining the repos caused
> > > > >> tags to
> > conflict.
> > > > >> I'll have to re-name them by repo.
> > > > >>
> > > > >> -Steve
> > > > >>
> > > > >> > -----Original Message-----
> > > > >> > From: Varnau, Steve (Trafodion)
> > > > >> > Sent: Wednesday, May 27, 2015 16:52
> > > > >> > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > >> > Subject: RE: Migrating code to Apache git -- multiple repos
> > > > >> >
> > > > >> > Thanks, guys. You've answered my questions. I'll work up a
> > > > >> > combined repo structure that we can review.
> > > > >> >
> > > > >> > -Steve
> > > > >> >
> > > > >> > > -----Original Message-----
> > > > >> > > From: shaposhnik@gmail.com <javascript:;> [mailto:
> shaposhnik@gmail.com <javascript:;>] On
> > > Behalf
> > > > >> > > Of Roman Shaposhnik
> > > > >> > > Sent: Wednesday, May 27, 2015 15:54
> > > > >> > > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > >> > > Subject: Re: Migrating code to Apache git -- multiple
> > > > >> > > repos
> > > > >> > >
> > > > >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve
> > > > >> > > (Trafodion) <steve.varnau@hp.com <javascript:;>> wrote:
> > > > >> > > > Sorry, I guess we can merge repos while retaining history.
> > > > >> > > > I
> > > just
> > > > >> > > > had
> > > > >> > > not done so before.
> > > > >> > >
> > > > >> > > I can help with that -- I've done it before.
> > > > >> > >
> > > > >> > > > Is that the preferred route?
> > > > >> > >
> > > > >> > > Yes.
> > > > >> > >
> > > > >> > > > The mechanics for migrating the trafodion code is for a
> > > committer
> > > > >> > > > to push the current code into the newly created repo?
> > > > >> > > > (When we are ready to pull that switch.)
> > > > >> > >
> > > > >> > > I'd suggest NOT involving INFRA in the mechanics of repo
> > > migration.
> > > > >> > > At this point it is not simple enough and that will be
> > > > >> > > kind of
> > > tough
> > > > >> > > to communicate to ASF INFRA.
> > > > >> > >
> > > > >> > > What I suggest is this: create a brand new staging repo on GH.
> > > Merge
> > > > >> > > all the code there. Review the result. And once it looks
> > > > >> > > good do everybody just do a git push to ASF repo.
> > > > >> > >
> > > > >> > > Sounds reasonable?
> > > > >> > >
> > > > >> > > Thanks,
> > > > >> > > Roman.
> > > >
> > >
> >
>
--
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
Re: Migrating code to Apache git -- multiple repos
Posted by Pierre Smits <pi...@gmail.com>.
For sure not to Apache STeVe, as that is a totally different project.
Best regards,
Pierre
Op vrijdag 19 juni 2015 heeft Stack <st...@duboce.net> het volgende
geschreven:
> 1. and 2. below have been done by Dave (see
> http://www.apache.org/licenses/exports/).
>
> The VOTE on accepting the HP grant passed.
>
> Time to push from https://github.com/svarnau/traf-merged to Apache Steve?
>
> St.Ack
>
>
> On Wed, Jun 10, 2015 at 2:53 PM, Deyager, Kevin <kevin.deyager@hp.com
> <javascript:;>>
> wrote:
>
> > Hi Stack,
> >
> > I am finalizing the SGA with an HP attorney. I am still hopeful we can
> > get this executed and submitted by the end of the week to
> > secretary@apache.org <javascript:;>.
> >
> > After that, before we can submit code, we need to deal with cryptography
> > by:
> >
> > (1) updating the Exports page here (
> > http://www.apache.org/licenses/exports/) as follows:
> >
> > Product Name: Apache Trafodion
> > Versions: Development
> > ECCN: 5D002
> > Controlled Source:
> > ASF (git://git.apache.org/incubator-trafodion.git) -- Designed for use
> > with encryption library
> > Oracle (
> http://www.oracle.com/technetwork/java/javase/downloads/index.html)
> > -- Designed for use with Java Cryptography Extensions (JCE)
> > The OpenSLL Project (http://www.openssl.org/source/) -- Publically
> > available SSL encryption library
> >
> > And then:
> >
> > (2) sending the email to notify the US government.
> >
> > I assume Dave Birdsall can edit the file on the Apache site and send the
> > email, being a committer and part of the Trafodion PMC, if I am reading
> > this correctly.
> >
> > The next activity is we open a JIRA and submit.
> >
> > We'd really like to get that code over early next week, if possible. Is
> > there any other steps or gotchas?
> >
> > Regards,
> > -- Kevin
> >
> >
> > -----Original Message-----
> > From: saint.ack@gmail.com <javascript:;> [mailto:saint.ack@gmail.com
> <javascript:;>] On Behalf Of Stack
> > Sent: Wednesday, June 10, 2015 9:53 AM
> > To: dev@trafodion.incubator.apache.org <javascript:;>
> > Subject: Re: Migrating code to Apache git -- multiple repos
> >
> > Thanks Kevin
> >
> > Any updates?
> >
> > Am I right in thinking this the (only?) barrier to our being able to move
> > over the code to apache?
> >
> > Thanks,
> > St.Ack
> >
> > On Fri, May 29, 2015 at 8:55 PM, Deyager, Kevin <kevin.deyager@hp.com
> <javascript:;>>
> > wrote:
> >
> > > Hi Michael,
> > >
> > > I am working the SGA. And yes, things can work a bit slowly in big
> > > companies...
> > >
> > > Kevim
> > >
> > > On May 29, 2015 7:51 PM, Stack <stack@duboce.net <javascript:;>>
> wrote:
> > > HPers!
> > >
> > > You'll have to live w/ Steve's reorg going forward. You good w/ the
> > 'mess'
> > > he's made (smile)?
> > >
> > > Before I try build myself, where are the build instructions?
> > >
> > > On the software grant, who is on that? This often takes way more time
> > > than folks would expect.
> > >
> > > Thanks,
> > > St.Ack
> > >
> > >
> > > On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik
> > > <roman@shaposhnik.org <javascript:;>>
> > > wrote:
> > >
> > > > Great progress! I'll definitely take a look Mon/Tue next week!
> > > >
> > > > Thanks,
> > > > Roman.
> > > >
> > > > On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> > > > <steve.varnau@hp.com <javascript:;>> wrote:
> > > > > I have pushed more changes to my traf-merged repo.
> > > > >
> > > > > * renamed "test" directory to "tests/phx"
> > > > > * added "wms" component (master branch only, as it has not been
> > > released)
> > > > > * added 1.x.x_<component> release tags for applicable components
> > > > >
> > > > > I did not bother with the 0.x.x release tags.
> > > > >
> > > > > Feedback, please.
> > > > >
> > > > > -Steve
> > > > >
> > > > >> -----Original Message-----
> > > > >> From: Varnau, Steve (Trafodion)
> > > > >> Sent: Thursday, May 28, 2015 15:42
> > > > >> To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > >> Subject: RE: Migrating code to Apache git -- multiple repos
> > > > >>
> > > > >> I have a combined repo on github for folks to take a look at.
> > > > >>
> > > > >> https://github.com/svarnau/traf-merged
> > > > >>
> > > > >> The full history of all the repos is there for the three release
> > > > >> branches: master, stable/1.0, stable/1.1
> > > > >>
> > > > >> I restructured the various repos into sub-directories for each of
> > > > >> the three branches. Install has only a master branch, so it does
> > > > >> not exist in the stable branches.
> > > > >>
> > > > >> Next I need to put in some key tags. Since the same release tag
> > > > >> names were used across repos, combining the repos caused tags to
> > conflict.
> > > > >> I'll have to re-name them by repo.
> > > > >>
> > > > >> -Steve
> > > > >>
> > > > >> > -----Original Message-----
> > > > >> > From: Varnau, Steve (Trafodion)
> > > > >> > Sent: Wednesday, May 27, 2015 16:52
> > > > >> > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > >> > Subject: RE: Migrating code to Apache git -- multiple repos
> > > > >> >
> > > > >> > Thanks, guys. You've answered my questions. I'll work up a
> > > > >> > combined repo structure that we can review.
> > > > >> >
> > > > >> > -Steve
> > > > >> >
> > > > >> > > -----Original Message-----
> > > > >> > > From: shaposhnik@gmail.com <javascript:;> [mailto:
> shaposhnik@gmail.com <javascript:;>] On
> > > Behalf
> > > > >> > > Of Roman Shaposhnik
> > > > >> > > Sent: Wednesday, May 27, 2015 15:54
> > > > >> > > To: dev@trafodion.incubator.apache.org <javascript:;>
> > > > >> > > Subject: Re: Migrating code to Apache git -- multiple repos
> > > > >> > >
> > > > >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
> > > > >> > > <steve.varnau@hp.com <javascript:;>> wrote:
> > > > >> > > > Sorry, I guess we can merge repos while retaining history.
> > > > >> > > > I
> > > just
> > > > >> > > > had
> > > > >> > > not done so before.
> > > > >> > >
> > > > >> > > I can help with that -- I've done it before.
> > > > >> > >
> > > > >> > > > Is that the preferred route?
> > > > >> > >
> > > > >> > > Yes.
> > > > >> > >
> > > > >> > > > The mechanics for migrating the trafodion code is for a
> > > committer
> > > > >> > > > to push the current code into the newly created repo?
> > > > >> > > > (When we are ready to pull that switch.)
> > > > >> > >
> > > > >> > > I'd suggest NOT involving INFRA in the mechanics of repo
> > > migration.
> > > > >> > > At this point it is not simple enough and that will be kind
> > > > >> > > of
> > > tough
> > > > >> > > to communicate to ASF INFRA.
> > > > >> > >
> > > > >> > > What I suggest is this: create a brand new staging repo on GH.
> > > Merge
> > > > >> > > all the code there. Review the result. And once it looks good
> > > > >> > > do everybody just do a git push to ASF repo.
> > > > >> > >
> > > > >> > > Sounds reasonable?
> > > > >> > >
> > > > >> > > Thanks,
> > > > >> > > Roman.
> > > >
> > >
> >
>
--
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
Re: Migrating code to Apache git -- multiple repos
Posted by Stack <st...@duboce.net>.
1. and 2. below have been done by Dave (see
http://www.apache.org/licenses/exports/).
The VOTE on accepting the HP grant passed.
Time to push from https://github.com/svarnau/traf-merged to Apache Steve?
St.Ack
On Wed, Jun 10, 2015 at 2:53 PM, Deyager, Kevin <ke...@hp.com>
wrote:
> Hi Stack,
>
> I am finalizing the SGA with an HP attorney. I am still hopeful we can
> get this executed and submitted by the end of the week to
> secretary@apache.org.
>
> After that, before we can submit code, we need to deal with cryptography
> by:
>
> (1) updating the Exports page here (
> http://www.apache.org/licenses/exports/) as follows:
>
> Product Name: Apache Trafodion
> Versions: Development
> ECCN: 5D002
> Controlled Source:
> ASF (git://git.apache.org/incubator-trafodion.git) -- Designed for use
> with encryption library
> Oracle (http://www.oracle.com/technetwork/java/javase/downloads/index.html)
> -- Designed for use with Java Cryptography Extensions (JCE)
> The OpenSLL Project (http://www.openssl.org/source/) -- Publically
> available SSL encryption library
>
> And then:
>
> (2) sending the email to notify the US government.
>
> I assume Dave Birdsall can edit the file on the Apache site and send the
> email, being a committer and part of the Trafodion PMC, if I am reading
> this correctly.
>
> The next activity is we open a JIRA and submit.
>
> We'd really like to get that code over early next week, if possible. Is
> there any other steps or gotchas?
>
> Regards,
> -- Kevin
>
>
> -----Original Message-----
> From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of Stack
> Sent: Wednesday, June 10, 2015 9:53 AM
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Migrating code to Apache git -- multiple repos
>
> Thanks Kevin
>
> Any updates?
>
> Am I right in thinking this the (only?) barrier to our being able to move
> over the code to apache?
>
> Thanks,
> St.Ack
>
> On Fri, May 29, 2015 at 8:55 PM, Deyager, Kevin <ke...@hp.com>
> wrote:
>
> > Hi Michael,
> >
> > I am working the SGA. And yes, things can work a bit slowly in big
> > companies...
> >
> > Kevim
> >
> > On May 29, 2015 7:51 PM, Stack <st...@duboce.net> wrote:
> > HPers!
> >
> > You'll have to live w/ Steve's reorg going forward. You good w/ the
> 'mess'
> > he's made (smile)?
> >
> > Before I try build myself, where are the build instructions?
> >
> > On the software grant, who is on that? This often takes way more time
> > than folks would expect.
> >
> > Thanks,
> > St.Ack
> >
> >
> > On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik
> > <ro...@shaposhnik.org>
> > wrote:
> >
> > > Great progress! I'll definitely take a look Mon/Tue next week!
> > >
> > > Thanks,
> > > Roman.
> > >
> > > On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> > > <st...@hp.com> wrote:
> > > > I have pushed more changes to my traf-merged repo.
> > > >
> > > > * renamed "test" directory to "tests/phx"
> > > > * added "wms" component (master branch only, as it has not been
> > released)
> > > > * added 1.x.x_<component> release tags for applicable components
> > > >
> > > > I did not bother with the 0.x.x release tags.
> > > >
> > > > Feedback, please.
> > > >
> > > > -Steve
> > > >
> > > >> -----Original Message-----
> > > >> From: Varnau, Steve (Trafodion)
> > > >> Sent: Thursday, May 28, 2015 15:42
> > > >> To: dev@trafodion.incubator.apache.org
> > > >> Subject: RE: Migrating code to Apache git -- multiple repos
> > > >>
> > > >> I have a combined repo on github for folks to take a look at.
> > > >>
> > > >> https://github.com/svarnau/traf-merged
> > > >>
> > > >> The full history of all the repos is there for the three release
> > > >> branches: master, stable/1.0, stable/1.1
> > > >>
> > > >> I restructured the various repos into sub-directories for each of
> > > >> the three branches. Install has only a master branch, so it does
> > > >> not exist in the stable branches.
> > > >>
> > > >> Next I need to put in some key tags. Since the same release tag
> > > >> names were used across repos, combining the repos caused tags to
> conflict.
> > > >> I'll have to re-name them by repo.
> > > >>
> > > >> -Steve
> > > >>
> > > >> > -----Original Message-----
> > > >> > From: Varnau, Steve (Trafodion)
> > > >> > Sent: Wednesday, May 27, 2015 16:52
> > > >> > To: dev@trafodion.incubator.apache.org
> > > >> > Subject: RE: Migrating code to Apache git -- multiple repos
> > > >> >
> > > >> > Thanks, guys. You've answered my questions. I'll work up a
> > > >> > combined repo structure that we can review.
> > > >> >
> > > >> > -Steve
> > > >> >
> > > >> > > -----Original Message-----
> > > >> > > From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On
> > Behalf
> > > >> > > Of Roman Shaposhnik
> > > >> > > Sent: Wednesday, May 27, 2015 15:54
> > > >> > > To: dev@trafodion.incubator.apache.org
> > > >> > > Subject: Re: Migrating code to Apache git -- multiple repos
> > > >> > >
> > > >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
> > > >> > > <st...@hp.com> wrote:
> > > >> > > > Sorry, I guess we can merge repos while retaining history.
> > > >> > > > I
> > just
> > > >> > > > had
> > > >> > > not done so before.
> > > >> > >
> > > >> > > I can help with that -- I've done it before.
> > > >> > >
> > > >> > > > Is that the preferred route?
> > > >> > >
> > > >> > > Yes.
> > > >> > >
> > > >> > > > The mechanics for migrating the trafodion code is for a
> > committer
> > > >> > > > to push the current code into the newly created repo?
> > > >> > > > (When we are ready to pull that switch.)
> > > >> > >
> > > >> > > I'd suggest NOT involving INFRA in the mechanics of repo
> > migration.
> > > >> > > At this point it is not simple enough and that will be kind
> > > >> > > of
> > tough
> > > >> > > to communicate to ASF INFRA.
> > > >> > >
> > > >> > > What I suggest is this: create a brand new staging repo on GH.
> > Merge
> > > >> > > all the code there. Review the result. And once it looks good
> > > >> > > do everybody just do a git push to ASF repo.
> > > >> > >
> > > >> > > Sounds reasonable?
> > > >> > >
> > > >> > > Thanks,
> > > >> > > Roman.
> > >
> >
>
Re: Migrating code to Apache git -- multiple repos
Posted by Stack <st...@duboce.net>.
Thats good news Kevin (can't think of what else -- you seem to have it well
covered).
Thanks,
St.Ack
On Wed, Jun 10, 2015 at 2:53 PM, Deyager, Kevin <ke...@hp.com>
wrote:
> Hi Stack,
>
> I am finalizing the SGA with an HP attorney. I am still hopeful we can
> get this executed and submitted by the end of the week to
> secretary@apache.org.
>
> After that, before we can submit code, we need to deal with cryptography
> by:
>
> (1) updating the Exports page here (
> http://www.apache.org/licenses/exports/) as follows:
>
> Product Name: Apache Trafodion
> Versions: Development
> ECCN: 5D002
> Controlled Source:
> ASF (git://git.apache.org/incubator-trafodion.git) -- Designed for use
> with encryption library
> Oracle (http://www.oracle.com/technetwork/java/javase/downloads/index.html)
> -- Designed for use with Java Cryptography Extensions (JCE)
> The OpenSLL Project (http://www.openssl.org/source/) -- Publically
> available SSL encryption library
>
> And then:
>
> (2) sending the email to notify the US government.
>
> I assume Dave Birdsall can edit the file on the Apache site and send the
> email, being a committer and part of the Trafodion PMC, if I am reading
> this correctly.
>
> The next activity is we open a JIRA and submit.
>
> We'd really like to get that code over early next week, if possible. Is
> there any other steps or gotchas?
>
> Regards,
> -- Kevin
>
>
> -----Original Message-----
> From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of Stack
> Sent: Wednesday, June 10, 2015 9:53 AM
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Migrating code to Apache git -- multiple repos
>
> Thanks Kevin
>
> Any updates?
>
> Am I right in thinking this the (only?) barrier to our being able to move
> over the code to apache?
>
> Thanks,
> St.Ack
>
> On Fri, May 29, 2015 at 8:55 PM, Deyager, Kevin <ke...@hp.com>
> wrote:
>
> > Hi Michael,
> >
> > I am working the SGA. And yes, things can work a bit slowly in big
> > companies...
> >
> > Kevim
> >
> > On May 29, 2015 7:51 PM, Stack <st...@duboce.net> wrote:
> > HPers!
> >
> > You'll have to live w/ Steve's reorg going forward. You good w/ the
> 'mess'
> > he's made (smile)?
> >
> > Before I try build myself, where are the build instructions?
> >
> > On the software grant, who is on that? This often takes way more time
> > than folks would expect.
> >
> > Thanks,
> > St.Ack
> >
> >
> > On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik
> > <ro...@shaposhnik.org>
> > wrote:
> >
> > > Great progress! I'll definitely take a look Mon/Tue next week!
> > >
> > > Thanks,
> > > Roman.
> > >
> > > On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> > > <st...@hp.com> wrote:
> > > > I have pushed more changes to my traf-merged repo.
> > > >
> > > > * renamed "test" directory to "tests/phx"
> > > > * added "wms" component (master branch only, as it has not been
> > released)
> > > > * added 1.x.x_<component> release tags for applicable components
> > > >
> > > > I did not bother with the 0.x.x release tags.
> > > >
> > > > Feedback, please.
> > > >
> > > > -Steve
> > > >
> > > >> -----Original Message-----
> > > >> From: Varnau, Steve (Trafodion)
> > > >> Sent: Thursday, May 28, 2015 15:42
> > > >> To: dev@trafodion.incubator.apache.org
> > > >> Subject: RE: Migrating code to Apache git -- multiple repos
> > > >>
> > > >> I have a combined repo on github for folks to take a look at.
> > > >>
> > > >> https://github.com/svarnau/traf-merged
> > > >>
> > > >> The full history of all the repos is there for the three release
> > > >> branches: master, stable/1.0, stable/1.1
> > > >>
> > > >> I restructured the various repos into sub-directories for each of
> > > >> the three branches. Install has only a master branch, so it does
> > > >> not exist in the stable branches.
> > > >>
> > > >> Next I need to put in some key tags. Since the same release tag
> > > >> names were used across repos, combining the repos caused tags to
> conflict.
> > > >> I'll have to re-name them by repo.
> > > >>
> > > >> -Steve
> > > >>
> > > >> > -----Original Message-----
> > > >> > From: Varnau, Steve (Trafodion)
> > > >> > Sent: Wednesday, May 27, 2015 16:52
> > > >> > To: dev@trafodion.incubator.apache.org
> > > >> > Subject: RE: Migrating code to Apache git -- multiple repos
> > > >> >
> > > >> > Thanks, guys. You've answered my questions. I'll work up a
> > > >> > combined repo structure that we can review.
> > > >> >
> > > >> > -Steve
> > > >> >
> > > >> > > -----Original Message-----
> > > >> > > From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On
> > Behalf
> > > >> > > Of Roman Shaposhnik
> > > >> > > Sent: Wednesday, May 27, 2015 15:54
> > > >> > > To: dev@trafodion.incubator.apache.org
> > > >> > > Subject: Re: Migrating code to Apache git -- multiple repos
> > > >> > >
> > > >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
> > > >> > > <st...@hp.com> wrote:
> > > >> > > > Sorry, I guess we can merge repos while retaining history.
> > > >> > > > I
> > just
> > > >> > > > had
> > > >> > > not done so before.
> > > >> > >
> > > >> > > I can help with that -- I've done it before.
> > > >> > >
> > > >> > > > Is that the preferred route?
> > > >> > >
> > > >> > > Yes.
> > > >> > >
> > > >> > > > The mechanics for migrating the trafodion code is for a
> > committer
> > > >> > > > to push the current code into the newly created repo?
> > > >> > > > (When we are ready to pull that switch.)
> > > >> > >
> > > >> > > I'd suggest NOT involving INFRA in the mechanics of repo
> > migration.
> > > >> > > At this point it is not simple enough and that will be kind
> > > >> > > of
> > tough
> > > >> > > to communicate to ASF INFRA.
> > > >> > >
> > > >> > > What I suggest is this: create a brand new staging repo on GH.
> > Merge
> > > >> > > all the code there. Review the result. And once it looks good
> > > >> > > do everybody just do a git push to ASF repo.
> > > >> > >
> > > >> > > Sounds reasonable?
> > > >> > >
> > > >> > > Thanks,
> > > >> > > Roman.
> > >
> >
>
RE: Migrating code to Apache git -- multiple repos
Posted by "Deyager, Kevin" <ke...@hp.com>.
Hi Stack,
I am finalizing the SGA with an HP attorney. I am still hopeful we can get this executed and submitted by the end of the week to secretary@apache.org.
After that, before we can submit code, we need to deal with cryptography by:
(1) updating the Exports page here (http://www.apache.org/licenses/exports/) as follows:
Product Name: Apache Trafodion
Versions: Development
ECCN: 5D002
Controlled Source:
ASF (git://git.apache.org/incubator-trafodion.git) -- Designed for use with encryption library
Oracle (http://www.oracle.com/technetwork/java/javase/downloads/index.html) -- Designed for use with Java Cryptography Extensions (JCE)
The OpenSLL Project (http://www.openssl.org/source/) -- Publically available SSL encryption library
And then:
(2) sending the email to notify the US government.
I assume Dave Birdsall can edit the file on the Apache site and send the email, being a committer and part of the Trafodion PMC, if I am reading this correctly.
The next activity is we open a JIRA and submit.
We'd really like to get that code over early next week, if possible. Is there any other steps or gotchas?
Regards,
-- Kevin
-----Original Message-----
From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of Stack
Sent: Wednesday, June 10, 2015 9:53 AM
To: dev@trafodion.incubator.apache.org
Subject: Re: Migrating code to Apache git -- multiple repos
Thanks Kevin
Any updates?
Am I right in thinking this the (only?) barrier to our being able to move over the code to apache?
Thanks,
St.Ack
On Fri, May 29, 2015 at 8:55 PM, Deyager, Kevin <ke...@hp.com>
wrote:
> Hi Michael,
>
> I am working the SGA. And yes, things can work a bit slowly in big
> companies...
>
> Kevim
>
> On May 29, 2015 7:51 PM, Stack <st...@duboce.net> wrote:
> HPers!
>
> You'll have to live w/ Steve's reorg going forward. You good w/ the 'mess'
> he's made (smile)?
>
> Before I try build myself, where are the build instructions?
>
> On the software grant, who is on that? This often takes way more time
> than folks would expect.
>
> Thanks,
> St.Ack
>
>
> On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik
> <ro...@shaposhnik.org>
> wrote:
>
> > Great progress! I'll definitely take a look Mon/Tue next week!
> >
> > Thanks,
> > Roman.
> >
> > On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> > <st...@hp.com> wrote:
> > > I have pushed more changes to my traf-merged repo.
> > >
> > > * renamed "test" directory to "tests/phx"
> > > * added "wms" component (master branch only, as it has not been
> released)
> > > * added 1.x.x_<component> release tags for applicable components
> > >
> > > I did not bother with the 0.x.x release tags.
> > >
> > > Feedback, please.
> > >
> > > -Steve
> > >
> > >> -----Original Message-----
> > >> From: Varnau, Steve (Trafodion)
> > >> Sent: Thursday, May 28, 2015 15:42
> > >> To: dev@trafodion.incubator.apache.org
> > >> Subject: RE: Migrating code to Apache git -- multiple repos
> > >>
> > >> I have a combined repo on github for folks to take a look at.
> > >>
> > >> https://github.com/svarnau/traf-merged
> > >>
> > >> The full history of all the repos is there for the three release
> > >> branches: master, stable/1.0, stable/1.1
> > >>
> > >> I restructured the various repos into sub-directories for each of
> > >> the three branches. Install has only a master branch, so it does
> > >> not exist in the stable branches.
> > >>
> > >> Next I need to put in some key tags. Since the same release tag
> > >> names were used across repos, combining the repos caused tags to conflict.
> > >> I'll have to re-name them by repo.
> > >>
> > >> -Steve
> > >>
> > >> > -----Original Message-----
> > >> > From: Varnau, Steve (Trafodion)
> > >> > Sent: Wednesday, May 27, 2015 16:52
> > >> > To: dev@trafodion.incubator.apache.org
> > >> > Subject: RE: Migrating code to Apache git -- multiple repos
> > >> >
> > >> > Thanks, guys. You've answered my questions. I'll work up a
> > >> > combined repo structure that we can review.
> > >> >
> > >> > -Steve
> > >> >
> > >> > > -----Original Message-----
> > >> > > From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On
> Behalf
> > >> > > Of Roman Shaposhnik
> > >> > > Sent: Wednesday, May 27, 2015 15:54
> > >> > > To: dev@trafodion.incubator.apache.org
> > >> > > Subject: Re: Migrating code to Apache git -- multiple repos
> > >> > >
> > >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
> > >> > > <st...@hp.com> wrote:
> > >> > > > Sorry, I guess we can merge repos while retaining history.
> > >> > > > I
> just
> > >> > > > had
> > >> > > not done so before.
> > >> > >
> > >> > > I can help with that -- I've done it before.
> > >> > >
> > >> > > > Is that the preferred route?
> > >> > >
> > >> > > Yes.
> > >> > >
> > >> > > > The mechanics for migrating the trafodion code is for a
> committer
> > >> > > > to push the current code into the newly created repo?
> > >> > > > (When we are ready to pull that switch.)
> > >> > >
> > >> > > I'd suggest NOT involving INFRA in the mechanics of repo
> migration.
> > >> > > At this point it is not simple enough and that will be kind
> > >> > > of
> tough
> > >> > > to communicate to ASF INFRA.
> > >> > >
> > >> > > What I suggest is this: create a brand new staging repo on GH.
> Merge
> > >> > > all the code there. Review the result. And once it looks good
> > >> > > do everybody just do a git push to ASF repo.
> > >> > >
> > >> > > Sounds reasonable?
> > >> > >
> > >> > > Thanks,
> > >> > > Roman.
> >
>
Re: Migrating code to Apache git -- multiple repos
Posted by Stack <st...@duboce.net>.
Thanks Kevin
Any updates?
Am I right in thinking this the (only?) barrier to our being able to move
over the code to apache?
Thanks,
St.Ack
On Fri, May 29, 2015 at 8:55 PM, Deyager, Kevin <ke...@hp.com>
wrote:
> Hi Michael,
>
> I am working the SGA. And yes, things can work a bit slowly in big
> companies...
>
> Kevim
>
> On May 29, 2015 7:51 PM, Stack <st...@duboce.net> wrote:
> HPers!
>
> You'll have to live w/ Steve's reorg going forward. You good w/ the 'mess'
> he's made (smile)?
>
> Before I try build myself, where are the build instructions?
>
> On the software grant, who is on that? This often takes way more time than
> folks would expect.
>
> Thanks,
> St.Ack
>
>
> On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
> > Great progress! I'll definitely take a look Mon/Tue next week!
> >
> > Thanks,
> > Roman.
> >
> > On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> > <st...@hp.com> wrote:
> > > I have pushed more changes to my traf-merged repo.
> > >
> > > * renamed "test" directory to "tests/phx"
> > > * added "wms" component (master branch only, as it has not been
> released)
> > > * added 1.x.x_<component> release tags for applicable components
> > >
> > > I did not bother with the 0.x.x release tags.
> > >
> > > Feedback, please.
> > >
> > > -Steve
> > >
> > >> -----Original Message-----
> > >> From: Varnau, Steve (Trafodion)
> > >> Sent: Thursday, May 28, 2015 15:42
> > >> To: dev@trafodion.incubator.apache.org
> > >> Subject: RE: Migrating code to Apache git -- multiple repos
> > >>
> > >> I have a combined repo on github for folks to take a look at.
> > >>
> > >> https://github.com/svarnau/traf-merged
> > >>
> > >> The full history of all the repos is there for the three release
> > >> branches: master, stable/1.0, stable/1.1
> > >>
> > >> I restructured the various repos into sub-directories for each of the
> > >> three branches. Install has only a master branch, so it does not exist
> > >> in the stable branches.
> > >>
> > >> Next I need to put in some key tags. Since the same release tag names
> > >> were used across repos, combining the repos caused tags to conflict.
> > >> I'll have to re-name them by repo.
> > >>
> > >> -Steve
> > >>
> > >> > -----Original Message-----
> > >> > From: Varnau, Steve (Trafodion)
> > >> > Sent: Wednesday, May 27, 2015 16:52
> > >> > To: dev@trafodion.incubator.apache.org
> > >> > Subject: RE: Migrating code to Apache git -- multiple repos
> > >> >
> > >> > Thanks, guys. You've answered my questions. I'll work up a combined
> > >> > repo structure that we can review.
> > >> >
> > >> > -Steve
> > >> >
> > >> > > -----Original Message-----
> > >> > > From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On
> Behalf
> > >> > > Of Roman Shaposhnik
> > >> > > Sent: Wednesday, May 27, 2015 15:54
> > >> > > To: dev@trafodion.incubator.apache.org
> > >> > > Subject: Re: Migrating code to Apache git -- multiple repos
> > >> > >
> > >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
> > >> > > <st...@hp.com> wrote:
> > >> > > > Sorry, I guess we can merge repos while retaining history. I
> just
> > >> > > > had
> > >> > > not done so before.
> > >> > >
> > >> > > I can help with that -- I've done it before.
> > >> > >
> > >> > > > Is that the preferred route?
> > >> > >
> > >> > > Yes.
> > >> > >
> > >> > > > The mechanics for migrating the trafodion code is for a
> committer
> > >> > > > to push the current code into the newly created repo? (When we
> > >> > > > are ready to pull that switch.)
> > >> > >
> > >> > > I'd suggest NOT involving INFRA in the mechanics of repo
> migration.
> > >> > > At this point it is not simple enough and that will be kind of
> tough
> > >> > > to communicate to ASF INFRA.
> > >> > >
> > >> > > What I suggest is this: create a brand new staging repo on GH.
> Merge
> > >> > > all the code there. Review the result. And once it looks good do
> > >> > > everybody just do a git push to ASF repo.
> > >> > >
> > >> > > Sounds reasonable?
> > >> > >
> > >> > > Thanks,
> > >> > > Roman.
> >
>
Re: Migrating code to Apache git -- multiple repos
Posted by "Deyager, Kevin" <ke...@hp.com>.
Hi Michael,
I am working the SGA. And yes, things can work a bit slowly in big companies...
Kevim
On May 29, 2015 7:51 PM, Stack <st...@duboce.net> wrote:
HPers!
You'll have to live w/ Steve's reorg going forward. You good w/ the 'mess'
he's made (smile)?
Before I try build myself, where are the build instructions?
On the software grant, who is on that? This often takes way more time than
folks would expect.
Thanks,
St.Ack
On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> Great progress! I'll definitely take a look Mon/Tue next week!
>
> Thanks,
> Roman.
>
> On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> <st...@hp.com> wrote:
> > I have pushed more changes to my traf-merged repo.
> >
> > * renamed "test" directory to "tests/phx"
> > * added "wms" component (master branch only, as it has not been released)
> > * added 1.x.x_<component> release tags for applicable components
> >
> > I did not bother with the 0.x.x release tags.
> >
> > Feedback, please.
> >
> > -Steve
> >
> >> -----Original Message-----
> >> From: Varnau, Steve (Trafodion)
> >> Sent: Thursday, May 28, 2015 15:42
> >> To: dev@trafodion.incubator.apache.org
> >> Subject: RE: Migrating code to Apache git -- multiple repos
> >>
> >> I have a combined repo on github for folks to take a look at.
> >>
> >> https://github.com/svarnau/traf-merged
> >>
> >> The full history of all the repos is there for the three release
> >> branches: master, stable/1.0, stable/1.1
> >>
> >> I restructured the various repos into sub-directories for each of the
> >> three branches. Install has only a master branch, so it does not exist
> >> in the stable branches.
> >>
> >> Next I need to put in some key tags. Since the same release tag names
> >> were used across repos, combining the repos caused tags to conflict.
> >> I'll have to re-name them by repo.
> >>
> >> -Steve
> >>
> >> > -----Original Message-----
> >> > From: Varnau, Steve (Trafodion)
> >> > Sent: Wednesday, May 27, 2015 16:52
> >> > To: dev@trafodion.incubator.apache.org
> >> > Subject: RE: Migrating code to Apache git -- multiple repos
> >> >
> >> > Thanks, guys. You've answered my questions. I'll work up a combined
> >> > repo structure that we can review.
> >> >
> >> > -Steve
> >> >
> >> > > -----Original Message-----
> >> > > From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On Behalf
> >> > > Of Roman Shaposhnik
> >> > > Sent: Wednesday, May 27, 2015 15:54
> >> > > To: dev@trafodion.incubator.apache.org
> >> > > Subject: Re: Migrating code to Apache git -- multiple repos
> >> > >
> >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
> >> > > <st...@hp.com> wrote:
> >> > > > Sorry, I guess we can merge repos while retaining history. I just
> >> > > > had
> >> > > not done so before.
> >> > >
> >> > > I can help with that -- I've done it before.
> >> > >
> >> > > > Is that the preferred route?
> >> > >
> >> > > Yes.
> >> > >
> >> > > > The mechanics for migrating the trafodion code is for a committer
> >> > > > to push the current code into the newly created repo? (When we
> >> > > > are ready to pull that switch.)
> >> > >
> >> > > I'd suggest NOT involving INFRA in the mechanics of repo migration.
> >> > > At this point it is not simple enough and that will be kind of tough
> >> > > to communicate to ASF INFRA.
> >> > >
> >> > > What I suggest is this: create a brand new staging repo on GH. Merge
> >> > > all the code there. Review the result. And once it looks good do
> >> > > everybody just do a git push to ASF repo.
> >> > >
> >> > > Sounds reasonable?
> >> > >
> >> > > Thanks,
> >> > > Roman.
>
Re: Migrating code to Apache git -- multiple repos
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Sat, Jun 6, 2015 at 9:51 PM, Stack <st...@duboce.net> wrote:
> Thanks Steve. Looking at src, it all has Apache license stamped on it
> already. Thats good. We'll just flip copyright from hp to Apache after the
> grant is worked out (You might want to try Apache Rat --
> http://creadur.apache.org/rat/ -- on it to see what files it turns up as
> absent the Apache license).
As a matter of fact -- integrating RAT into your build would be a great
way to make sure that whoever reviews your first release has an easy
time doing that. That plus it is also a great way to keep inadvertent
commits that may upset RAT out.
Thanks,
Roman.
Re: Migrating code to Apache git -- multiple repos
Posted by Stack <st...@duboce.net>.
On Sat, May 30, 2015 at 10:50 AM, Varnau, Steve (Trafodion) <
steve.varnau@hp.com> wrote:
>
> https://wiki.trafodion.org/wiki/index.php/Building_the_Software
>
>
Thanks Steve. Looking at src, it all has Apache license stamped on it
already. Thats good. We'll just flip copyright from hp to Apache after the
grant is worked out (You might want to try Apache Rat --
http://creadur.apache.org/rat/ -- on it to see what files it turns up as
absent the Apache license).
Is there any work that could be done now ahead of the grant going through?
Will there be a script at top level to build all Steve or will it be a
module by module? Looking at the merged repo, it looks like it could get
stuff like LICENSE and NOTICE at the top level (
http://www.apache.org/dev/licensing-howto.html) Can work be done on undoing
the LGPL dependencies meantime?
Thanks,
St.Ack
> -Steve
>
> > -----Original Message-----
> > From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of
> > Stack
> > Sent: Friday, May 29, 2015 19:51
> > To: dev@trafodion.incubator.apache.org
> > Subject: Re: Migrating code to Apache git -- multiple repos
> >
> > HPers!
> >
> > You'll have to live w/ Steve's reorg going forward. You good w/ the
> > 'mess'
> > he's made (smile)?
> >
> > Before I try build myself, where are the build instructions?
> >
> > On the software grant, who is on that? This often takes way more time
> > than folks would expect.
> >
> > Thanks,
> > St.Ack
> >
> >
> > On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik <ro...@shaposhnik.org>
> > wrote:
> >
> > > Great progress! I'll definitely take a look Mon/Tue next week!
> > >
> > > Thanks,
> > > Roman.
> > >
> > > On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> > > <st...@hp.com> wrote:
> > > > I have pushed more changes to my traf-merged repo.
> > > >
> > > > * renamed "test" directory to "tests/phx"
> > > > * added "wms" component (master branch only, as it has not been
> > > > released)
> > > > * added 1.x.x_<component> release tags for applicable components
> > > >
> > > > I did not bother with the 0.x.x release tags.
> > > >
> > > > Feedback, please.
> > > >
> > > > -Steve
> > > >
> > > >> -----Original Message-----
> > > >> From: Varnau, Steve (Trafodion)
> > > >> Sent: Thursday, May 28, 2015 15:42
> > > >> To: dev@trafodion.incubator.apache.org
> > > >> Subject: RE: Migrating code to Apache git -- multiple repos
> > > >>
> > > >> I have a combined repo on github for folks to take a look at.
> > > >>
> > > >> https://github.com/svarnau/traf-merged
> > > >>
> > > >> The full history of all the repos is there for the three release
> > > >> branches: master, stable/1.0, stable/1.1
> > > >>
> > > >> I restructured the various repos into sub-directories for each of
> > > >> the three branches. Install has only a master branch, so it does
> > > >> not exist in the stable branches.
> > > >>
> > > >> Next I need to put in some key tags. Since the same release tag
> > > >> names were used across repos, combining the repos caused tags to
> > conflict.
> > > >> I'll have to re-name them by repo.
> > > >>
> > > >> -Steve
> > > >>
> > > >> > -----Original Message-----
> > > >> > From: Varnau, Steve (Trafodion)
> > > >> > Sent: Wednesday, May 27, 2015 16:52
> > > >> > To: dev@trafodion.incubator.apache.org
> > > >> > Subject: RE: Migrating code to Apache git -- multiple repos
> > > >> >
> > > >> > Thanks, guys. You've answered my questions. I'll work up a
> > > >> > combined repo structure that we can review.
> > > >> >
> > > >> > -Steve
> > > >> >
> > > >> > > -----Original Message-----
> > > >> > > From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On
> > > >> > > Behalf Of Roman Shaposhnik
> > > >> > > Sent: Wednesday, May 27, 2015 15:54
> > > >> > > To: dev@trafodion.incubator.apache.org
> > > >> > > Subject: Re: Migrating code to Apache git -- multiple repos
> > > >> > >
> > > >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
> > > >> > > <st...@hp.com> wrote:
> > > >> > > > Sorry, I guess we can merge repos while retaining history. I
> > > >> > > > just had
> > > >> > > not done so before.
> > > >> > >
> > > >> > > I can help with that -- I've done it before.
> > > >> > >
> > > >> > > > Is that the preferred route?
> > > >> > >
> > > >> > > Yes.
> > > >> > >
> > > >> > > > The mechanics for migrating the trafodion code is for a
> > > >> > > > committer to push the current code into the newly created
> > > >> > > > repo? (When we are ready to pull that switch.)
> > > >> > >
> > > >> > > I'd suggest NOT involving INFRA in the mechanics of repo
> > migration.
> > > >> > > At this point it is not simple enough and that will be kind of
> > > >> > > tough to communicate to ASF INFRA.
> > > >> > >
> > > >> > > What I suggest is this: create a brand new staging repo on GH.
> > > >> > > Merge all the code there. Review the result. And once it looks
> > > >> > > good do everybody just do a git push to ASF repo.
> > > >> > >
> > > >> > > Sounds reasonable?
> > > >> > >
> > > >> > > Thanks,
> > > >> > > Roman.
> > >
>
RE: Migrating code to Apache git -- multiple repos
Posted by "Varnau, Steve (Trafodion)" <st...@hp.com>.
https://wiki.trafodion.org/wiki/index.php/Building_the_Software
-Steve
> -----Original Message-----
> From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of
> Stack
> Sent: Friday, May 29, 2015 19:51
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Migrating code to Apache git -- multiple repos
>
> HPers!
>
> You'll have to live w/ Steve's reorg going forward. You good w/ the
> 'mess'
> he's made (smile)?
>
> Before I try build myself, where are the build instructions?
>
> On the software grant, who is on that? This often takes way more time
> than folks would expect.
>
> Thanks,
> St.Ack
>
>
> On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
> > Great progress! I'll definitely take a look Mon/Tue next week!
> >
> > Thanks,
> > Roman.
> >
> > On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> > <st...@hp.com> wrote:
> > > I have pushed more changes to my traf-merged repo.
> > >
> > > * renamed "test" directory to "tests/phx"
> > > * added "wms" component (master branch only, as it has not been
> > > released)
> > > * added 1.x.x_<component> release tags for applicable components
> > >
> > > I did not bother with the 0.x.x release tags.
> > >
> > > Feedback, please.
> > >
> > > -Steve
> > >
> > >> -----Original Message-----
> > >> From: Varnau, Steve (Trafodion)
> > >> Sent: Thursday, May 28, 2015 15:42
> > >> To: dev@trafodion.incubator.apache.org
> > >> Subject: RE: Migrating code to Apache git -- multiple repos
> > >>
> > >> I have a combined repo on github for folks to take a look at.
> > >>
> > >> https://github.com/svarnau/traf-merged
> > >>
> > >> The full history of all the repos is there for the three release
> > >> branches: master, stable/1.0, stable/1.1
> > >>
> > >> I restructured the various repos into sub-directories for each of
> > >> the three branches. Install has only a master branch, so it does
> > >> not exist in the stable branches.
> > >>
> > >> Next I need to put in some key tags. Since the same release tag
> > >> names were used across repos, combining the repos caused tags to
> conflict.
> > >> I'll have to re-name them by repo.
> > >>
> > >> -Steve
> > >>
> > >> > -----Original Message-----
> > >> > From: Varnau, Steve (Trafodion)
> > >> > Sent: Wednesday, May 27, 2015 16:52
> > >> > To: dev@trafodion.incubator.apache.org
> > >> > Subject: RE: Migrating code to Apache git -- multiple repos
> > >> >
> > >> > Thanks, guys. You've answered my questions. I'll work up a
> > >> > combined repo structure that we can review.
> > >> >
> > >> > -Steve
> > >> >
> > >> > > -----Original Message-----
> > >> > > From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On
> > >> > > Behalf Of Roman Shaposhnik
> > >> > > Sent: Wednesday, May 27, 2015 15:54
> > >> > > To: dev@trafodion.incubator.apache.org
> > >> > > Subject: Re: Migrating code to Apache git -- multiple repos
> > >> > >
> > >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
> > >> > > <st...@hp.com> wrote:
> > >> > > > Sorry, I guess we can merge repos while retaining history. I
> > >> > > > just had
> > >> > > not done so before.
> > >> > >
> > >> > > I can help with that -- I've done it before.
> > >> > >
> > >> > > > Is that the preferred route?
> > >> > >
> > >> > > Yes.
> > >> > >
> > >> > > > The mechanics for migrating the trafodion code is for a
> > >> > > > committer to push the current code into the newly created
> > >> > > > repo? (When we are ready to pull that switch.)
> > >> > >
> > >> > > I'd suggest NOT involving INFRA in the mechanics of repo
> migration.
> > >> > > At this point it is not simple enough and that will be kind of
> > >> > > tough to communicate to ASF INFRA.
> > >> > >
> > >> > > What I suggest is this: create a brand new staging repo on GH.
> > >> > > Merge all the code there. Review the result. And once it looks
> > >> > > good do everybody just do a git push to ASF repo.
> > >> > >
> > >> > > Sounds reasonable?
> > >> > >
> > >> > > Thanks,
> > >> > > Roman.
> >
Re: Migrating code to Apache git -- multiple repos
Posted by Stack <st...@duboce.net>.
HPers!
You'll have to live w/ Steve's reorg going forward. You good w/ the 'mess'
he's made (smile)?
Before I try build myself, where are the build instructions?
On the software grant, who is on that? This often takes way more time than
folks would expect.
Thanks,
St.Ack
On Fri, May 29, 2015 at 7:05 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> Great progress! I'll definitely take a look Mon/Tue next week!
>
> Thanks,
> Roman.
>
> On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
> <st...@hp.com> wrote:
> > I have pushed more changes to my traf-merged repo.
> >
> > * renamed "test" directory to "tests/phx"
> > * added "wms" component (master branch only, as it has not been released)
> > * added 1.x.x_<component> release tags for applicable components
> >
> > I did not bother with the 0.x.x release tags.
> >
> > Feedback, please.
> >
> > -Steve
> >
> >> -----Original Message-----
> >> From: Varnau, Steve (Trafodion)
> >> Sent: Thursday, May 28, 2015 15:42
> >> To: dev@trafodion.incubator.apache.org
> >> Subject: RE: Migrating code to Apache git -- multiple repos
> >>
> >> I have a combined repo on github for folks to take a look at.
> >>
> >> https://github.com/svarnau/traf-merged
> >>
> >> The full history of all the repos is there for the three release
> >> branches: master, stable/1.0, stable/1.1
> >>
> >> I restructured the various repos into sub-directories for each of the
> >> three branches. Install has only a master branch, so it does not exist
> >> in the stable branches.
> >>
> >> Next I need to put in some key tags. Since the same release tag names
> >> were used across repos, combining the repos caused tags to conflict.
> >> I'll have to re-name them by repo.
> >>
> >> -Steve
> >>
> >> > -----Original Message-----
> >> > From: Varnau, Steve (Trafodion)
> >> > Sent: Wednesday, May 27, 2015 16:52
> >> > To: dev@trafodion.incubator.apache.org
> >> > Subject: RE: Migrating code to Apache git -- multiple repos
> >> >
> >> > Thanks, guys. You've answered my questions. I'll work up a combined
> >> > repo structure that we can review.
> >> >
> >> > -Steve
> >> >
> >> > > -----Original Message-----
> >> > > From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On Behalf
> >> > > Of Roman Shaposhnik
> >> > > Sent: Wednesday, May 27, 2015 15:54
> >> > > To: dev@trafodion.incubator.apache.org
> >> > > Subject: Re: Migrating code to Apache git -- multiple repos
> >> > >
> >> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
> >> > > <st...@hp.com> wrote:
> >> > > > Sorry, I guess we can merge repos while retaining history. I just
> >> > > > had
> >> > > not done so before.
> >> > >
> >> > > I can help with that -- I've done it before.
> >> > >
> >> > > > Is that the preferred route?
> >> > >
> >> > > Yes.
> >> > >
> >> > > > The mechanics for migrating the trafodion code is for a committer
> >> > > > to push the current code into the newly created repo? (When we
> >> > > > are ready to pull that switch.)
> >> > >
> >> > > I'd suggest NOT involving INFRA in the mechanics of repo migration.
> >> > > At this point it is not simple enough and that will be kind of tough
> >> > > to communicate to ASF INFRA.
> >> > >
> >> > > What I suggest is this: create a brand new staging repo on GH. Merge
> >> > > all the code there. Review the result. And once it looks good do
> >> > > everybody just do a git push to ASF repo.
> >> > >
> >> > > Sounds reasonable?
> >> > >
> >> > > Thanks,
> >> > > Roman.
>
Re: Migrating code to Apache git -- multiple repos
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
Great progress! I'll definitely take a look Mon/Tue next week!
Thanks,
Roman.
On Fri, May 29, 2015 at 6:04 PM, Varnau, Steve (Trafodion)
<st...@hp.com> wrote:
> I have pushed more changes to my traf-merged repo.
>
> * renamed "test" directory to "tests/phx"
> * added "wms" component (master branch only, as it has not been released)
> * added 1.x.x_<component> release tags for applicable components
>
> I did not bother with the 0.x.x release tags.
>
> Feedback, please.
>
> -Steve
>
>> -----Original Message-----
>> From: Varnau, Steve (Trafodion)
>> Sent: Thursday, May 28, 2015 15:42
>> To: dev@trafodion.incubator.apache.org
>> Subject: RE: Migrating code to Apache git -- multiple repos
>>
>> I have a combined repo on github for folks to take a look at.
>>
>> https://github.com/svarnau/traf-merged
>>
>> The full history of all the repos is there for the three release
>> branches: master, stable/1.0, stable/1.1
>>
>> I restructured the various repos into sub-directories for each of the
>> three branches. Install has only a master branch, so it does not exist
>> in the stable branches.
>>
>> Next I need to put in some key tags. Since the same release tag names
>> were used across repos, combining the repos caused tags to conflict.
>> I'll have to re-name them by repo.
>>
>> -Steve
>>
>> > -----Original Message-----
>> > From: Varnau, Steve (Trafodion)
>> > Sent: Wednesday, May 27, 2015 16:52
>> > To: dev@trafodion.incubator.apache.org
>> > Subject: RE: Migrating code to Apache git -- multiple repos
>> >
>> > Thanks, guys. You've answered my questions. I'll work up a combined
>> > repo structure that we can review.
>> >
>> > -Steve
>> >
>> > > -----Original Message-----
>> > > From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On Behalf
>> > > Of Roman Shaposhnik
>> > > Sent: Wednesday, May 27, 2015 15:54
>> > > To: dev@trafodion.incubator.apache.org
>> > > Subject: Re: Migrating code to Apache git -- multiple repos
>> > >
>> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
>> > > <st...@hp.com> wrote:
>> > > > Sorry, I guess we can merge repos while retaining history. I just
>> > > > had
>> > > not done so before.
>> > >
>> > > I can help with that -- I've done it before.
>> > >
>> > > > Is that the preferred route?
>> > >
>> > > Yes.
>> > >
>> > > > The mechanics for migrating the trafodion code is for a committer
>> > > > to push the current code into the newly created repo? (When we
>> > > > are ready to pull that switch.)
>> > >
>> > > I'd suggest NOT involving INFRA in the mechanics of repo migration.
>> > > At this point it is not simple enough and that will be kind of tough
>> > > to communicate to ASF INFRA.
>> > >
>> > > What I suggest is this: create a brand new staging repo on GH. Merge
>> > > all the code there. Review the result. And once it looks good do
>> > > everybody just do a git push to ASF repo.
>> > >
>> > > Sounds reasonable?
>> > >
>> > > Thanks,
>> > > Roman.
RE: Migrating code to Apache git -- multiple repos
Posted by "Varnau, Steve (Trafodion)" <st...@hp.com>.
I have pushed more changes to my traf-merged repo.
* renamed "test" directory to "tests/phx"
* added "wms" component (master branch only, as it has not been released)
* added 1.x.x_<component> release tags for applicable components
I did not bother with the 0.x.x release tags.
Feedback, please.
-Steve
> -----Original Message-----
> From: Varnau, Steve (Trafodion)
> Sent: Thursday, May 28, 2015 15:42
> To: dev@trafodion.incubator.apache.org
> Subject: RE: Migrating code to Apache git -- multiple repos
>
> I have a combined repo on github for folks to take a look at.
>
> https://github.com/svarnau/traf-merged
>
> The full history of all the repos is there for the three release
> branches: master, stable/1.0, stable/1.1
>
> I restructured the various repos into sub-directories for each of the
> three branches. Install has only a master branch, so it does not exist
> in the stable branches.
>
> Next I need to put in some key tags. Since the same release tag names
> were used across repos, combining the repos caused tags to conflict.
> I'll have to re-name them by repo.
>
> -Steve
>
> > -----Original Message-----
> > From: Varnau, Steve (Trafodion)
> > Sent: Wednesday, May 27, 2015 16:52
> > To: dev@trafodion.incubator.apache.org
> > Subject: RE: Migrating code to Apache git -- multiple repos
> >
> > Thanks, guys. You've answered my questions. I'll work up a combined
> > repo structure that we can review.
> >
> > -Steve
> >
> > > -----Original Message-----
> > > From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On Behalf
> > > Of Roman Shaposhnik
> > > Sent: Wednesday, May 27, 2015 15:54
> > > To: dev@trafodion.incubator.apache.org
> > > Subject: Re: Migrating code to Apache git -- multiple repos
> > >
> > > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
> > > <st...@hp.com> wrote:
> > > > Sorry, I guess we can merge repos while retaining history. I just
> > > > had
> > > not done so before.
> > >
> > > I can help with that -- I've done it before.
> > >
> > > > Is that the preferred route?
> > >
> > > Yes.
> > >
> > > > The mechanics for migrating the trafodion code is for a committer
> > > > to push the current code into the newly created repo? (When we
> > > > are ready to pull that switch.)
> > >
> > > I'd suggest NOT involving INFRA in the mechanics of repo migration.
> > > At this point it is not simple enough and that will be kind of tough
> > > to communicate to ASF INFRA.
> > >
> > > What I suggest is this: create a brand new staging repo on GH. Merge
> > > all the code there. Review the result. And once it looks good do
> > > everybody just do a git push to ASF repo.
> > >
> > > Sounds reasonable?
> > >
> > > Thanks,
> > > Roman.
RE: Migrating code to Apache git -- multiple repos
Posted by "Varnau, Steve (Trafodion)" <st...@hp.com>.
I have a combined repo on github for folks to take a look at.
https://github.com/svarnau/traf-merged
The full history of all the repos is there for the three release branches: master, stable/1.0, stable/1.1
I restructured the various repos into sub-directories for each of the three branches. Install has only a master branch, so it does not exist in the stable branches.
Next I need to put in some key tags. Since the same release tag names were used across repos, combining the repos caused tags to conflict. I'll have to re-name them by repo.
-Steve
> -----Original Message-----
> From: Varnau, Steve (Trafodion)
> Sent: Wednesday, May 27, 2015 16:52
> To: dev@trafodion.incubator.apache.org
> Subject: RE: Migrating code to Apache git -- multiple repos
>
> Thanks, guys. You've answered my questions. I'll work up a combined repo
> structure that we can review.
>
> -Steve
>
> > -----Original Message-----
> > From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On Behalf Of
> > Roman Shaposhnik
> > Sent: Wednesday, May 27, 2015 15:54
> > To: dev@trafodion.incubator.apache.org
> > Subject: Re: Migrating code to Apache git -- multiple repos
> >
> > On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
> > <st...@hp.com> wrote:
> > > Sorry, I guess we can merge repos while retaining history. I just
> > > had
> > not done so before.
> >
> > I can help with that -- I've done it before.
> >
> > > Is that the preferred route?
> >
> > Yes.
> >
> > > The mechanics for migrating the trafodion code is for a committer to
> > > push the current code into the newly created repo? (When we are
> > > ready to pull that switch.)
> >
> > I'd suggest NOT involving INFRA in the mechanics of repo migration. At
> > this point it is not simple enough and that will be kind of tough to
> > communicate to ASF INFRA.
> >
> > What I suggest is this: create a brand new staging repo on GH. Merge
> > all the code there. Review the result. And once it looks good do
> > everybody just do a git push to ASF repo.
> >
> > Sounds reasonable?
> >
> > Thanks,
> > Roman.
RE: Migrating code to Apache git -- multiple repos
Posted by "Varnau, Steve (Trafodion)" <st...@hp.com>.
Thanks, guys. You've answered my questions. I'll work up a combined repo structure that we can review.
-Steve
> -----Original Message-----
> From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On Behalf Of
> Roman Shaposhnik
> Sent: Wednesday, May 27, 2015 15:54
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Migrating code to Apache git -- multiple repos
>
> On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
> <st...@hp.com> wrote:
> > Sorry, I guess we can merge repos while retaining history. I just had
> not done so before.
>
> I can help with that -- I've done it before.
>
> > Is that the preferred route?
>
> Yes.
>
> > The mechanics for migrating the trafodion code is for a committer to
> > push the current code into the newly created repo? (When we are ready
> > to pull that switch.)
>
> I'd suggest NOT involving INFRA in the mechanics of repo migration. At
> this point it is not simple enough and that will be kind of tough to
> communicate to ASF INFRA.
>
> What I suggest is this: create a brand new staging repo on GH. Merge all
> the code there. Review the result. And once it looks good do everybody
> just do a git push to ASF repo.
>
> Sounds reasonable?
>
> Thanks,
> Roman.
Re: Migrating code to Apache git -- multiple repos
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion)
<st...@hp.com> wrote:
> Sorry, I guess we can merge repos while retaining history. I just had not done so before.
I can help with that -- I've done it before.
> Is that the preferred route?
Yes.
> The mechanics for migrating the trafodion code is for a committer to push the current code
> into the newly created repo? (When we are ready to pull that switch.)
I'd suggest NOT involving INFRA in the mechanics of repo migration. At
this point
it is not simple enough and that will be kind of tough to communicate to ASF
INFRA.
What I suggest is this: create a brand new staging repo on GH. Merge
all the code
there. Review the result. And once it looks good do everybody just do a git push
to ASF repo.
Sounds reasonable?
Thanks,
Roman.
Re: Migrating code to Apache git -- multiple repos
Posted by Stack <st...@duboce.net>.
On Wed, May 27, 2015 at 2:59 PM, Varnau, Steve (Trafodion) <
steve.varnau@hp.com> wrote:
> Sorry, I guess we can merge repos while retaining history. I just had not
> done so before.
>
> Is that the preferred route?
>
>
Generally one project, one repo, yeah.
> The mechanics for migrating the trafodion code is for a committer to push
> the current code into the newly created repo? (When we are ready to pull
> that switch.)
>
>
I asked for a bare repo. We can go back to INFRA and ask if they can do an
import from current location preserving history. We can diagram how we want
the layout.
What is in the way of the import?
We could import with the LGPL log4cpp and unixodbc dependency for now and
then address replacing tout de suite. Ditto on move from proprietary
docbook to asciidoc.
I believe we need to do a software grant to Apache. See here:
http://incubator.apache.org/guides/mentor.html#initial-ip-clearance How you
folks going to assert you own the software? And then, how to grant it to
Apache?
Thanks,
St.Ack
> -Steve
>
> > -----Original Message-----
> > From: Varnau, Steve (Trafodion)
> > Sent: Wednesday, May 27, 2015 14:26
> > To: dev@trafodion.incubator.apache.org
> > Subject: RE: Migrating code to Apache git -- multiple repos
> >
> > In practice, these pieces were built/packaged somewhat separately, but
> > tested together. The developers generally had areas of focus, so
> > several people worked primarily on DCS, a couple on install, and the
> > majority on various parts of "core". But the permissions were such that
> > they were not restricted to those areas.
> >
> > The releases of core and DCS were always tied together, but installer
> > was released more frequently. The installer also had a single branch,
> > with the latest version supporting installation of multiple trafodion
> > versions.
> >
> > I don't think separate repos are "required", but they have been
> > developed this way for the past year. So, to preserve that history, we'd
> > need to continue that I think. I guess I was assuming that we are
> > preserving history.
> >
> > I actually forgot one more repo (trafodion/win-odbc), which is a windows
> > ODBC driver. Its change history is very small compared to the others,
> > but it was released along with core and DCS.
> >
> > -Steve
> >
> > > -----Original Message-----
> > > From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On Behalf Of
> > > Roman Shaposhnik
> > > Sent: Wednesday, May 27, 2015 12:34
> > > To: dev@trafodion.incubator.apache.org
> > > Subject: Re: Migrating code to Apache git -- multiple repos
> > >
> > > I'd like to understand better why separate repos are required.
> > > Are these code bases being developed asynchronously with different
> > > release schedules, etc.
> > >
> > > Most important of all I'd like to understand the overlap of developer
> > > communities around these sub-projects. Things like if I'm a committer
> > > on core does it mean I am a committer on phoenix_test and vs.
> > >
> > > Thanks,
> > > Roman.
> > >
> > > On Wed, May 27, 2015 at 12:09 PM, Varnau, Steve (Trafodion)
> > > <st...@hp.com> wrote:
> > > > Mentors,
> > > >
> > > > I'm looking for some guidance on source code set-up.
> > > >
> > > > We currently use several git repos for trafodion
> > > (https://github.com/trafodion):
> > > > trafodion/core - bulk of product code, tests, etc
> > > > trafodion/dcs - product and test code for connectivity
> > > services
> > > > trafodion/install - installation scripts
> > > > trafodion/phoenix_test - test suite adapted from
> > > > apache/phoenix customized to trafodion
> > > >
> > > > Our initial incubation repo set up is at:
> > > > https://git-wip-us.apache.org/repos/asf/incubator-trafodion.git
> > > >
> > > > Assuming the trafodion/core history will go into
> > > > incubator-trafodion,
> > > do we also need additional repos?
> > > > Perhaps:
> > > > incubator-trafodion-dcs
> > > > incubator-trafodion-install
> > > > incubator-trafodion-test
> > > >
> > > > -Steve
> > > >
> > > >
> > > >
>
RE: Migrating code to Apache git -- multiple repos
Posted by "Varnau, Steve (Trafodion)" <st...@hp.com>.
Sorry, I guess we can merge repos while retaining history. I just had not done so before.
Is that the preferred route?
The mechanics for migrating the trafodion code is for a committer to push the current code into the newly created repo? (When we are ready to pull that switch.)
-Steve
> -----Original Message-----
> From: Varnau, Steve (Trafodion)
> Sent: Wednesday, May 27, 2015 14:26
> To: dev@trafodion.incubator.apache.org
> Subject: RE: Migrating code to Apache git -- multiple repos
>
> In practice, these pieces were built/packaged somewhat separately, but
> tested together. The developers generally had areas of focus, so
> several people worked primarily on DCS, a couple on install, and the
> majority on various parts of "core". But the permissions were such that
> they were not restricted to those areas.
>
> The releases of core and DCS were always tied together, but installer
> was released more frequently. The installer also had a single branch,
> with the latest version supporting installation of multiple trafodion
> versions.
>
> I don't think separate repos are "required", but they have been
> developed this way for the past year. So, to preserve that history, we'd
> need to continue that I think. I guess I was assuming that we are
> preserving history.
>
> I actually forgot one more repo (trafodion/win-odbc), which is a windows
> ODBC driver. Its change history is very small compared to the others,
> but it was released along with core and DCS.
>
> -Steve
>
> > -----Original Message-----
> > From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On Behalf Of
> > Roman Shaposhnik
> > Sent: Wednesday, May 27, 2015 12:34
> > To: dev@trafodion.incubator.apache.org
> > Subject: Re: Migrating code to Apache git -- multiple repos
> >
> > I'd like to understand better why separate repos are required.
> > Are these code bases being developed asynchronously with different
> > release schedules, etc.
> >
> > Most important of all I'd like to understand the overlap of developer
> > communities around these sub-projects. Things like if I'm a committer
> > on core does it mean I am a committer on phoenix_test and vs.
> >
> > Thanks,
> > Roman.
> >
> > On Wed, May 27, 2015 at 12:09 PM, Varnau, Steve (Trafodion)
> > <st...@hp.com> wrote:
> > > Mentors,
> > >
> > > I'm looking for some guidance on source code set-up.
> > >
> > > We currently use several git repos for trafodion
> > (https://github.com/trafodion):
> > > trafodion/core - bulk of product code, tests, etc
> > > trafodion/dcs - product and test code for connectivity
> > services
> > > trafodion/install - installation scripts
> > > trafodion/phoenix_test - test suite adapted from
> > > apache/phoenix customized to trafodion
> > >
> > > Our initial incubation repo set up is at:
> > > https://git-wip-us.apache.org/repos/asf/incubator-trafodion.git
> > >
> > > Assuming the trafodion/core history will go into
> > > incubator-trafodion,
> > do we also need additional repos?
> > > Perhaps:
> > > incubator-trafodion-dcs
> > > incubator-trafodion-install
> > > incubator-trafodion-test
> > >
> > > -Steve
> > >
> > >
> > >
RE: Migrating code to Apache git -- multiple repos
Posted by "Varnau, Steve (Trafodion)" <st...@hp.com>.
In practice, these pieces were built/packaged somewhat separately, but tested together. The developers generally had areas of focus, so several people worked primarily on DCS, a couple on install, and the majority on various parts of "core". But the permissions were such that they were not restricted to those areas.
The releases of core and DCS were always tied together, but installer was released more frequently. The installer also had a single branch, with the latest version supporting installation of multiple trafodion versions.
I don't think separate repos are "required", but they have been developed this way for the past year. So, to preserve that history, we'd need to continue that I think. I guess I was assuming that we are preserving history.
I actually forgot one more repo (trafodion/win-odbc), which is a windows ODBC driver. Its change history is very small compared to the others, but it was released along with core and DCS.
-Steve
> -----Original Message-----
> From: shaposhnik@gmail.com [mailto:shaposhnik@gmail.com] On Behalf Of
> Roman Shaposhnik
> Sent: Wednesday, May 27, 2015 12:34
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Migrating code to Apache git -- multiple repos
>
> I'd like to understand better why separate repos are required.
> Are these code bases being developed asynchronously with different
> release schedules, etc.
>
> Most important of all I'd like to understand the overlap of developer
> communities around these sub-projects. Things like if I'm a committer on
> core does it mean I am a committer on phoenix_test and vs.
>
> Thanks,
> Roman.
>
> On Wed, May 27, 2015 at 12:09 PM, Varnau, Steve (Trafodion)
> <st...@hp.com> wrote:
> > Mentors,
> >
> > I'm looking for some guidance on source code set-up.
> >
> > We currently use several git repos for trafodion
> (https://github.com/trafodion):
> > trafodion/core - bulk of product code, tests, etc
> > trafodion/dcs - product and test code for connectivity
> services
> > trafodion/install - installation scripts
> > trafodion/phoenix_test - test suite adapted from
> > apache/phoenix customized to trafodion
> >
> > Our initial incubation repo set up is at:
> > https://git-wip-us.apache.org/repos/asf/incubator-trafodion.git
> >
> > Assuming the trafodion/core history will go into incubator-trafodion,
> do we also need additional repos?
> > Perhaps:
> > incubator-trafodion-dcs
> > incubator-trafodion-install
> > incubator-trafodion-test
> >
> > -Steve
> >
> >
> >
Re: Migrating code to Apache git -- multiple repos
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
I'd like to understand better why separate repos are required.
Are these code bases being developed asynchronously with
different release schedules, etc.
Most important of all I'd like to understand the overlap of developer
communities around these sub-projects. Things like if I'm a committer
on core does it mean I am a committer on phoenix_test and vs.
Thanks,
Roman.
On Wed, May 27, 2015 at 12:09 PM, Varnau, Steve (Trafodion)
<st...@hp.com> wrote:
> Mentors,
>
> I'm looking for some guidance on source code set-up.
>
> We currently use several git repos for trafodion (https://github.com/trafodion):
> trafodion/core - bulk of product code, tests, etc
> trafodion/dcs - product and test code for connectivity services
> trafodion/install - installation scripts
> trafodion/phoenix_test - test suite adapted from apache/phoenix customized to trafodion
>
> Our initial incubation repo set up is at: https://git-wip-us.apache.org/repos/asf/incubator-trafodion.git
>
> Assuming the trafodion/core history will go into incubator-trafodion, do we also need additional repos?
> Perhaps:
> incubator-trafodion-dcs
> incubator-trafodion-install
> incubator-trafodion-test
>
> -Steve
>
>
>