trafodion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varnau, Steve (Trafodion)" <steve.var...@hp.com>
Subject RE: Migrating code to Apache git -- multiple repos
Date Wed, 27 May 2015 21:59:22 GMT
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)
> > <steve.varnau@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
> > >
> > >
> > >
Mime
View raw message