Skip to content

Commit 37d3a29

Browse files
committed
add 2.12.2 patch release notes
1 parent 04e0f3f commit 37d3a29

File tree

1 file changed

+14
-2
lines changed

1 file changed

+14
-2
lines changed

cpt-releasenotes.rst

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,23 @@
11

2+
Release Notes for CernVM-FS 2.12.2
3+
==================================
4+
5+
CernVM-FS 2.12.2 is a small patch release that adds the "quick" ``cvmfs_config fsck -q`` option to check for and quarantine zeroed files in the cache.
6+
7+
Release Notes for CernVM-FS 2.12.1
8+
==================================
9+
10+
CernVM-FS 2.12.1 is a small patch release that fixes a packaging issue: it ensures that the service to reload cvmfs after package upgrades is correctly configured.
211

312
Release Notes for CernVM-FS 2.12.0
413
==================================
514

6-
CernVM-FS 2.12.0 is a sizeable feature release with new features, bug fixes and performance improvements,
15+
CernVM-FS 2.12.0 is a sizeable feature release with new features, bug fixes and performance improvements.
16+
NOTE: Testing has shown instances of cache corruption with this release, it will not be released in production. On your testing instances, upgrade to 2.12.2, run ``cvmfs_config fsck -q`` frequently and report any errors.
717

818
Highlights are:
919

10-
* Support for FUSE-T on MacOS, allowing for easy installation without security tweaks
20+
* Experimental Support for FUSE-T on MacOS, allowing for easy installation without security tweaks
1121

1222
* Refcounted Cache Manager now the default
1323

@@ -17,6 +27,8 @@ Highlights are:
1727

1828
* Several fixes in the fuse internals, for example the page cache tracker
1929

30+
* Reloading of CVMFS after package upgrades is now done via a daemon to avoid blocking the package transaction
31+
2032

2133
As with previous releases, upgrading clients should be seamless just by
2234
installing the new package from the repository. As usual, we recommend updating only a few worker nodes first and gradually ramp up once the new version proves

0 commit comments

Comments
 (0)