2.4.1

• A bug was solved, if a benchmark used the older ,-separated tag= format in contrast to the new layout introduced in version 2.2.2.
• A warning message in context of newer YAML versions was removed.
• A Python3 problem inside the YAML parser was solved.
• A bug was solved, which was raised if the benchmark was started on a different filesystem then the one which was configured within outpath.
• The jube base script within bin will now use python3 by default. This is necessary as many newer systems does not have a "standard" python
  defined by default. In addition the additional script jube-python2 is now available, which utilizes python2.
  So far Python 2 is still fully supported but can be seen deprecated and future versions of JUBE might break
  the Python 2 backwards compatibility.
• All style=pretty tables in JUBE will now use a markdown like format to allow easier integration within other tools.

2.4.0

• New YAML based JUBE input format. The existing XML format still stays available. Both
  formats cover the same amount of features. If you plan to use YAML based JUBE input files, you have to
  add the pyyaml-module to your Python module library.
• New <do> attribute: error_file="...". In contrast to the existing done_file this file handle can be used to mark
  a broken asynchronous execution (the job templates in the platform folder were updated accordingly)
• The analyse step is now automatically called when a result is shown and if it was not executed before (instead of showing an error message).
• New option --workpackage for remove command line sub command. Allows to remove an individual
  workpackage from a benchmark.
• New table output format: aligned