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^W2021-03-31
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^W2021-03-31
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | • gniibe | T4620 no support for multiple (yubikey) smartcards plugged in at the same time | ||
Resolved | • gniibe | T4362 Replace the exec funtions for photoids in gpg by our standard exec functions. | ||
Resolved | • werner | T4713 Bug in get_best_pubkey_byname | ||
Duplicate | • aheinecke | T4989 Gpg4win-4.0.0 | ||
Resolved | • werner | T4702 Deadline for the GnuPG 2.3.0 release | ||
Resolved | • aheinecke | T5273 Release Gpg4win 4.x.x |
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.
We have used this task for more than the usual release info, thus the new title. We will use
T5343 for the 2.3.0 release info.
Things are working out nicely and thus I am convinced that we will miss that whooshing sound the deadline would make as it fly by.