mirror of
https://github.com/pgbackrest/pgbackrest.git
synced 2025-02-01 13:17:46 +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.
36 lines
1.8 KiB
XML
36 lines
1.8 KiB
XML
<release date="2015-12-24" version="0.89" title="Timeout Bug Fix and Restore Read-Only Repositories">
|
|
<release-core-list>
|
|
<release-bug-list>
|
|
<release-item>
|
|
<release-item-contributor-list>
|
|
<release-item-ideator id="stephen.frost"/>
|
|
</release-item-contributor-list>
|
|
|
|
<p>Fixed an issue where longer-running backups/restores would timeout when remote and threaded. Keepalives are now used to make sure the remote for the main process does not timeout while the thread remotes do all the work. The error message for timeouts was also improved to make debugging easier.</p>
|
|
</release-item>
|
|
</release-bug-list>
|
|
|
|
<release-feature-list>
|
|
<release-item>
|
|
<p>Allow restores to be performed on a read-only repository by using <setting>{[dash]}-no-lock</setting> and <setting>{[dash]}-log-level-file=off</setting>. The <setting>{[dash]}-no-lock</setting> option can only be used with restores.</p>
|
|
</release-item>
|
|
</release-feature-list>
|
|
</release-core-list>
|
|
|
|
<release-doc-list>
|
|
<release-development-list>
|
|
<release-item>
|
|
<p>Minor styling changes, clarifications and rewording in the user guide.</p>
|
|
</release-item>
|
|
</release-development-list>
|
|
</release-doc-list>
|
|
|
|
<release-test-list>
|
|
<release-development-list>
|
|
<release-item>
|
|
<p>The dev branch has been renamed to master and for the time being the master branch has renamed to release, though it will probably be removed at some point {[dash]}- thus ends the gitflow experiment for <backrest/>. It is recommended that any forks get re-forked and clones get re-cloned.</p>
|
|
</release-item>
|
|
</release-development-list>
|
|
</release-test-list>
|
|
</release>
|