RSB 0.6 Released

Added by J. Moringen over 12 years ago

Overview

We are happy to announce the release of version 0.6 of RSB. The development activities in this cycle focused on
  • tool improvements
  • better packaging and deployment
  • extended documentation

In the process, about 40 issues have been created and subsequently resolved.

This RSB release is available in the following forms:
  • Source archives
  • Pre-compiled self-installing archives or executable binaries
  • Debian packages for different Ubuntu Linux versions
These can be downloaded from the continuous integration server: As always, bugs, feature requests and enhancement proposals can be reported in the respective issue trackers Please note that
  • RSB clients using the 0.6 version of RSB cannot generally communicate with clients using a previous RSB version.
  • Log files recorded with the 0.6 version of RSBag cannot be processed with older RSBag versions. The opposite direction works, though.

The following paragraphs describe the changes in more detail. An overview regarding the current state of the different implementations is available in the wiki.

For an even more detailed list of fixed bugs, added features and other enhancements, see https://code.cor-lab.de/projects/rsb/versions/25

General

RSB Tools

  • The C++ logger now has a "monitor mode" , see #815
  • The C++ logger can now print event collections, see #736
  • The Common Lisp logger adjusts its display to the width of the containing terminal
  • The Common Lisp logger can now print event collections, see #737

RSBag Tools

  • All tools can now read log files written by older tool versions, see #735
  • A simplistic Elan backend has been added, see #780
  • The RSBag distribution now includes some export-scripts which can be used with bag-cat (or the logger)
  • bag-cat now supports the same output styles as the logger, see #733, #758
  • bag-record can now store IDL, in the format field of TIDELog files, see #867
  • bag-play and bag-cat now support time-based playback ranges via --start-time and --end-time, see #932

Comments