Think about a v9.1 release?

[James Ralston]

I gently echo the requests for a 9.02 release.

Without commit c9831b38, OpenConnect does not support Pulse VPN
servers 9.1R16 or later; both --protocol=nc and --protocol=pulse are
inoperable:

https://gitlab.com/openconnect/openconnect/-/issues/472
https://gitlab.com/openconnect/openconnect/-/commit/c9831b382c7839682b3f1ea0a7f950e6cb55d5e8

We are a RHEL shop, and the EPEL project provides OpenConnect RPMs for
RHEL, but EPEL didn’t cherry-pick c9831b38 into their 9.01 package
builds.

This past weekend, our network team upgraded our Pulse server to
9.1R16 over the past weekend—which meant on Monday morning all Linux
OpenConnect users were locked out of the VPN. I built and packaged
openconnect HEAD, but then we had a chicken-and-the-egg problem where
the folks who needed the upgraded package couldn’t get it because you
had to be connected to the VPN to access the package repository
server. (I finally ended up emailing the RPM package to personal email
addresses.)

I could file a Bugzilla against EPEL to cherry-pick commit c9831b38
into their 9.01 package builds, but the best solution for the Pulse
9.1R16 compatibility issue would be to cut a 9.02 release from the
current HEAD. Please?