Create v0.17.1 release with rnp_signature_get_features

[ronaldtse]

Description

Source: 74b70af#commitcomment-138429079

From @kaie :

Would the RNP team be willing to create a v0.17.1 release, based on the former v0.17.0 release, which adds this feature (commit)? This could allow those Linux distributions which ship RNP separately, to pick up this feature easily, and allow Thunderbird to make use of the new API in its current stable 115.x release.

[ni4]

@ronaldtse I think adding #2180 contents to release would be good idea?

[ronaldtse]

Agree with @ni4 . Thanks!

[ni4]

...also required to pick CI updates + Botan 3 support + OpenSSL 3.0 fixes (see #2190). @kaie don't you mind these changes? They should not have an impact for already existing behaviour and improve compatibility.

[kaie]

Hi @ni4 - If your intention is to include correctness fixes, plus compatibility fixes for a wider set of build environments and libraries, that makes sense to me. I'd suggest that you ask yourself: Would any long term support environment, that currently ships Thunderbird 115.x, and is willing to take updates for it, but that also wants to minimize the amount of fixes it takes, be fine with your included changes? For example, stable Debian or RHEL? I'd exclude changes those stable environments might be unwilling to bring in.

[kaie]

CC @jfx2006

[ni4]

@kaie Yeah, this is mostly for systems which updated to Botan 3/latest OpenSSL 3.0 (like #2159). For LTE nothing would change as they would continue to use older Botan/OpenSSL packages.

[kaie]

Hello, do you expect this to happen very soon, or are you blocked?

[ni4]

@kaie The only blocker was this thing : #2209 , however now it seems to be not of that importance as it is easily solvable by maintainers and mostly related to the v0.17.0.

[ni4]

Finally release is published: https://github.com/rnpgp/rnp/releases/tag/v0.17.1

[kaie]

Thank you. FYI, the release page also says function set_features was added, I assume that's a mistake.