2017-03-09 09:40:24 +00:00
|
|
|
This file describes changes relevant to all users that are made in each
|
|
|
|
|
released version of restic from the perspective of the user.
|
|
|
|
|
|
2017-05-25 15:06:06 +00:00
|
|
|
Important Changes in 0.X.Y
|
|
|
|
|
==========================
|
|
|
|
|
|
|
|
|
|
Small changes:
|
|
|
|
|
--------------
|
|
|
|
|
|
|
|
|
|
* Regular status report: We've removed the status report that was printed
|
|
|
|
|
every 10 seconds when restic is run non-interactively. You can still force
|
|
|
|
|
reporting the current status by sending a `USR1` signal to the process.
|
|
|
|
|
https://github.com/restic/restic/pull/974
|
|
|
|
|
|
2017-05-25 13:42:44 +00:00
|
|
|
Important Changes in 0.6.0
|
2017-05-25 13:26:22 +00:00
|
|
|
==========================
|
2017-03-09 09:40:24 +00:00
|
|
|
|
2017-05-25 13:26:22 +00:00
|
|
|
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
|
