On Mon, Jun 23, 2025 at 1:41 AM Greg Stein <gst...@gmail.com> wrote:
> Holy crap. I didn't realize the spread of broken. ... Yeah, I thought it > was "we're trying". > > Short of a veto, I concur with removing CMake entirely from the serf build > options. It is something that matters to me, and happy to help. > > 72 hours, starting now. FWIW, I don't agree with this 72 hour deadline. AFAICT we have never *released* a release of Serf with the new CMake-based build system. If someone is packaging unreleased stuff from trunk and unleashing it on unsuspecting isers, that is not how it's supposed to be done! But, they are probably doing that because we have not made a proper release in a long time. So, I propose: 1. Let's get a new Serf release out, not necessarily from trunk@HEAD but from some (to be decided) stable branch point, so that packagers will have an official stable codebase to package. If the CMake build isn't ready, choose an earlier branch point or manually exclude it from the release. This is a stopgap release to fix the problem of packagers using unreleased trunk. And: 2. Let's take as long as needed to either fix the CMake build or debate the removal of one or the other build system, without a 72 hour imposed timeframe. I personally need more than 72 hours to study this issue and provide my input, and I'm sure others will concur, especially given that this project normally has a slower pace. Thank you, Nathan
