mirror of
https://github.com/pgbackrest/pgbackrest.git
synced 2025-01-22 05:08:58 +02:00
c0935b7992
The release.xml file was getting pretty unwieldy so break release notes into separate files. Also break contributors into a separate file. In theory most of release.xml could now be generated automatically but adding a new release does not represent a serious maintenance burden, so for the time being it does not seem worth it.
14 lines
883 B
XML
14 lines
883 B
XML
<release date="2016-04-06" version="0.92" title="Command-line Repository Path Fix">
|
|
<release-core-list>
|
|
<release-bug-list>
|
|
<release-item>
|
|
<release-item-contributor-list>
|
|
<release-item-ideator id="jan.wieck"/>
|
|
</release-item-contributor-list>
|
|
|
|
<p>Fixed an issue where the master process was passing <setting>{[dash]}-repo-remote-path</setting> instead of <setting>{[dash]}-repo-path</setting> to the remote and causing the lock files to be created in the default repository directory (<path>/var/lib/backup</path>), generally ending in failure. This was only an issue when <setting>{[dash]}-repo-remote-path</setting> was defined on the command line rather than in <file>pg_backrest.conf</file>.</p>
|
|
</release-item>
|
|
</release-bug-list>
|
|
</release-core-list>
|
|
</release>
|