On Wed, Aug 12, 2009 at 04:02, Hugo Garcia<hugo [dot] a [dot] garcia [..] ...> wrote:
> On Tue, Aug 11, 2009 at 11:02 AM, Hugo Garcia<hugo [dot] a [dot] garcia [..] ...> wrote:
>> Hi
>>
>> I am ready to start figuring out RTT. I am in doubt if I should just
>> download the latest distribution and start from there OR if I should
>> check out the everything from SVN repository?

svn trunk is had a big change in the build system but seems to work, otherwise,
use the branches/rtt-1.8 for getting the latest 'stable' fixes.

I plan to release rtt 1.8.5 and ocl 1.8.2 with the latest known fixes.
Shortly after
RTT 1.10.0 and OCL 1.10.0 come out.

>>
>> -H
>>
>
> I found the following page on the wiki where it seems it is time to learn GIT:
>
> http://orocos.org/forum/rtt/rtt-dev/commits-svn-trunk-oclrtt-limited
>
> Although I like the idea of providing SVN as read-only in order to
> facilitate getting the latest source release quickly and effortlessly
> (at least for someone who has worked with subversion for years). In
> addition, at least as for Eclipse, the subversion plugins are more
> mature as compared to the EGit project which just started as an
> incubation project.
>
> What is the transition plan?

The modus operandi is that I integrate everything in my git repository
first and then selectively push patches to svn. The 1.x releases are
still made from the SVN branches.

>
> To GIT or not to GIT... that is the question.

I'm only maintaining SVN for the RTT/OCL 1.x branch. The 2.x branch is
git only, someone else needs to setup svn if he/she wants to do the
trouble.
I regret that git integration is not as mature as svn integration in
eclipse, but svn truely sucks once you're used to git.

Peter