Hi, To try to figure out how we can move this forward, today I started running through the process in README.release. I filed my (very, very modest) work as #880 <https://github.com/cyrusimap/cyrus-sasl/pull/880>, which gets some of the trivial things completed, but can't really be turned into a release candidate.
First off, the code changes since v2.1.18 are in an unknown state. I can't possibly "just ship". But if we had a perfect oracle of code quality who said it was good to go, we'd need to know *how* to ship this… so I wanted to answer that. The main problem for me was that "distcheck" failed. It complained about automake things, so I punted this to some colleagues. Matthew Horsfall filed #881 <https://github.com/cyrusimap/cyrus-sasl/pull/881>, trying to get distcheck in a passing state. GitHub user flowerysong mentioned their PR #855 <https://github.com/cyrusimap/cyrus-sasl/pull/855>, which may address these problems in the same or other ways — I haven't looked yet! They do add a workflow for automated testing, which would be great. I've reached out to Quanah, who did the 2.1.28 release, and who has been much more active in the project than I have, to help get a further sense of the state of things. I'm at IETF this week, so I'm not sure I'll make much more progress on this, but it remains high on my to-do list. -- rjbs ------------------------------------------ Cyrus: SASL Permalink: https://cyrus.topicbox.com/groups/sasl/T4bfea6b1dc01d766-M2b31b98400470ff8dbd9aaf4 Delivery options: https://cyrus.topicbox.com/groups/sasl/subscription
