GitLab

* version/2.3:
  Update README.md

* version/2.2:
  Update README.md

(cherry-picked from 2.5: 9112b933)

Bug identified when implementing a JSON output for tweak_pipeline.pl
(see #62) and backported to the earliest branch.

* version/2.3:
  add a pull request template

* version/2.2:
  add a pull request template

* version/2.3:
  End of support for older Perl versions
  Better diagnostic: tell what events were expected

* version/2.2:
  End of support for older Perl versions

Enabled testing on 5.26, as per our announcement. Hopefully it will work !

* version/2.3
  2019 copyright update

* version/2.2
  2019 copyright update

* version/2.3:
  Clearer with an eq, and clearer test description
  Since sqlite databases are dropped with "rm -f", the command doesn't fail
  Allow the IF NOT EXISTS of CREATE DATABASE
  Allow the IF NOT EXISTS of CREATE DATABASE
  Forgot to fix these two chdir

* version/2.2:
  Allow the IF NOT EXISTS of CREATE DATABASE

* version/2.1:
  Allow the IF NOT EXISTS of CREATE DATABASE

* version/2.0:
  Allow the IF NOT EXISTS of CREATE DATABASE

* version/1.9:
  Allow the IF NOT EXISTS of CREATE DATABASE

The Python Params API had not been updated following the changes made to
the Perl API in January 2016

* version/2.3:
  Go back to the original directory
  bugfix: chdir does not return the current path
  Added a warning about using too-recent versions of the core API

* version/2.2:
  Go back to the original directory
  bugfix: chdir does not return the current path
  Added a warning about using too-recent versions of the core API

* version/2.1:
  Go back to the original directory
  bugfix: chdir does not return the current path
  Added a warning about using too-recent versions of the core API

* version/2.0:
  Go back to the original directory
  bugfix: chdir does not return the current path
  Added a warning about using too-recent versions of the core API

* version/1.9:
  Go back to the original directory
  bugfix: chdir does not return the current path
  Added a warning about using too-recent versions of the core API

This must be an urban legend I have been spreading