|
Size: 887
Comment: Remove issues done with 2.2.2 and move over generic stuff to 2.2.3
|
Size: 346
Comment: Remove released 3.0.3 and link to tracking task for 3.1.0
|
| 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 * 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 |
= Gpg4win Roadmap |
| Line 12: | Line 4: |
| === GnuPG 2.1 integration | == Gpg4win 3.1.0 (Feb / March 2018) |
| Line 14: | Line 6: |
| === Refactoring Kleopatra | [[https://dev.gnupg.org/T3742|See the tracking task in dev.gnupg.org]] |
| Line 16: | Line 8: |
| See KleopatraHackability. | == For each release * Update of third party libraries. * Update of gnupg and libraries. |
| Line 18: | Line 12: |
| === Shall we remove Claws-Mail from the installer? | |
| Line 20: | 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. 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. |
//Additional features from [[../Wishlist|wishlist]] (needs cleanup) depending on funding and available time.// |
Gpg4win Roadmap
Gpg4win 3.1.0 (Feb / March 2018)
See the tracking task in dev.gnupg.org
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.