|
Size: 779
Comment: initial version with some roadmap planning
|
Size: 887
Comment: Remove issues done with 2.2.2 and move over generic stuff to 2.2.3
|
| 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: |
| == next minor release? maybe 2.2.2 | == 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.) |
| Line 6: | Line 9: |
| === screenreader ability for kleo | == next normal release? maybe 2.3.0 |
| Line 8: | Line 11: |
| === update on some libraries, e.g. image format libraries | |
| Line 10: | Line 12: |
| === GnuPG 2.1 integration === Refactoring Kleopatra See KleopatraHackability. |
|
| Line 19: | Line 26: |
== next normal release? maybe 2.3.0 |
(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
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.