This tag is used as a reminder to do a release and to collect information pertaining to such a release. It is often useful to add this bug number to release information so that users are able to quickly find solutions for problems with a certain release.
Details
Thu, Jul 31
Wed, Jul 30
Note that 2.5.11 fixes a regression in 2.5.10 regarding the use of notations for 3rd party signatures. See T7743
Mon, Jul 28
Noteworthy changes in version 1.3.2 (2025-07-28)
Fri, Jul 25
Fri, Jul 18
I wonder about GCC 15 preparation for the release. If it's good to have, two patches are needed to apply:
- Cherry-picking rCd5fb7cd9b351: Mark nonstring use cases with __nonstring__ attribute.
- Apply changes of T7721: libgcrypt build-error with gcc-15 on powerpc and alpha
Wed, Jul 16
Mon, Jul 14
Thu, Jul 10
701bd8fe8789a86cd2b7c27254a2ab837ee4fcfa gnupg-2.5.9.tar.bz2 1209dd1dc3cb9e33e3c7857e7f10a7b0fc8d478e gnupg-w32-2.5.9_20250710.tar.xz 0c7814a9ed67c48d0498f42f5a0eeaaf18e29f49 gnupg-w32-2.5.9_20250710.exe
Jun 20 2025
In case of problems with token based cv25519 key, please update to 2.5.8.
Jun 17 2025
Jun 5 2025
We will keep the 1.24 branch for bug fixing. Do you really have a problem with gpgme 2.0? Ist that due to factoring out the c++ and qt bindings? That was actually a long standing request from the KDE community so that they can use their cmake stuff.
I'm wondering whether gpgme v1 will still be supported? Or it will be abandoned from now on.
Jun 3 2025
Jun 2 2025
May 27 2025
May 23 2025
May 20 2025
May 19 2025
Noet that one file is missing in the released tarball; when building for RISC-V please see T7647#201164