|
Size: 779
Comment: initial version with some roadmap planning
|
Size: 1418
Comment: As 4.0.0 was released, add 4.0.x and 4.1.0
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| (For Developers, just an initial stub, work in progress) = Potential Roadmap-Planning |
= Gpg4win Roadmap |
| Line 4: | Line 3: |
| == next minor release? maybe 2.2.2 | This page lists the major goals that are worked on. For minor releases only the next release is listed with some more details. |
| Line 6: | Line 6: |
| === screenreader ability for kleo | == Life Cycle * For the crypto engine, see [[https://gnupg.org/download/index.html#end-of-life|GnuPG's EOL]]. Note that GnuPG can be updated for Gpg4win by using the simple Gnu~PG installer. |
| Line 8: | Line 9: |
| === update on some libraries, e.g. image format libraries | * Gpg4win 3.1.x with GnuPG 2.2 will be maintained as part of GnuPG VS-Desktop [[https://gnupg.com/gnupg-desktop.de.html|GnuPG Desktop]] at least until Gpg4win 4 gains approval for restricted communication in Germany. == Gpg4win 4.1.0 (tba) == Gpg4win 4.0.x (2022) * Fixing important defects. * Will be released as needed. * New features (that keep the user experience). |
| Line 11: | Line 19: |
| === Shall we remove Claws-Mail from the installer? | == Ongoing developments |
| Line 13: | Line 21: |
| Rationale: Claws-Mail maintains [[https://www.claws-mail.org/win32/|its own installer for windows]], which often is more current. Supporting it by building in into the Gpg4win 2.0.0 installer was a success, this helped the initiative to get a windows installer and it spread the word. |
* Authenticated encryption support for S/MIME in Gpg~S~M * Better Microsoft Exchange / GAL integration for GpgOL (fingerprints and encryption info as attributes in the GAL) * Further improvements to automated encryption -> default on. * Usability and automation improvements * One focus is improved hardware token support (Yubikey, GnuK-Token) and for the GnuK-Token to improve availability in [[https://dev.gnupg.org/T4363|Europe]]. |
| Line 17: | Line 28: |
| It makes Gpg4win easier to maintain, if we decouple the installers. There is less work to be done, especially less quality control and even some space is safed. |
== For each release * Update of third party libraries. * Update of Gnu~P~G and libraries. |
| Line 20: | Line 32: |
== next normal release? maybe 2.3.0 |
//Additional features from [[../Wishlist|wishlist]] (needs cleanup) depending on funding and available time.// |
Gpg4win Roadmap
This page lists the major goals that are worked on. For minor releases only the next release is listed with some more details.
Life Cycle
- For the crypto engine, see GnuPG's EOL. Note that GnuPG can be updated for Gpg4win by using the simple GnuPG installer.
- Gpg4win 3.1.x with GnuPG 2.2 will be maintained as part of GnuPG VS-Desktop GnuPG Desktop at least until Gpg4win 4 gains approval for restricted communication in Germany.
Gpg4win 4.1.0 (tba)
Gpg4win 4.0.x (2022)
- Fixing important defects.
- Will be released as needed.
- New features (that keep the user experience).
Ongoing developments
- Authenticated encryption support for S/MIME in GpgSM
- Better Microsoft Exchange / GAL integration for GpgOL (fingerprints and encryption info as attributes in the GAL)
- Further improvements to automated encryption -> default on.
- Usability and automation improvements
- One focus is improved hardware token support (Yubikey, GnuK-Token) and for the GnuK-Token to improve availability in Europe.
For each release
- Update of third party libraries.
- Update of GnuPG and libraries.
Additional features from wishlist (needs cleanup) depending on funding and available time.