|
Size: 1243
Comment: Gp4win Roadmap updated for 3.0
|
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 3: | Line 3: |
| == Gpg4win 2.3.0 (November 2015) * Support for AES-NI in gcrypt * Read support for MIME messages (PGP/MIME and S/MIME) in GpgOL * Outlook 2016 Support for GpgOL |
This page lists the major goals that are worked on. For minor releases only the next release is listed with some more details. |
| Line 8: | Line 6: |
| == Gpg4win 3.0-testversion1 (end of 2015) * GnuPG 2.1 integration * Move installation location from %~P~R~O~G~R~A~M~F~I~L~E~S%\~G~N~U\~Gnu~P~G to %~P~R~O~G~R~A~M~F~I~L~E~S%\~Gpg4win (To avoids conflicts with other ~Gnu~P~G installers and to use a more logic place to install) * MIME send support for GpgOL |
== 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 13: | Line 9: |
| == Gpg4win 3.0-testversion2 (Q1 2016) * Kleopatra based on KDE Framework 5 * Kleopatra included from Source in the Gpg4win build * Packaging additional localisations for Kleopatra |
* 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. |
| Line 18: | Line 11: |
| == Gpg4win 3.0-testversion* (Q1-Q4 2016) * stabilize improvements in Kleopatra, GpgOL and GnuPG |
== Gpg4win 4.1.0 (tba) |
| Line 21: | Line 13: |
| == Gpg4win 3.0 (end of 2016) * GnuPG 2.1 integration (with ECC support) * GpgOL: MIME support, Exchange Server support, 64-bit * Kleoaptra: based on KDE Frameworks 5, many UI improvements, additional localisations * Gpg4win update notification |
== 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 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 29: | Line 30: |
| * Update of gnupg and libraries. | * Update of Gnu~P~G and libraries. |
| Line 31: | Line 32: |
//Additional features from [[../Wishlist|wishlist]] depends on funding and available time.// |
//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.