| 1 |
jenkins-debian-glue (0.22.0) unstable; urgency=medium |
| 2 |
|
| 3 |
To reduce the namespace pollution, all programs are namespaced now with |
| 4 |
«jdg-» or «jdg-tap-» and their names had their ‘_’ replaced with ‘-’. |
| 5 |
|
| 6 |
For backwards compatibility symlinks are provided for a transition period |
| 7 |
to avoid breakage, but projects should be switched to the new names, which |
| 8 |
will disappear eventually. |
| 9 |
|
| 10 |
-- Guillem Jover <[email protected]> Thu, 11 Feb 2021 22:24:37 +0100 |
| 11 |
|
| 12 |
jenkins-debian-glue (0.14.0) unstable; urgency=medium |
| 13 |
|
| 14 |
To reduce the amount of Debian binary packages we decided to |
| 15 |
minimize the number of packages we ship via jenkins-debian-glue. |
| 16 |
This means that the packages named |
| 17 |
jenkins-debian-glue-buildenv-git, |
| 18 |
jenkins-debian-glue-buildenv-svn, |
| 19 |
jenkins-debian-glue-buildenv-slave, |
| 20 |
jenkins-debian-glue-buildenv-lintian, |
| 21 |
jenkins-debian-glue-buildenv-taptools and |
| 22 |
jenkins-debian-glue-buildenv-piuparts are deprecated now. |
| 23 |
To get all the scripts just the jenkins-debian-glue package is |
| 24 |
needed. To install all the Debian packages that might be needed |
| 25 |
to be useful with all the scripts the |
| 26 |
jenkins-debian-glue-buildenv package can be used. If you don't |
| 27 |
want to install all the packages which are listed in |
| 28 |
jenkins-debian-glue-buildenv's Depends/Recommends you're |
| 29 |
encouraged to create your own metapackage or use the |
| 30 |
configuration management system of your choice. |
| 31 |
|
| 32 |
-- Michael Prokop <[email protected]> Sat, 22 Aug 2015 12:26:59 +0200 |
| 33 |
|
| 34 |
jenkins-debian-glue (0.6.0) unstable; urgency=low |
| 35 |
|
| 36 |
The timestamp format used in automatically generated version |
| 37 |
strings changed. |
| 38 |
|
| 39 |
Until and including version 0.5.0 jenkins-debian-glue's |
| 40 |
generate-git-snapshot and generate-svn-snapshot scripts used |
| 41 |
"seconds since 1970-01-01 00:00:00 UTC" inside the version |
| 42 |
string. The new timestamp format YYYYMMDDhhmmss (in UTC) sorts |
| 43 |
equally well as unix timestamp and yet it is much more usable |
| 44 |
for human beings. As this timestamp change still increases the |
| 45 |
version numbers the change does NOT break any existing setups, |
| 46 |
but to avoid confusion it's worth noting. |
| 47 |
|
| 48 |
-- Michael Prokop <[email protected]> Mon, 10 Jun 2013 23:38:45 +0200 |