[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tm-dev] Git migration update

Anna --

This is the question we are wrestling with. We will absolutely require the ability to do legacy builds for several years yet. If we move entirely to git, do we destroy this ability?

-- David Dykstal,  Architect - Rational Developer for Power Systems

From:        Anna Dushistova <anna.dushistova@xxxxxxxxx>
To:        tm-dev <tm-dev@xxxxxxxxxxx>,
Date:        08/22/2012 09:40 AM
Subject:        Re: [tm-dev] Git migration update
Sent by:        tm-dev-bounces@xxxxxxxxxxx

I have one more specific question: are the TM legacy builds still needed?
Will we have to build 3.2.x in the future?


On Wed, Aug 22, 2012 at 1:50 AM, Anna Dushistova
<anna.dushistova@xxxxxxxxx> wrote:
> Dear committers,
> I am going to request our project migration with the webmaster.
> We plan to have one repository, org.eclipse.tm.git for now with the
> following structure:
> org.eclipse.tm.git-> rse
>                            |
>                              discovery
>                            |
>                              terminal
>                            |
>                              wince
>                            |
>                              releng
> I would like to move releng out of org.eclipse.tm.rse where it resides
> now into a separate module;
> we are going to drop thirdparty from org.eclipse.tm.core since all the
> bundles are moved to Orbit.
> I would also like us to import all the history, that is migrate our
> project completely.
> My preference would be to start the process as soon as possible. If
> you have any concerns, please,
> bring them up now.
> Thanks!
> Anna.
tm-dev mailing list