|
Size: 1446
Comment: 2.2.4 planning gets more real triggered by gnupg 2.0.27
|
Size: 1415
Comment: 2.2.4 is out. Plan 2.2.5 This also removes the libpng update as the rationale for this is unclear to me.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| == 2.2.4 (Q1 2015) | == 2.2.5 (Q2 2015) |
| Line 6: | Line 6: |
| ** libpng to 1.2.5 (probably no relevant changes for Gpg4win) * update of gnupg to 2.0.27 and libraries |
* update of gnupg and libraries |
| Line 11: | Line 10: |
| Line 15: | Line 14: |
| * Probably something for a 3.0 release |
(For Developers, work in progress)
Potential Roadmap-Planning
2.2.5 (Q2 2015)
- update of third party libraries.
- update of gnupg 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
- Probably something for a 3.0 release
Refactoring Kleopatra
See KleopatraHackability.
Shall we remove Claws-Mail from the installer?
Rationale: Claws-Mail maintains 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 2014-10-24 19:10:21
Additional features from wishlist
(Depends on funding and available time) more improvements from the Wishlists.