README: list changes for v0.12 but don't add release date
The release of v0.12 is delayed to give people more time to upgrade using "mv" or "rsync --remove-source-files".
This commit is contained in:
parent
4d067e2de1
commit
0869188032
13
README.md
13
README.md
@ -101,15 +101,22 @@ RM: 4.42
|
||||
Changelog
|
||||
---------
|
||||
|
||||
v0.12 (not yet released)
|
||||
* Deprecate filesystems created by v0.6 and older (stage 2/3)
|
||||
* Now they can only be mounted read-only
|
||||
* A warning explaining the situation is printed as well
|
||||
* New command line option: `-ro`
|
||||
* Mounts the filesystem read-only
|
||||
|
||||
v0.11, 2016-06-10
|
||||
* Deprecate filesystems created by v0.6 and older
|
||||
* Deprecate filesystems created by v0.6 and older (stage 1/3)
|
||||
* Filesystems can still be mounted but a warning is printed
|
||||
* See https://github.com/rfjakob/gocryptfs/issues/29 for details and
|
||||
join the discussion
|
||||
* Add rsync stress test "pingpong-rsync.bash"
|
||||
** Fix chown and utimens failures that caused rsync to complain
|
||||
* Fix chown and utimens failures that caused rsync to complain
|
||||
* Build release binaries with Go 1.6.2
|
||||
** Big speedup for CPUs with AES-NI, see [#23](https://github.com/rfjakob/gocryptfs/issues/23))
|
||||
* Big speedup for CPUs with AES-NI, see [#23](https://github.com/rfjakob/gocryptfs/issues/23))
|
||||
|
||||
v0.10, 2016-05-30
|
||||
* **Replace `spacemonkeygo/openssl` with `stupidgcm`**
|
||||
|
Loading…
Reference in New Issue
Block a user