Den lör 9 maj 2026 kl 11:26 skrev <[email protected]>: > > Author: dsahlberg > Date: Fri May 8 19:20:08 2026 > New Revision: 1933963 > > Log: > In branches/1.3.x, vote for r1933327 > > Modified: > serf/branches/1.3.x/STATUS > > Modified: serf/branches/1.3.x/STATUS > ============================================================================== > --- serf/branches/1.3.x/STATUS Fri May 8 18:55:21 2026 (r1933962) > +++ serf/branches/1.3.x/STATUS Fri May 8 19:20:08 2026 (r1933963) > @@ -35,6 +35,12 @@ Candidate changes: > this point for the 1.3.x branch > - Seems to only be required for LibreSSL, not OpenSSL) > > + * r1933327 > + Make sure we can build with VS 2026 > + Votes: > + +1: dsahlberg > + > + > Veto-blocked changes: > ===================== > >
Since Serf is currently not possible to build with VS 2026, I would like to see a new release of the 1.3 line as soon as possible. In addition to this, there is only one more change from 1.3.10: r1926677 (r1926676 in trunk), changing file permissions in the distributed tarball from 666 to 644. Based on this it should be a really low risk release. I can volunteer to RM this one (my first!). I don't think we have a formal backport policy but this is a change only affecting build system and borrowing from Subversion this could go in with two +1. If someone could do this I will start preparing the release. Cheers, Daniel PS. The commit notification was stuck in mailing list moderation. I have used webmod to do "accept+allow" on all e-mails from [email protected] for both dev@ and private@.
