Put a removal / update of claws on the roadmap. Schedule 2.1 for a 3.0 series and move it to "End of 2015"
Note down that we want to move the install location of gpg4win
|Deletions are marked like this.||Additions are marked like this.|
|Line 8:||Line 8:|
|== 2.2.6 (? probably merged into a 3.0 release)
* Remove or Update Claws.
|== 2.2.6 (August 2015)
* Remove Claws from gpg4win.
* Fix gpgsm --gen-key ( https://bugs.gnupg.org/gnupg/issue2043 )
|Line 14:||Line 15:|
|* Move installation location from %~P~R~O~G~R~A~M~F~I~L~E~S%\~G~N~U\~Gnu~P~G to %~P~R~O~G~R~A~M~F~I~L~E~S%\~Gpg4win (To avoids conflicts with other ~Gnu~P~G installers and to use a more logic place to install)|
(For Developers, work in progress)
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?
- Move installation location from %PROGRAMFILES%\GNU\GnuPG to %PROGRAMFILES%\Gpg4win (To avoids conflicts with other GnuPG installers and to use a more logic place to install)
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.