|
Size: 943
Comment:
|
Size: 1406
Comment: Plan 2.2.6
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| (For Developers, just an initial stub, work in progress) | (For Developers, work in progress) |
| Line 4: | Line 4: |
| == 2.2.2 | == For each release * Update of third party libraries. * Update of gnupg and libraries. |
| Line 6: | Line 8: |
| * screenreader ability for kleo * update of third party libraries * update of gnupg version and libraries * fix for dll load startup problems with kleopatra on some systems * possibly fix exchange address recognition in gpgOl for outlook 2010/2013 |
== 2.2.6 (August 2015) * Remove Claws from gpg4win. * Fix gpgsm --gen-key ( https://bugs.gnupg.org/gnupg/issue2043 ) == 3.0.0 (Not scheduled yet, may depend on available funding. End 2015?) * GnuPG 2.1 integration * Kleopatra based on KDE Framework 5? |
| Line 12: | Line 16: |
| === Refactoring Kleopatra See KleopatraHackability. |
|
| Line 21: | Line 29: |
| 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)>> |
|
| Line 22: | Line 32: |
| == next normal release? maybe 2.3.0 | === Additional features from wishlist |
| Line 24: | Line 34: |
| === GnuPG 2.1 integration | (Depends on funding and available time) more improvements from the [[../Wishlist|Wishlists]]. |
(For Developers, work in progress)
Potential Roadmap-Planning
For each release
- Update of third party libraries.
- Update of gnupg and libraries.
2.2.6 (August 2015)
- Remove Claws from gpg4win.
- Fix gpgsm --gen-key ( https://bugs.gnupg.org/gnupg/issue2043 )
3.0.0 (Not scheduled yet, may depend on available funding. End 2015?)
- GnuPG 2.1 integration
- Kleopatra based on KDE Framework 5?
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.