[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rap-dev] Git migration starting

The git repositories have been created and look ok [1]. We have one
repository for RAP itself [2] and one for the tools [3]. At some
points the migration tool created an "interesting" structure to
maintain the history. I fixed this where it was obvious and easy to
correct, some remaining places are funny but harmless. All .cvsignore
files have been removed and .gitignore files have been added as

I think we can consider the migration successful and carefully start
using the git repositories. Please have a look at the repositories
soon and check if you can spot any potential problems. Since we're
approaching RC1, we won't make large commits anyway and have some time
to adjust and find a suitable workflow.

Some obsolete bundles have not been migrated. We will create an
"obsolete" repository, just to have those contents available in the
unlikely case some of this stuff is ever needed again when nobody can
remember how to access a CVS repository ;-)

The CVS has already been switched to read-only mode. Next week we will
adjust our builds to checkout from git, update the website etc.

Happy that we did it :)

[1] http://wiki.eclipse.org/RAP/Git
[2] http://git.eclipse.org/c/rap/org.eclipse.rap.git/
[3] http://git.eclipse.org/c/rap/org.eclipse.rap.tools.git/

On Fri, May 11, 2012 at 8:21 AM, Markus Knauer
<mknauer@xxxxxxxxxxxxxxxxx> wrote:
> Last minute reminder... if you have any changes on your disk but not yet in
> CVS, *now* would be the time to synchronize, otherwise it has to wait until
> we migrated the code to Git.
> I'll take the CVS snapshot in about an hour from now and I hope that Ralf
> and I can finish the migration today.
> Thanks,
> Markus
> On Thu, May 10, 2012 at 2:25 PM, Ralf Sternberg
> <rsternberg@xxxxxxxxxxxxxxxxx> wrote:
>> Hi RAP committers,
>> after the successful migration of the RAP Incubator, tomorrow Markus
>> and I will start with the migration of RAP itself [1]. Therefore we'd
>> like to ask you not to make any commits to CVS anymore from tomorrow
>> on. If all goes well, we'll be on Git by Monday evening.
>> We're going to create two repositories for the runtime and the tooling
>> [2]. Inspired by this tweet [3] I'd propose to name the repository
>> "o.e.rap.tools" instead of "o.e.rap.tooling" and to rename the tooling
>> feature to tools as well in 2.0. Even though the term "tooling" is
>> commonly used in the Eclipse community, it's jargon and I think
>> "tools" is a more suitable name for the component. If you have a
>> comment on this, please reply to this suggestion on [2].
>> This brings up the question how the runtime repository should be
>> named. Is "runtime" still a suitable name for "RAP itself", or does it
>> stand for the complete stack, including Equinox etc.? How about naming
>> the repository simply "org.eclipse.rap"? Let's discuss this on [1].
>> Sorry for bringing this up so late, it just came to my mind when I saw
>> Wayne's rant ;-)
>> Regards, Ralf
>> [1] 331780: Migrate RAP from CVS to Git
>> Â Âhttps://bugs.eclipse.org/bugs/show_bug.cgi?id=331780
>> [2] 376696: Migrate RAP Tooling to a separate Git repository?
>> Â Âhttps://bugs.eclipse.org/bugs/show_bug.cgi?id=376696
>> [3] https://twitter.com/#!/waynebeaton/status/199531054070120448
>> _______________________________________________
>> rap-dev mailing list
>> rap-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/rap-dev
> _______________________________________________
> rap-dev mailing list
> rap-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/rap-dev