On 31.03.2020 18:53, Justin Erenkrantz wrote: > Hi all! > > I hope that everyone is doing as well as they can in these times. > > I'd like to do a sweep of STATUS and do a final 1.3.x release that captures > the relevant build system and test fixes. I'll try to test out the Visual > Studio fixes that are pending for 1.3.x; I have VS 2019 here, so I may try > to see if there are additional fixes required for VS 2019 as well. > > I also see the changes for OpenSSL/LibreSSL in 1.3.x STATUS - it looks like > the OpenSSL 1.1.x patches that were already merged in 1.3.9 obsolete that > branch; but, I'm open to whether we want to do something with LibreSSL as > well. Thoughts? > > What do folks think about cutting a 1.4.x release as well? I see that > there are a number of good bits there that have yet to see a formal > release, so I'm open to also cutting a 1.4.0 release too over the next few > weeks. > > Once I have the tree ready for 1.3.x and 1.4.x, I'll ask for votes. I'm > optimistic that we can get a quorum of 3 people to cut a release. =)
Thanks, Justin. I don't know if we need another 1.3.x release, given that 1.4 will be API compatible and has more robust OpenSSL 1.1.x and LibreSSL support. For 1.4, we have (had? not quite up to date here...) the proposed Python 3 fixes which I'd treat as mandatory. The CMake build doesn't support BROTLI and GSSAPI yet, but that's not a blocker for the release IMO. A bulk merge to the 1.4.x branch would make sense, too; I don't think we have to go through STATUS for the minor improvements currently on trunk. -- Brane
