Re: Migrating code to Apache git -- multiple repos

[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

[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.