Re: On Rock's master/next/stable and orocos-toolchain's master/stable

On Wed, May 15, 2013 at 10:34 AM, Sylvain Joyeux <[email protected]>wrote:

> I discussed a while back with Peter the possibility that the toolchain
> development, which is currently done primarily on Rock repositories,
> would actually be done on the orocos toolchain's repositories.
>
> While there is no problem for Rock's master and next flavors (master is
> current dev and next is not used by the orocos toolchain), I fear that
> it becomes more problematic for stable, since rock and orocos-toolchain
> do not have synchronized release plans. I.e., stable would be updated
> from master "out-of-sync".
>
> I don't really know what is the best/more practical option there ...
> Suggestions ?
>

I think we can merge both without disturbing 99% of the users. I think this
is a reasonable estimate of the current usage patterns:

Users using Orocos Toolchain
- master: few, mainly for having specific feature branch
- stable: fewer, I never got complaints for not updating this branch and
never had reports of users using this branch
- toolchain-2.X : most used, also due to the bootstrap scripts using this
- fuerte/groovy/... : used by the ROS build system

So if we drop current stable and use rock's stable+semantics instead, I
think it will actually be an improvement.

The only thing we'd need to take care of is then is when to do a '+1'
version and if this does not break users using 'stable'.

Peter

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