Re: 1.14.4 release
On Mon, Mar 11, 2024 at 8:55 AM Stefan Sperling wrote: > > On Sun, Mar 10, 2024 at 07:59:38PM -0400, Nathan Hartman wrote: > > There is at least a week before I can begin working on it, so there is > > time for the dev community to respond. > > I will be around to help with testing/signing. Thanks for picking this up! Likewise. +1 -- Johan
Re: 1.14.4 release
On Sun, Mar 10, 2024 at 07:59:38PM -0400, Nathan Hartman wrote: > There is at least a week before I can begin working on it, so there is > time for the dev community to respond. I will be around to help with testing/signing. Thanks for picking this up!
Re: 1.14.4 release
Den mån 11 mars 2024 kl 00:59 skrev Nathan Hartman : > Hi all, > > Unfortunately the recently released 1.14.3 contains a new regression > [1] that may crash the SWIG python bindings in repos.replay() under > some conditions. > > It is already fixed on trunk in r1915316 and backported to the 1.14.x > branch in r1915338. > > There was a discussion [2] about issuing a 1.14.4 release to fix it, > as there is no known workaround for Python users other than patching > some code or downgrading to 1.14.2. > > I volunteer to RM the 1.14.4 release. Of course, if anyone else would > like to RM, feel free to speak up. I'll be happy to assist. > > My tentative plan is to try to reproduce the issue and verify the fix, > and then proceed with the normal patch release process. > > There is at least a week before I can begin working on it, so there is > time for the dev community to respond. > > Meanwhile, there are two proposed backports in STATUS that might merit > some consideration: > * r1890223 et al "Support building on Win64/ARM64" > * r1914222 "Improve help message for svnmucc PUT" > > Each needs one additional vote to make it into the release. > > References: > > [1] 30 Jan 2024 mail to dev@ titled > "[patch] publication for the fix of swig-py bug fixed in r1915316" > archived at: > https://lists.apache.org/thread/ds24b6w446horzvl4n8y6dqrfl3jb6s4 > > [2] 1 Feb 2024 mail to dev@ titled > "Re: svn commit: r1915317 - /subversion/branches/1.14.x/STATUS" > archived at: > https://lists.apache.org/thread/571hk0nykvrorx9wq0r0lyylpjj42qdw > > Thanks, > Nathan > That sounds great Nathan, thank you for following up on this! I'm travelling this week with limited amount of time but I will do my best to make room next week. Cheers, Daniel
1.14.4 release
Hi all, Unfortunately the recently released 1.14.3 contains a new regression [1] that may crash the SWIG python bindings in repos.replay() under some conditions. It is already fixed on trunk in r1915316 and backported to the 1.14.x branch in r1915338. There was a discussion [2] about issuing a 1.14.4 release to fix it, as there is no known workaround for Python users other than patching some code or downgrading to 1.14.2. I volunteer to RM the 1.14.4 release. Of course, if anyone else would like to RM, feel free to speak up. I'll be happy to assist. My tentative plan is to try to reproduce the issue and verify the fix, and then proceed with the normal patch release process. There is at least a week before I can begin working on it, so there is time for the dev community to respond. Meanwhile, there are two proposed backports in STATUS that might merit some consideration: * r1890223 et al "Support building on Win64/ARM64" * r1914222 "Improve help message for svnmucc PUT" Each needs one additional vote to make it into the release. References: [1] 30 Jan 2024 mail to dev@ titled "[patch] publication for the fix of swig-py bug fixed in r1915316" archived at: https://lists.apache.org/thread/ds24b6w446horzvl4n8y6dqrfl3jb6s4 [2] 1 Feb 2024 mail to dev@ titled "Re: svn commit: r1915317 - /subversion/branches/1.14.x/STATUS" archived at: https://lists.apache.org/thread/571hk0nykvrorx9wq0r0lyylpjj42qdw Thanks, Nathan
