3.7
* the taktuk library that implements the C-interface with TakTuk has a wrong
  .so number -> do not use it
* the latest revision of Term::ReadLine Core module breaks TakTuk
  interoperability with other programs. In particular, it breaks kanif. This
  should also affect all previous TakTuk releases
* TakTuk hangs when connections using a connector command that cannot be killed
  are timeouted. This is the case of Grid5000 for instance.

3.6.3
* Perl-module do not install in prefix directory
* TakTuk fail if Sys::Hostname is not installed in the system

3.6.2
* ranges in hostnames cannot start from 0
* configure error message

3.6.1
* command quit does not work properly on recent linux machines

3.6
* option -t for setting timeouts does not work anymore
* network state command might deadlock
* some termination issues: interpreter does not always terminates properly

3.5.2
* file_input command blocks when sending input to a command that writes output
  at the same time (e.g. cat). Overall this is reveals more serious deadlock
  possibilities in TakTuk. The internal sending mechanism will have to be
  changed in order to avoid this problem... Planned for 3.6

3.5.1
* -S does not send files in time for use in options

3.5
* taktuk::send error reporting not always correct

3.3
* connections timeout and cancellation do not always work when connector forks
  (e.g. proxy command in ssh)
* some parsing bug with input parameters
* piping taktuk in scripts do not work
* ugly behavior when environment settings are illegal
* C interface does not tolerate signals

3.2.4
* $depth variable is the depth of TakTuk instance in the deployed tree. Thus
  couples ($position, $depth) are not necessarily unique. This was not the
  intended meaning of these variables. $depth and $father_position will be made
  obsolete in the next releases, do not use them. Also, $position will change a
  bit.

3.2.3
* when many connections fail and connection time is timeouted, TakTuk might
  issue some warning because it does not manage timers removal correctly

3.2
* the print_tree command does not work correctly when executed on a non root
  node (I'm not sure wether this deserves a fix)
* ./taktuk -v pretends it is version 3.1 instead of 3.2
* hostnames ranges do not work correctly when the lower bound is not
  lexicographically lower than the second (for instance [2-10] do not work)

3.1
* abnormal termination of some TakTuk parts when sending input to already
  terminated commands

3.0
* missing -l option

3.0.2
* Files containing options and command must be terminated by a separator (e.g.
  newline or space by default)
* Commands parsing bug in interactive mode introduced in this release (bad
  parsing of command separators)
* TakTuk still fail if Time::HiRes is not installed. It seems to be the case
  only for too old Perl versions that do not support other things in TakTuk
  (some open modes). So, from now, it is a requirement to have Time::HiRes
  installed. This should not be very annoying as it is included as core module
  at least since Perl 5.8.0.

3.0.1
* Minor bug when using -P option
* TakTuk fail if Time::HiRes is not installed
* sets specifications do not work with taktuk commands (you have to change the
  command separator to something that do not include comma)
* one cannot use variables (such as $HOME) in the filename given to taktuk_perl