|
Size: 1244
Comment: update regard claws
|
Size: 1389
Comment: small update, 2.2.3 was released in Nov
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| == 2.2.2 planned within August 2014, may see a beta first. * screenreader ability for kleo |
== 2.2.4 (not scheduled yet) |
| Line 9: | Line 6: |
| * update of gnupg version (2.0.26) and libraries * fix for dll load startup problems with kleopatra on some systems * possibly fix exchange address recognition in gpgOl for outlook 2010/2013 * fix https://bugs.gnupg.org/gnupg/issue1571 (gpg --multifile and wildcards problem on Windows) |
* update of gnupg version and libraries |
| Line 15: | Line 9: |
| == 2.2.3 (?) | == next normal release? maybe 2.3.0 or 3.0.0 |
| Line 17: | Line 11: |
== next normal release? maybe 2.3.0 |
(Not scheduled yet, may depend on available funding). Mid 2015? |
| Line 22: | Line 14: |
| Line 35: | Line 28: |
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]]. |
(For Developers, work in progress)
Potential Roadmap-Planning
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.)
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
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.