Skip to content

Commit d853366

Browse files
committed
docs(README): update v2.2.0 roadmap details
* Clarify the introduction of the optional `rpgp` backend for OpenPGPv6 support. * Emphasize that GnuPG remains the default backend. * Note that both backends can be used simultaneously and that feature parity will improve over time.
1 parent 43e2ee6 commit d853366

1 file changed

Lines changed: 5 additions & 6 deletions

File tree

README.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -22,12 +22,11 @@ trustworthy to your privacy life.
2222
2323
**Planned Next Release:**
2424

25-
- v2.2.0+: expected in the next few months, with a focus on adding a new OpenPGP
26-
backend `rpgp` to have a better support for OpenPGPv6 standard. The `gnupg`
27-
backend will surely be kept as the default and the most important one, so the
28-
new `rpgp` backend will be optional for users who want to try it out. It must
29-
be noticed that the `rpgp` backend can not cover all the features of the
30-
`gnupg` backend at the beginning, but it will be improved gradually.
25+
- v2.2.0+ Roadmap: Expected in the coming months, this version introduces an
26+
optional rpgp backend for OpenPGPv6 (RFC 9580) support. GnuPG will remain the
27+
default; however, both backends can be used simultaneously. Although rpgp will
28+
initially have fewer features than GnuPG, I plan to bridge this gap through
29+
gradual improvements.
3130

3231
## Table of Contents
3332

0 commit comments

Comments
 (0)