Re: What's going on with versionning ?

Hi Willy,

On Thu, Feb 19, 2015 at 4:30 PM, Willy Lambert <[email protected]> wrote:
> Hi all,
>
> I just saw a reference to toolchain-2.8 branch in another discussion on the
> ML, could someone explain what's going on  ?

Maybe everybody was looking at me...

>
> The 2.7 version seem to have had hard time with multiple "rc". Is this a way
> to go out of a dead end ?

2.7 was only released as Debian packages in the ROS repositories,
currently at 2.7.0-9.
I must admit I also can't find these version tags on github, where
they should be.

The lack of announcements of these releases on the mailing lists is
clearly very confusing. The reason for this is
that the release procedure (but also the review of branches/patches) I
could do until 2.6 is
not working anymore for me. From a timing/effort perspective.

> I'm also interested in the ROS/Orocos version compatibility change. As far
> as I know 2.7 was compatible with Ros::Indigo.

It is, if you build from source. If you want to use the ROS .deb
binaries, you're limited to what is
in the ros repositories:

fuerte : toolchain-2.6
hydro : toolchain-2.7
indigo : toolchain-2.8

So we only create binaries for one Orocos major version per ROS release.

toolchain-2.8 branched from master last year, but afaikt it's still in
sync with master.

The majority of the changes of 2.7 vs  2.8 are on the 'extensions'
level, so not API's but extra
functionality. On the ROS extension side, lots of support was added to
be compatible with
the ROS primitives (so access/modify Orocos primitives using ROS
tools). On the orogen
side, lot of work was done to get the masters of orocos-toolchain back
in sync with the masters
of rock. That's also a major step forward.

2.8 and 2.7 are not binary compatible, but are source-level compatible.

Finally, we discussed a few weeks ago to create release notes for this
2.8 release,
and properly tag it, since we all agree that before it was better. But
I need more than a
few hours to prepare that the 'old way'. Many hours passed since, and
there always seems
to be a higher priority task in front of it.

Peter
-- 
Orocos-Dev mailing list
[email protected]
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev