I suggest to make the following text changes for the VSD versions only:

A bunch more improvements (for gpg4win 5.0):

Result of first iteration sorting the tickets by Features, Bug Fixes, and different reasons why they are not relevant for the release notes of 4.4.0

Noteworthy changes in Version 4.4.0 (unreleased)
------------------------------------------------

This doesn't need to be verified with VSD 3.3 after it was verified with Gpg4win.

This was fixed in gpgme and is therefore automatically in VSD 3.3

Ready for testing. Note that you also need gpgme master.

We should show the original algorithm name instead of "Unknown algorithm" if we don't have a pretty name for it. This way we can show the Kyber algorithms without adding pretty names for them. T7397: Kleopatra: Support Kyber generation

This might fix the issue https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpg4win.git;a=commit;h=cf13e915581ca32e05e229cc54ef8e35753128e0

This fix is also in VSD 3.3

This is included in test installers since some time already.

This change is also used for VSD 3.3

Gpg4win-Beta-75: works

Name of the window is now "GnuPG Configuration Overview" and "gpgconf -X" is preselected and executed in the window.

Works, you now get an error message that the card can not be found.

This has been backported for VSD 3.3 and Gpg4win

This symptom can be explained by the nPth bug of T7386.

I guess it's now ready for testing

All changes have been backported for VSD 3.3

FWIW, there is some code in gpa which uses the event counter. It was introduced with
rGPA936825b4b994cdf5900fc987abd9be7889989627

With Gpg4win-Beta-75+

I agree, this is done, follow up Tasks will get new tickets

This seems to be QWizard-specific behavior. One more reason to port away from that

Gpg4win-Beta-75:
This works in principle. That some TCOS cards seem to have a high chance of causing a hang-up of scdaemon is not Kleopatra's fault and that issue is tracked somewhere else. I'm not sure where, probably T7378 or T7379?

Should be ready for testing

Backported for VSD 3.3

This bugfix shall be backported for VSD 3.3 as discussed with ebo

Latest changes backported for VSD 3.3

Backported for VSD 3.3

And backported for VSD 3.3.

Fixed.

Gpg4win-Beta-75:
Works. The filters are also applied to groups now and match groups even if not all certificates in them conform to the filter rule.
Tested with OpenPGP ans S/MIME filters.

For the record, I add the info here too (was: just in xmpp).

And to make commands run only once when Enter is pressed: https://invent.kde.org/pim/kleopatra/-/merge_requests/320

Hmm, calling QProcess::setStandardInputFile(QProcess::nullDevice()) before start() may be even better than calling closeWriteChannel() after start().

On the Cli, gpg does not give an error but an info message informing that the subkey already exists so there is no error message for Kleopatra to act on.

Fix for the crash https://invent.kde.org/pim/kleopatra/-/merge_requests/318

It works in Gpg4win-Beta-75 to add the ADSK to more than one Key.

The QProcesses we start should be configured with closed stdin so that the started process don't hang waiting for input, e.g. by calling closeWriteChannel() immediately after start(). Or by calling start() with QIODeviceBase::ReadOnly, but, sadly, the documentation of QProcess doesn't document what effect that has.

Gpg4win-Beta-75, works:

Gpg4win-Beta-75: This is in principle ok. Even adding further commands to
C:\Program Files (x86)\Gpg4win\etc\xdg\kleopatradebugcommandsrc works:

@ebo @ikloecker Let me explain my thoughts. If you have time, please help me doing some tests in your environment.

This shell script running gpg-connect-agent should run successfully:

For Beta-75 it looks similar judging from my first tries.

Gpg4win-Beta-75:
Looks good, I see no "EXCEPTION_ACCESS_VIOLATION" after quitting any more.
Instead only: "process started at 14:11:03.007 has terminated with exit code 0"

Gpg4win-Beta-75: This does not work.

Gpg4win-Beta-75:
Checked the property details of some files in "Progams (X86)" and found several without product name, E.g. libgpg-error-0.dll and other dlls located at C:\Program Files (x86)\GnuPG\bin.
Or gpgolconfig.exe at C:\Program Files (x86)\Gpg4win\bin and the examble from above, libKF5JobWidgets.dll, shows no product name either.

Gpg4win-Beta-75: Symbol is there.