|
Size: 1504
Comment:
|
Size: 706
Comment: Start on 3.0.2 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.3 (bugfix release) Planned within October 2014. |
== Gpg4win 3.0.2 (Dec 2017 or Q1 2018) * Improvements for Kleopatras File Encrypt / Sign dialog. * Making Update Notifications enabled by default (allow-version-check). * GpgOL ** Fixing PGP/INLINE (no-mime) deprecated compatibility option. |
| Line 7: | Line 9: |
| * 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 |
== Gpg4win 3.0.x (Q4 2017/Q1 2018) |
| Line 12: | Line 11: |
| == 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.) |
* contains security and bug fixes |
| Line 17: | Line 13: |
| == next normal release? maybe 2.3.0 | == Gpg4win 3.1 (Q1 2018) * GpgOL ** Remove support for Outlook 2003/2007 (Microsofts' Extended Support ends 2017-12-31). * more features ... == For each release * Update of third party libraries. * Update of gnupg and libraries. |
| Line 20: | Line 24: |
| === GnuPG 2.1 integration === 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|wishlist]] (needs cleanup) depending on funding and available time.// |
Gpg4win Roadmap
Gpg4win 3.0.2 (Dec 2017 or Q1 2018)
- Improvements for Kleopatras File Encrypt / Sign dialog.
- Making Update Notifications enabled by default (allow-version-check).
- GpgOL
- Fixing PGP/INLINE (no-mime) deprecated compatibility option.
Gpg4win 3.0.x (Q4 2017/Q1 2018)
- contains security and bug fixes
Gpg4win 3.1 (Q1 2018)
- GpgOL
- Remove support for Outlook 2003/2007 (Microsofts' Extended Support ends 2017-12-31).
- more features ...
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.