|
Size: 1446
Comment: 2.2.4 planning gets more real triggered by gnupg 2.0.27
|
Size: 783
Comment: Move 3.1.2 and 3.2.0 planned release dates.
|
| 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.) |
== Gpg4win 3.1.2 (KW 24, early June 2018) [[https://dev.gnupg.org/T3925|See the tracking task in dev.gnupg.org]] |
| Line 10: | Line 6: |
| == next normal release? maybe 2.3.0 or 3.0.0 | * Improved handling of unsigned S/MIME mails in GpgOL. (in light of efail) * Outlook 2007 Support removal in GpgOL. * Several Bugfixes, including a crash in GpgOL. |
| Line 12: | Line 10: |
| (Not scheduled yet, may depend on available funding). Mid 2015? | == Gpg4win 3.2.0 (early Fall 2018) |
| Line 14: | Line 12: |
| === GnuPG 2.1 integration | General focus: GpgOL and improved automation. * Defaulting to automated trust model for GpgOL. (more implementation of the [[AutomatedEncryption]] concept) * Automatic encryption selection if keys are available in GpgOL. == For each release * Update of third party libraries. * Update of gnupg and libraries. |
| Line 17: | Line 22: |
| === Refactoring Kleopatra See KleopatraHackability. === Shall we remove Claws-Mail from the installer? 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
Gpg4win 3.1.2 (KW 24, early June 2018)
See the tracking task in dev.gnupg.org
- Improved handling of unsigned S/MIME mails in GpgOL. (in light of efail)
- Outlook 2007 Support removal in GpgOL.
- Several Bugfixes, including a crash in GpgOL.
Gpg4win 3.2.0 (early Fall 2018)
General focus: GpgOL and improved automation.
- Defaulting to automated trust model for GpgOL. (more implementation of the AutomatedEncryption concept)
- Automatic encryption selection if keys are available in GpgOL.
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.