|
Size: 1719
Comment: Section that links the wishlist
|
Size: 800
Comment: 3.1.1 will be released next week.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| (For Developers, work in progress) = Potential Roadmap-Planning == 2.2.3 (bugfix release) Very likely in November 2014. * 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 == 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.) == next normal release? maybe 2.3.0 or 3.0.0 (Not scheduled yet, may depend on available funding). Mid 2015? === GnuPG 2.1 integration |
= Gpg4win Roadmap |
| Line 24: | Line 4: |
| === Refactoring Kleopatra | == Gpg4win 3.1.1 (KW 17 2018) |
| Line 26: | Line 6: |
| See KleopatraHackability. | [[https://dev.gnupg.org/T3899|See the tracking task in dev.gnupg.org]] |
| Line 28: | Line 8: |
| === Shall we remove Claws-Mail from the installer? | Highlights: * GPGSM: Fixed several CRL handling issues. * GpgOL: Fixed a regression when decrypting signed / encrypted mails in a specific format, when the signers key was not available. * Fixes for mkportable |
| Line 30: | Line 13: |
| 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.0 (Summer 2018) |
| Line 34: | Line 15: |
| 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. |
* File support for Kleopatras notepad. (Read / Write of simple PGP/MIME and S/MIME messages) * Defaulting to automated trust model for GpgOL. (more implementation of the [[AutomatedEncryption]] concept) |
| Line 37: | Line 18: |
| 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)>> |
== For each release * Update of third party libraries. * Update of gnupg and libraries. |
| Line 40: | Line 22: |
| === Additional features from wishlist | |
| Line 42: | Line 23: |
| (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
Gpg4win 3.1.1 (KW 17 2018)
See the tracking task in dev.gnupg.org
Highlights:
- GPGSM: Fixed several CRL handling issues.
- GpgOL: Fixed a regression when decrypting signed / encrypted mails in a specific format, when the signers key was not available.
- Fixes for mkportable
Gpg4win 3.2.0 (Summer 2018)
- File support for Kleopatras notepad. (Read / Write of simple PGP/MIME and S/MIME messages)
- Defaulting to automated trust model for GpgOL. (more implementation of the AutomatedEncryption concept)
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.