I've just created the rtt-1.2 branch in order to prepare the 1.2.0 release.
This branch should only accept documentation updates and critical bugfixes.
You can preview the RTT 1.2.0 documentation/changes here:
Both KDL and OCL require a new release too which uses the new features of RTT
1.2.
KDL and OCL are at version 0.2.1. I propose to release both with v0.4.0. The
KTaskBrowser will be released at v1.2.0, as announced earlier.
Ruben, can you prepare the KDL release asap ? I plan to release RTT 1.2.0
on May 14. Could you write up some release notes and release it before that
date ?
Are there any release plans for BFL ?
Peter
Coordinated OCL/KDL/BFL releases with RTT 1.2.0
On Thursday May 3 2007 10:12:09 Peter Soetens wrote:
> I've just created the rtt-1.2 branch in order to prepare the 1.2.0 release.
> This branch should only accept documentation updates and critical bugfixes.
>
> You can preview the RTT 1.2.0 documentation/changes here:
>
>
>
> Both KDL and OCL require a new release too which uses the new features of
> RTT 1.2.
What new features could we use? From RTT-1.0 to RTT-1.2, nothing really
changed on the KDL-trunk. What should be the reason for a new KDL-release?
> KDL and OCL are at version 0.2.1. I propose to release both with v0.4.0.
> The KTaskBrowser will be released at v1.2.0, as announced earlier.
>
> Ruben, can you prepare the KDL release asap ? I plan to release RTT 1.2.0
> on May 14. Could you write up some release notes and release it before that
> date ?
I can try ;)
> Are there any release plans for BFL ?
>
> Peter
>
> --
> Peter Soetens -- FMTC --
Coordinated OCL/KDL/BFL releases with RTT 1.2.0
Quoting Ruben Smits <Ruben [dot] Smits [..] ...>:
>> Both KDL and OCL require a new release too which uses the new features of
>> RTT 1.2.
>
> What new features could we use? From RTT-1.0 to RTT-1.2, nothing really
> changed on the KDL-trunk. What should be the reason for a new KDL-release?
I remember a post that KDL was not compiling against trunk some time ago.
Peter
Coordinated OCL/KDL/BFL releases with RTT 1.2.0
On Thursday May 3 2007 11:37:16 Peter Soetens wrote:
> Quoting Ruben Smits <Ruben [dot] Smits [..] ...>:
> >> Both KDL and OCL require a new release too which uses the new features
> >> of RTT 1.2.
> >
> > What new features could we use? From RTT-1.0 to RTT-1.2, nothing really
> > changed on the KDL-trunk. What should be the reason for a new
> > KDL-release?
>
> I remember a post that KDL was not compiling against trunk some time ago.
>
Indeed, this was due to changes in RTT (the << operator for properties), I did
not really solved the problem, but just disabled the >> and << operators for
some of the kinematic family properties. Since the availability of this
operators, before the change in RTT it worked, never got in a release, i
don't think this is a reason to make a new one :)
Ruben
> Peter
> --
> www.fmtc.be
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
Coordinated OCL/KDL/BFL releases with RTT 1.2.0
Quoting Ruben Smits <Ruben [dot] Smits [..] ...>:
>> I remember a post that KDL was not compiling against trunk some time ago.
>>
>
> Indeed, this was due to changes in RTT (the << operator for
> properties), I did
> not really solved the problem, but just disabled the >> and << operators for
> some of the kinematic family properties. Since the availability of this
> operators, before the change in RTT it worked, never got in a release, i
> don't think this is a reason to make a new one :)
OK.
Peter
Coordinated OCL/KDL/BFL releases with RTT 1.2.0
On Thursday May 3 2007 12:12:03 Peter Soetens wrote:
> Quoting Ruben Smits <Ruben [dot] Smits [..] ...>:
> >> I remember a post that KDL was not compiling against trunk some time
> >> ago.
> >
> > Indeed, this was due to changes in RTT (the << operator for
> > properties), I did
> > not really solved the problem, but just disabled the >> and << operators
> > for some of the kinematic family properties. Since the availability of
> > this operators, before the change in RTT it worked, never got in a
> > release, i don't think this is a reason to make a new one :)
>
> OK.
i _can_ make a 0.2.2 release which has a few changes in the build-system:
shared-libs instead of static and a standard build-type
Ruben
> Peter
>
> --
> www.fmtc.be
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
Coordinated OCL/KDL/BFL releases with RTT 1.2.0
Quoting Ruben Smits <Ruben [dot] Smits [..] ...>:
> On Thursday May 3 2007 12:12:03 Peter Soetens wrote:
>> Quoting Ruben Smits <Ruben [dot] Smits [..] ...>:
>> >> I remember a post that KDL was not compiling against trunk some time
>> >> ago.
>> >
>> > Indeed, this was due to changes in RTT (the << operator for
>> > properties), I did
>> > not really solved the problem, but just disabled the >> and << operators
>> > for some of the kinematic family properties. Since the availability of
>> > this operators, before the change in RTT it worked, never got in a
>> > release, i don't think this is a reason to make a new one :)
>>
>> OK.
>
> i _can_ make a 0.2.2 release which has a few changes in the build-system:
>
> shared-libs instead of static and a standard build-type
Very good, although I don't understand what you mean with 'standard
build-type'.
Peter
Coordinated OCL/KDL/BFL releases with RTT 1.2.0
On Thursday May 3 2007 13:53:02 Peter Soetens wrote:
> Quoting Ruben Smits <Ruben [dot] Smits [..] ...>:
> > On Thursday May 3 2007 12:12:03 Peter Soetens wrote:
> >> Quoting Ruben Smits <Ruben [dot] Smits [..] ...>:
> >> >> I remember a post that KDL was not compiling against trunk some time
> >> >> ago.
> >> >
> >> > Indeed, this was due to changes in RTT (the << operator for
> >> > properties), I did
> >> > not really solved the problem, but just disabled the >> and <<
> >> > operators for some of the kinematic family properties. Since the
> >> > availability of this operators, before the change in RTT it worked,
> >> > never got in a release, i don't think this is a reason to make a new
> >> > one :)
> >>
> >> OK.
> >
> > i _can_ make a 0.2.2 release which has a few changes in the build-system:
> >
> > shared-libs instead of static and a standard build-type
>
> Very good, although I don't understand what you mean with 'standard
> build-type'.
like in RTT and OCL, CMAKE_BUILD_TYPE is set to a type i defined myself
instead of Release, Debug, RelWithDebInfo etc.
Ruben
> Peter
>
>
> --
> www.fmtc.be
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
Coordinated OCL/KDL/BFL releases with RTT 1.2.0
On Thursday 03 May 2007 10:12:09 Peter Soetens wrote:
> I've just created the rtt-1.2 branch in order to prepare the 1.2.0 release.
> This branch should only accept documentation updates and critical bugfixes.
>
> You can preview the RTT 1.2.0 documentation/changes here:
>
>
>
> Both KDL and OCL require a new release too which uses the new features of
> RTT 1.2.
>
> KDL and OCL are at version 0.2.1. I propose to release both with v0.4.0.
> The KTaskBrowser will be released at v1.2.0, as announced earlier.
>
> Ruben, can you prepare the KDL release asap ? I plan to release RTT 1.2.0
> on May 14. Could you write up some release notes and release it before that
> date ?
>
> Are there any release plans for BFL ?
We plan a the 0.5.0 release for BFL on the short term. This would include
cpp-unit tests and a cmake-based build system.
Tinne
Coordinated OCL/KDL/BFL releases with RTT 1.2.0
On Thursday 03 May 2007 10:12:09 Peter Soetens wrote:
> I've just created the rtt-1.2 branch in order to prepare the 1.2.0 release.
> This branch should only accept documentation updates and critical bugfixes.
>
> You can preview the RTT 1.2.0 documentation/changes here:
>
>
>
> Both KDL and OCL require a new release too which uses the new features of
> RTT 1.2.
>
> KDL and OCL are at version 0.2.1. I propose to release both with v0.4.0.
> The KTaskBrowser will be released at v1.2.0, as announced earlier.
>
> Ruben, can you prepare the KDL release asap ? I plan to release RTT 1.2.0
> on May 14. Could you write up some release notes and release it before that
> date ?
>
> Are there any release plans for BFL ?
We plan a the 0.5.0 release for BFL on the short term. This would include
cpp-unit tests and a cmake-based build system.
Tinne
_______________________________________________
I hereby promise not to top-post on the
BFL mailing list
BFL [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/bfl
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm