|
Size: 1581
Comment: 2.2.3 very likely in Nov, 2.3 or 3.0 not planned yet.
|
Size: 2065
Comment: A note about life cycle of gnupg
|
| 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.3 (bugfix release) Very likely in November 2014. |
This page lists the major goals that are worked on. For minor releases only the next release is listed with some more details. |
| Line 7: | Line 6: |
| * Fix gpa and claws on XP, glib defect, rand_so * Fix makeportable [[http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpg4win.git;a=commit;h=619481b224a9704195c456db74073599d01eac0f|commit]] * Fix -vanilla packaging to include gnutls * Update assuan and libgcrypt as intended with 2.2.2 |
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 12: | Line 9: |
| == 2.2.4 * update of third party libraries * update of gnupg version and libraries * (Claws will not be updated, because overall time pressure and lack of help with it.) |
The other focus is improved usability and automation. |
| Line 17: | Line 11: |
| == next normal release? maybe 2.3.0 or 3.0.0 | == Life Cycle |
| Line 19: | Line 13: |
| (Not scheduled yet, may depend on available funding). Mid 2015? === GnuPG 2.1 integration |
* GnuPG 2.2 will be security maintained at least until the end of 2020. GnuPG can be updated individually from Gpg4win. * GnuPG 2.3 will be security maintained at least until the end of 2022. |
| Line 24: | Line 17: |
| === Refactoring Kleopatra | == Gpg4win 3.1.6 (early March 2019) |
| Line 26: | Line 19: |
| See KleopatraHackability. | See the [[https://dev.gnupg.org/T4264|Tracking Task]] |
| Line 28: | Line 21: |
| === Shall we remove Claws-Mail from the installer? | General focus: GpgOL and bugfixes. * More but less secure automation support in GpgOL for OpenPGP (default off) * Basic support to read encrypted subjects in GpgOL * Better attachment handling in GpgOL * Option to decrypt permanently in GpgOL * Update to latest KDE and Qt with performance improvements for Kleopatra. |
| Line 30: | Line 28: |
| 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. |
== Gpg4win 3.2 (late summer 2019) |
| Line 34: | Line 30: |
| 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. |
* GnuPG 2.3 ** Basic ECC Support in GpgSM (including brainpool curves) ** rfc4880bis support with new AEAD methods (EAX, OCB) in GPG * Better support for [[https://wiki.gnupg.org/AutomatedEncryption|automated encryption]] for OpenPGP in GpgOL * Improved archive / folder support in Kleopatra * Usability improvements * S/MIME Adressbook integration for GpgOL |
| Line 37: | Line 38: |
| 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)>> |
== Gpg4win 3.3 (early 2020) * 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. * Additional S/MIME Smartcard support. * (maybe) Rework of GpgEX to have "ZIP Style" explorer integration for encrypted files. * Usability improvements == For each release * Update of third party libraries. * Update of gnupg and libraries. //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.
One focus is improved hardware token support (Yubikey, GnuK-Token) and for the GnuK-Token to improve availability in Europe.
The other focus is improved usability and automation.
Life Cycle
- GnuPG 2.2 will be security maintained at least until the end of 2020. GnuPG can be updated individually from Gpg4win.
- GnuPG 2.3 will be security maintained at least until the end of 2022.
Gpg4win 3.1.6 (early March 2019)
See the Tracking Task
General focus: GpgOL and bugfixes.
- More but less secure automation support in GpgOL for OpenPGP (default off)
- Basic support to read encrypted subjects in GpgOL
- Better attachment handling in GpgOL
- Option to decrypt permanently in GpgOL
- Update to latest KDE and Qt with performance improvements for Kleopatra.
Gpg4win 3.2 (late summer 2019)
- GnuPG 2.3
- Better support for automated encryption for OpenPGP in GpgOL
- Improved archive / folder support in Kleopatra
- Usability improvements
- S/MIME Adressbook integration for GpgOL
Gpg4win 3.3 (early 2020)
- 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.
- Additional S/MIME Smartcard support.
- (maybe) Rework of GpgEX to have "ZIP Style" explorer integration for encrypted files.
- Usability improvements
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.