-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release of 10.39 #33
Comments
The issue was indeed quickly fixed, but we don't like to put out releases too often, in order to minimize the load on downstream maintainers. It is still less than one month since 10.38 was released, so I am loath to put out another release quite so soon. However, I will ask on the mailing list to see what others think. |
FWIW, I'm holding off uploading a new PCRE2 to Debian in the hopes of a fixed version being available :) |
I think that a bugfix version like 10.38.1 would be best. The "patch" version number clearly indicates there are no new features, only bugfixes. Having a known impacting bug in the latest release won't minimize the load on downstream maintainers, quite the contrary, as they'll get bug reports from their users. |
Not sure about 10.38.1 because we've never put out such release numbers, and in general I'm not really in favour of putting too much meaning into them. There have been plenty of previous releases with no new features. |
OK, there seems to be general support for putting out 10.39. I have just completed working through the pull requests, which are mostly concerned with configuration untidinesses. There seems little point in putting out a Release Candidate, so I will just get on with 10.39 and release it shortly. |
Hi,
i wanted to ask if there is a rough estimation of when 10.39 with the fix is going to be released?
We are currently using PHP 7.4 packaged from Sury (https://deb.sury.org/) which includes libpcre2-8-0 in version 10.38.
Because of the bug some of our regex do not longer work like this one:
It would be super cool if you could release the fix (which seems to be already implemented/merged).
The text was updated successfully, but these errors were encountered: