From 5c4facd9dcced893d03e61fd60ea265299d020e3 Mon Sep 17 00:00:00 2001 From: Alexander Neumann Date: Thu, 25 May 2017 15:26:22 +0200 Subject: [PATCH] Update CHANGELOG.md --- CHANGELOG.md | 44 +++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 41 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 7477cd045..3fea3daa3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,7 +1,45 @@ This file describes changes relevant to all users that are made in each released version of restic from the perspective of the user. -Changes in 0.5.X -================ +Important Changes in 0.5.1 +========================== - * Sample entry, made the flux capacitor work with less than 1.21GW +Consistent forget policy +------------------------ + +The `forget` command was corrected to be more consistent in which snapshots are +to be forgotten. It is possible that the new code removes more snapshots than +before, so please review what would be deleted by using the `--dry-run` option. + +https://github.com/restic/restic/pull/957 +https://github.com/restic/restic/issues/953 + +Unified repository layout +------------------------- + +Up to now the s3 backend used a special repository layout. We've decided to +unify the repository layout and implemented the default layout also for the s3 +backend. For creating a new repository on s3 with the default layout, use +`restic -o s3.layout=default init`. For further commands the option is not +necessary any more, restic will automatically detect the correct layout to use. +A future version will switch to the default layout for new repositories. + +https://github.com/restic/restic/pull/966 +https://github.com/restic/restic/issues/965 + +Memory and time improvements for the s3 backend +----------------------------------------------- + +We've updated the library used for accessing s3, switched to using a lower +level API and added caching for some requests. This lead to a decrease in +memory usage and a great speedup. In addition, we added benchmark functions for +all backends, so we can track improvements over time. The Continuous +Integration test service we're using (Travis) now runs the s3 backend tests not +only against a Minio server, but also against the Amazon s3 live service, so we +should be notified of any regressions much sooner. + +https://github.com/restic/restic/pull/962 +https://github.com/restic/restic/pull/960 +https://github.com/restic/restic/pull/946 +https://github.com/restic/restic/pull/938 +https://github.com/restic/restic/pull/883