Snapshot Creation / Cloning / Destruction

With zfs snapshot creation / destruction / cloning support. Filesystems can also be destroyed, but recursive destroy is not implemented yet.

ZFS Snapshot List / Rollback

With zfs snapshot display / rollback support. Snapshots can also be mounted, but Finder and other GUI programs can not access them.

And and a lot of internal refactoring. ZetaWatch might now also work on Mac OS X 10.11.

Keychain Support / Notifications

ZetaWatch will now notify about the success of many actions, such as mounting, unmounting, importing, exporting or unloading keys. Also notify about attempting to automatically import pools.

It can now also optionally store passwords to unlock encrypted zfs file systems in the Mac OS X keychain. This can be controlled on a filesystem-by-filesystem basis. The default can be configured in the settings.

Scrub Pause

Release 28 improves auto-update and adds scrub pause support

Auto Update

ZetaWatch now auto updates using sparkle framework.

Unload Key / Recursive Mount / Recursive Unmount

Encryption Keys can now be unloaded. This includes a recursive unmount of the chosen dataset before unloading the key.

Filesystems can now be recursively mounted / unmounted. This is more generally useful than unmounting or mounting a single filesystem, so it is first in the menu. The recursive options are always shown, even if not appropriate for the selected file system, since child filesystems can be affected.

Better reporting

Improved scrub reporting and in-progress action reporting. And some internal cleanups that hopefully didn't break anything.

Improved Auto Import

ZFS Import All protection

Only import pools automatically if they are healthy. Show the status of importable pool with emoji, like that of imported pools.
Import all now checks for pool health before attempting an import. Pools that have been destroyed or are not healthy are not considered for import. Such pools can still be imported individually.

Auto Pool Import

Import newly discovered pools unless they were already known as being imported before, unless they already vanished from being importable (for example by the device having been removed). This heuristic is likely not perfect, but it seems to work at least sometimes.

Proxy Threading Fixes

Attempt to solve the proxy threading issues at the root, by dispatching all replies to the main thread instead of leaving this to the individual consumers, which should avoid several race conditions.