In a discussion we decided that we need a deadline for GnuPG 2.3.0 so that we finally release it.
This deadline is the 2019-12-20.
In a discussion we decided that we need a deadline for GnuPG 2.3.0 so that we finally release it.
This deadline is the 2019-12-20.
Status | Assigned | Task | ||
---|---|---|---|---|
Open | werner | T4417 Work needed for gnupg 2.3 | ||
Resolved | gniibe | T4362 Replace the exec funtions for photoids in gpg by our standard exec functions. | ||
Testing | gniibe | T4620 no support for multiple (yubikey) smartcards plugged in at the same time | ||
Resolved | gniibe | T4713 Bug in get_best_pubkey_byname | ||
Open | aheinecke | T4989 Gpg4win-4.0.0 | ||
Open | werner | T4702 Release GnuPG 2.3.0 |
In a discussion we decided that we need a deadline for GnuPG 2.3.0 so that we finally release it.
This deadline is the 2019-12-20.
Due Date: Sep 29 2020, 6:00 PM
It seems both of these due dates have passed and it's been a year since the first. Could a new deadline be chosen? I understand the need to take one's time, but a deadline would help inform one's decision, e.g. whether to hold out for fixes in GnuPG 2.3 or build a beta locally for one's needs.
We are hoping to have at least a beta release soon with gcrypt 1.9 that we can put in a Gpg4win-4 beta.