v0.8 release timeline

[QUser534]

Priorities for the next release:

Beta:

• Feature: multiple backup profiles (not just default?) #60
• Feature request: Support BTRFS and XFS Reflink source volumes #75
• Support restoring of volume modes/attributes #78
• Receive: Use explicit discards in sparse mode #116
• Avoid comparing whole volume when receiveing with --sparse #150
• Add 'foolproof' encryption options (Add encryption using libsodium keyed-hash nonce recommendation #159 and Add encryption option using keyed-hash of existing digests #161)

Full Release:

• Feature: /etc config to set default options #133
• Better control over --autoprune #154
• Explore backups for fixed LVM, non-CoW storage #31
• Features supporting wyng-util-qubes v0.9 #185
• More robust cleanup options #164
• Account for unicode in meta strings and path names #190

The release version number has been changed from v0.4 to v0.8 to better reflect the range of changes recently being made to Wyng.

The upcoming 'beta5' will be the final beta and feature-freeze for v0.8.

Related: #197

---

Original @QUser534 query:

I would love to try this out, but need the encryption guarantees, so I cannot try out 0.3. Looks like 0.4 has been mostly marinating for a few months. Any idea on when it is considered stable?

[tasket]

@QUser534 I would say that a beta is 4-7 months away. There will probably be an alpha3 before then (we are now on alpha2), which will change the metadata format somewhat.

However, alpha2 is in a very usable state; I would call it stable for an alpha or even beta. You could use it under the assumption that I will try to have future releases convert the format of existing archives, although successful conversion isn't guaranteed. If there is a major conversion problem, then you could keep using alpha2 until you're ready to create a new archive using a newer Wyng release.

OTOH, you could use v0.3 with your own crypto layer, such as LUKS or one of the fs integrated tools like encfs, ecryptfs, or fscrypt (interesting comparison here). In terms of robustness against analytical attacks, probably the Wyng v0.4 integral encryption is the strongest, while the Linux encryption layers have various weaknesses if your backup destination is an untrusted server.

[tasket]

FWIW, the v0.4 encryption is IMHO basically finished, but still lacking review by a trained cryptographer. There may be one or two new options added to the crypto and that's it.

[tasket]

@QUser534 Wyng has entered its final alpha before it goes to beta.

[tasket]

@QUser534 Wyng has been released as beta.

[tasket]

The upcoming 'beta4' will be the final beta and feature-freeze for v0.8.

[tasket]

Timeline has slipped a bit as there needs to be a beta5, hopefully out this week. I'm trying hard to accommodate wyng-util-qubes requirements for reasonably user-friendly operation.

[tasket]

The to-do list for a release candidate is complete!

[tasket]

Beta5 has been tagged and released... the really final beta :)