The orogen-related tooling is, for a pretty long time, developed in Rock.
One problem, when trying to use an already installed orocos toolchain
with the Rock infrastructure, is the level of synchronization between
the two codebases.
My blocker, when I update orocos-toolchain, is that I have no idea about
how much testing the pushed changes would get *in the context of an
orocos-toolchain user*. Especially in the context of a
ros-orocos-toolchain user.
The question is therefore: how can I update the orocos toolchain while
still being sure that people are testing these changes ? Who is
*actively* developing on the master branch of orocos-toolchain ?
Policy for Rock > Orocos updates
On Wed, May 9, 2012 at 11:19 AM, Sylvain Joyeux <sylvain [dot] joyeux [..] ...>wrote:
> The orogen-related tooling is, for a pretty long time, developed in Rock.
>
> One problem, when trying to use an already installed orocos toolchain
> with the Rock infrastructure, is the level of synchronization between
> the two codebases.
>
> My blocker, when I update orocos-toolchain, is that I have no idea about
> how much testing the pushed changes would get *in the context of an
> orocos-toolchain user*. Especially in the context of a
> ros-orocos-toolchain user.
>
> The question is therefore: how can I update the orocos toolchain while
> still being sure that people are testing these changes ? Who is
> *actively* developing on the master branch of orocos-toolchain ?
>
I think most/all are using toolchain-2.5, so pushing something to master
will only affect people who know what they are doing. I'm pushing/testing
new features on master too, so I don't see any problem of short periods of
danger/instability on master. Having it in there for a while is the only
way to get to a next major release.
Peter
Policy for Rock > Orocos updates
2012/5/9 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>
> The orogen-related tooling is, for a pretty long time, developed in Rock.
>
> One problem, when trying to use an already installed orocos toolchain
> with the Rock infrastructure, is the level of synchronization between
> the two codebases.
>
> My blocker, when I update orocos-toolchain, is that I have no idea about
> how much testing the pushed changes would get *in the context of an
> orocos-toolchain user*. Especially in the context of a
> ros-orocos-toolchain user.
>
> The question is therefore: how can I update the orocos toolchain while
> still being sure that people are testing these changes ? Who is
> *actively* developing on the master branch of orocos-toolchain ?
>
Personnaly, I am only using 'master', but most of Onera users are on
toolchain-2.5
Charles.
> --
> Sylvain Joyeux (Dr.Ing.)
> Space & Security Robotics
>
> !!! Achtung, neue Telefonnummer!!!
>
> Standort Bremen:
> DFKI GmbH
> Robotics Innovation Center
> Robert-Hooke-Straße 5
> 28359 Bremen, Germany
>
> Phone: +49 (0)421 178-454136
> Fax: +49 (0)421 218-454150
> E-Mail: robotik [..] ...
>
> Weitere Informationen: http://www.dfki.de/robotik
> -----------------------------------------------------------------------
> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
> Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
> Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
> (Vorsitzender) Dr. Walter Olthoff
> Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
> Amtsgericht Kaiserslautern, HRB 2313
> Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
> USt-Id.Nr.: DE 148646973
> Steuernummer: 19/673/0060/3
> -----------------------------------------------------------------------
> --
> Orocos-Dev mailing list
> Orocos-Dev [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev
>