RTT and OCL 2.0.0-beta2 Released
| Submitted by peter on Fri, 2010-04-02 09:36 |
It's called beta, but it's closer to release candidate than its name
suggests. This preview release of RTT 2.0 is capable of doing anything
you could do in 1.x, but only better, faster and cheaper. We're very
close to a feature freeze at this point in time and focus on the
testing and taking the latest user feedback into account. The main
focus of this release was to get CORBA transport up and running. It
needs polishing, but you can taskbrowse corba-deployed components.
For the latest information, check out the 2.0.0-beta2 wiki page:
http://www.orocos.org/wiki/rtt/rtt-20/rtt-200-beta2
It links to a bunch of useful sub-pages concerning what changed and how users
can upgrade.
Where to find it ?
There are tar balls and online docs available in the devel section of the
server kindly provided by the University of Leuven:
http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.2/doc/api/html/
http://people.mech.kuleuven.be/~orocos/pub/devel/rtt/v1.99.2/orocos-rtt-...
http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.2/doc/api/html/
http://people.mech.kuleuven.be/~orocos/pub/devel/ocl/v1.99.2/orocos-ocl-...
The exercises of beta1 still apply (1.99.1):
http://people.mech.kuleuven.be/~orocos/pub/devel/examples/rtt/tutorial
Other official code resources for 2.0 are my git repositories on github: rtt-
examples, orocos-rtt and orocos-ocl. Check out the ocl-2.0-mainline and
rtt-2.0-mainline code. I will not host 2.0 in an SVN repository.
What's not in here ?
See the caveats section on the wiki. Attention is now going to easy typekit
generation and plugin loading.
What will this release allow you to do ?
- Test porting effort to the RTT 2.0 C++ and CORBA API.
We have created scripts for converting application code to the 2.0 API,
regarding the C++ part.
- Test RTT 2.0 on your distribution/target.
A lot of code changed, not all compilers or operating systems could be tested.
Now is the time to see if 2.0 *at least compiles* on your system.
Requires cmake 2.6-patch3 to build or later.
What can you do to help ?
- Test the conversion scripts and update the wiki or scripts if you find
issues.
- Update wiki pages, installation notes etc if you encounter inconsistencies.
- Send patches against this codebase, preferably using a git repository.
- Provide feedback on documentation or API changes.
Are we there yet ?
There's need for more testing and user feedback before we can make it
to a final release. I'm trying to postpone feature additions after
2.0.0 such that we can release as early as possible. A new release
will follow around end of April, that could qualify as release
candidate.
Enjoy !
Peter
RTT and OCL 2.0.0-beta2 Released
________________________________________
From: Ruben Smits
Sent: Wednesday, April 21, 2010 20:49
To: Stephen Roderick
Subject: RE: [Orocos-Dev] RTT and OCL 2.0.0-beta2 Released
check http://build.willowgarage.com for an example of a fairly extensive buildfarm
Ruben
________________________________________
From: orocos-dev-bounces [..] ... [orocos-dev-bounces [..] ...] On Behalf Of Stephen Roderick [kiwi [dot] net [..] ...]
Sent: Wednesday, April 21, 2010 19:49
To: Peter Soetens
Cc: orocos-dev; Klaas Gadeyne
Subject: Re: [Orocos-Dev] RTT and OCL 2.0.0-beta2 Released
On Apr 20, 2010, at 12:08 , Peter Soetens wrote:
> On Thu, Apr 15, 2010 at 13:56, S Roderick <kiwi [dot] net [..] ...> wrote:
>> On Apr 15, 2010, at 04:01 , Klaas Gadeyne wrote:
>>
>>> Hi,
>>>
>>> On Fri, Apr 2, 2010 at 11:33 AM, Peter Soetens <peter [..] ...> wrote:
>>> [...]
>>>> For the latest information, check out the 2.0.0-beta2 wiki page:
>>>> http://www.orocos.org/wiki/rtt/rtt-20/rtt-200-beta2
>>>
>>> [disclaimer: I've ran the tests from the git repository, and ran a hg
>>> update -C to the rtt-2.0-mainline]
>>>
>>> Platform: debian testing, gcc 4.4.3, boost 1.40
>>>
>>> I have 3 failing tests (instead of only types-test), it's not obvious
>>> if this is due to timing issues.
>>>
>>> Best regards,
>>>
>>> Klaas
>>
>> There was brief talk of a "build farm" a few months back. Has this gone any further?
>>
>> Alternatively, any chance of setting up CDash on a centralized server, so that some of us can run builds and upload results? Getting CDash itself working is easy, getting the scripts/cron-jobs on the client machine is a little tricky but quite doable. Automating this would save some of this back and forward perhaps ...?
>
> I'm running a hudson on my development machine, also KUL runs a
> hudson, pulling from the public repositories. We only get emails for
> failing builds (I believe), not for failing tests.
>
> I prefer hudson above cdash... or are they complementary in a way ?
>
> Peter
Hudson looks nice, with some nice infrastructure integration that CDash lacks, but how can an external entity publish build results to a Hudson server? It seems to be built around a fairly fixed master/slave architecture, whereas CDash provides the server plus tools to run slave builds anywhere (and publish them back to the server). For Hudson, it looks like you need a login to the master server to publish, if using something like the Build Publisher plugin. One of the really nice features of CDash is the ability to easily push build results, for those of us that have different configurations (eg Mac OS X) that aren't currently system tested. This distributes the test effort.
I also can't find an example hudson site to review - at least CDash presents several working sites for potential new users!
Is the project interested in publishing build results, having others contribute build results, and in general, having more system configurations tested? [I would hope Yes, Yes and Yes]
Is anyone else personally interested in pursuing this kind of direction?
Stephen
--
Orocos-Dev mailing list
Orocos-Dev [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-dev