Size: 1446
Comment: 2.2.4 planning gets more real triggered by gnupg 2.0.27
|
← Revision 128 as of 2023-09-21 13:49:59 ⇥
Size: 1535
Comment: small update, now that 4.2.0 is there
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
(For Developers, work in progress) = Potential Roadmap-Planning |
= Gpg4win Roadmap |
Line 4: | Line 3: |
== 2.2.4 (Q1 2015) * update of third party libraries. ** libpng to 1.2.5 (probably no relevant changes for Gpg4win) * update of gnupg to 2.0.27 and libraries * (Claws will not be updated, because overall time pressure and lack of help with it.) |
This page lists the major goals that are worked on. For minor releases only the next release is listed with some more details. |
Line 10: | Line 6: |
== next normal release? maybe 2.3.0 or 3.0.0 | The [[https://dev.gnupg.org/project/board/117/|Release Info workboard]] sometimes has more features for upcoming GnuPG or Gpg4win releases. |
Line 12: | Line 9: |
(Not scheduled yet, may depend on available funding). Mid 2015? | == 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 14: | Line 12: |
=== GnuPG 2.1 integration | * Gpg4win 3.1.x is no longer maintained. A technical similar software is the BSI approved [[https://gnupg.com/gnupg-desktop.de.html|GnuPG VS-Desktop®]]; available for Windows and Linux as part of a support contract. == Gpg4win 4.2.x (tba) * Fixing important defects. * Will be released as needed. * New features (that keep the user experience). |
Line 17: | Line 20: |
=== Refactoring Kleopatra | == Ongoing developments |
Line 19: | Line 22: |
See KleopatraHackability. | * 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 21: | Line 29: |
=== Shall we remove Claws-Mail from the installer? | == For each release * Update of third party libraries. * Update of Gnu~P~G and libraries. |
Line 23: | Line 33: |
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. 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. This raises is a more general question: Shouldn't we consider to make the engine (GnuPG and the core libraries) a separate package which can be updated on its own and other packages may install it on the fly? -- [[Werner Koch]] <<DateTime(2014-10-24T19:10:21Z)>> === Additional features from wishlist (Depends on funding and available time) more improvements from the [[../Wishlist|Wishlists]]. |
//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.
The Release Info workboard sometimes has more features for upcoming GnuPG or Gpg4win releases.
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 is no longer maintained. A technical similar software is the BSI approved GnuPG VS-Desktop®; available for Windows and Linux as part of a support contract.
Gpg4win 4.2.x (tba)
- 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.