|
Size: 1389
Comment: small update, 2.2.3 was released in Nov
|
Size: 1191
Comment: Put 2.3.2 on the roadmap
|
| 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 (not scheduled yet) * 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.) |
== 2.3.2 (June 2016) * Fix for S/MIME sent mails behavior in GpgOL if S/MIME support is disabled. * Fix for Denial of Service in Libksba 1.3.4 |
| Line 9: | Line 7: |
| == next normal release? maybe 2.3.0 or 3.0.0 | == 3.0 Testversions Compare to [[Gpg4win/Testversions|current testversions]]. == 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 |
| Line 11: | Line 14: |
| (Not scheduled yet, may depend on available funding). Mid 2015? | == Gpg4win 3.0-testversion* (Q1-Q4 2016) * stabilize improvements in Kleopatra, GpgOL and GnuPG * Development platform improvements, to keep Gpg4win maintainable and ready for the future. ** Build Kleopatra, Qt5 all from source with the same (cross) compiler on a modern Debian GNU/Linux system. |
| Line 13: | Line 19: |
| === GnuPG 2.1 integration | == 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 == For each release * Update of third party libraries. * Update of gnupg and libraries. |
| Line 16: | Line 30: |
| === 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]] depends on funding and available time.// |
Gpg4win Roadmap
2.3.2 (June 2016)
- Fix for S/MIME sent mails behavior in GpgOL if S/MIME support is disabled.
- Fix for Denial of Service in Libksba 1.3.4
3.0 Testversions
Compare to current testversions.
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.0-testversion* (Q1-Q4 2016)
- stabilize improvements in Kleopatra, GpgOL and GnuPG
- Development platform improvements, to keep Gpg4win maintainable and ready for the future.
- Build Kleopatra, Qt5 all from source with the same (cross) compiler on a modern Debian GNU/Linux system.
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
For each release
- Update of third party libraries.
- Update of gnupg and libraries.
Additional features from wishlist depends on funding and available time.