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
Details
Description
Mon, Nov 23
Mon, Nov 23
Released on 2020-11-18
werner set Version to 2.2.25 on T5140: Release GnuPG 2.2.25.
Note that if you run into problems with a smartcard you should run "gpg --card-status" once. GUI frontends usually do that and this is the reason why this regression was not detected. Will be fixed in 2.2.25 (T5140).
werner moved T5140: Release GnuPG 2.2.25 from Backlog to Ready for release on the gnupg (gpg22) board.
Wed, Nov 18
Wed, Nov 18
Tue, Nov 17
Tue, Nov 17
werner added a comment to T5045: Release GnuPG 2.2.23.
A fix has been released; see T5052.
werner set Version to 2.2.24 on T5052: Release GnuPG 2.2.24.
Thu, Nov 12
Thu, Nov 12
Wed, Nov 11
Wed, Nov 11
3.1.12 was released on 2020-07-24.
Oct 28 2020
Oct 28 2020
werner added a comment to T5045: Release GnuPG 2.2.23.
Unfortunately this new release has a regression affecting users with non-ascii account names. See T5098.
Oct 23 2020
Oct 23 2020
werner updated the task description for T5113: Release Libgcrypt 1.8.7.
Sep 4 2020
Sep 4 2020
See
https://lists.wald.intevation.org/pipermail/gpg4win-announce/2020-September/000089.html
for the fixed Gpg4win 3.1.13
Sep 3 2020
Sep 3 2020
werner updated the task description for T5045: Release GnuPG 2.2.23.
werner set Version to GnuPG 2.2.23 on T5045: Release GnuPG 2.2.23.
Sep 2 2020
Sep 2 2020
werner added a comment to T5030: Release GnuPG 2.2.22 .
A bug was reported against this version which could happen also to older versions of GnuPG 2.2. In case of a crash please apply the patch over at rG8ec9573e57866dda5efb4677d4454161517484bc or wait for 2.2.23
werner added a commit to T5030: Release GnuPG 2.2.22 : rG8ec9573e5786: gpg: Fix segv importing certain keys..
Aug 31 2020
Aug 31 2020
werner added a comment to T5030: Release GnuPG 2.2.22 .
As a workaround please run
werner added a comment to T5030: Release GnuPG 2.2.22 .
There seems to be a problem with Gnuk and thus Nitrokey tokens with 2.2.22. We are investigating this. See T5039.
Aug 27 2020
Aug 27 2020
werner set External Link to https://lists.gnupg.org/pipermail/gnupg-announce/2020q3/000447.html on T5030: Release GnuPG 2.2.22 .
Aug 24 2020
Aug 24 2020
werner closed T5031: Release Libgpg-error 1.39, a subtask of T5030: Release GnuPG 2.2.22 , as Resolved.
Release done.
werner updated the task description for T5031: Release Libgpg-error 1.39.
Aug 22 2020
Aug 22 2020
Aug 20 2020
Aug 20 2020
werner closed T4997: 2.2.21 breaks passphrase-repeat and password checking, a subtask of T4897: Release GnuPG 2.2.21, as Resolved.
Jul 17 2020
Jul 17 2020
werner updated the task description for T4996: Release GPGME 1.14.0.
werner added a subtask for T4897: Release GnuPG 2.2.21: T4997: 2.2.21 breaks passphrase-repeat and password checking.
Jul 16 2020
Jul 16 2020
aheinecke added a parent task for T4789: Gpg4win-3.1.12: T4988: Kleopatra key generation does not use default algorithms 3072 but 2048.
Jul 14 2020
Jul 14 2020
werner added a comment to T4897: Release GnuPG 2.2.21.
It turns out that a test case in GPGME fails with that version. This is due to a regression I introduced in the passphrase repetition code for symmetric encryption. This will be fixed with the next GnuPG version; in the meantime you may use the patch F1646254.
Jul 9 2020
Jul 9 2020
werner edited subtasks for T4989: Gpg4win-4.0.0, added: T4702: Release GnuPG 2.3.0; removed: T4990: Release GnuPG 2.3.0.