db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2024-12-12 10:04:14 +02:00
Code Issues Releases Activity

Next development cycle.

Browse Source
This commit is contained in:
David Steele 2016-04-06 09:41:33 -04:00
parent 5307c858a7
commit aacc369e4f
3 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
CHANGELOG.md
View File

@ -1,5 +1,10 @@
# pgBackRest<br/>Change Log
## v0.95dev: UNDER DEVELOPMENT
__No Release Date Set__
*
## v0.92: Command-line Repository Path Fix
__Released April 6, 2016__

6
doc/xml/change-log.xml
View File

@ -6,6 +6,12 @@
</intro>
<changelog>
<changelog-release date="XXXX-XX-XX" version="0.95dev" title="UNDER DEVELOPMENT">
<release-feature-bullet-list>
<release-feature><text></text></release-feature>
</release-feature-bullet-list>
</changelog-release>
<changelog-release date="2016-04-06" version="0.92" title="Command-line Repository Path Fix">
<release-feature-bullet-list>
<release-feature><text>Fixed an issue where the master process was passing <setting>--repo-remote-path</setting> instead of <setting>--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>--repo-remote-path</setting> was defined on the command line rather than in <file>pg_backrest.conf</file>. <i>Reported by Jan Wieck</i>.</text></release-feature>

2
lib/BackRest/Version.pm
View File

@ -17,7 +17,7 @@ use Exporter qw(import);
# repositories or manifests can be read - that's the job of the format number.
#-----------------------------------------------------------------------------------------------------------------------------------
our # 'our' keyword is on a separate line to make the ExtUtils::MakeMaker parser happy.
$VERSION = '0.92';
$VERSION = '0.95dev';
push @EXPORT, qw($VERSION);