Repository navigation
Project maintenance status #28
Description
It's been a while since the last release now, and there are some issues I'd like to see fixed (#10 comes to mind). How active is this project?
I think it would make sense to make one release a year, even if there hasn't been any functional changes to the code — that's the release frequency of Python itself, and each new release of patch-ng could update to support (and test) the latest Python version, while dropping support for the version that went end-of-life. (I do think it's time to drop Python 2 support, for example.)
If we decide on some maintenance strategy, I could potentially help out a bit myself here, sending in some pull requests for example.
Activity
uilianries commentedon Aug 1, 2024
Hello @vonschultz ! Thank you for your thoughts! Indeed the project was forked because the upstream looks abandoned and we needed a hotfix for Conan client. It's described it here: https://github.com/conan-io/python-patch-ng?tab=readme-ov-file#why-did-we-fork-this-project
Then was fixed that bug in the past and so far Conan didn't have more trouble related to this package, so it was kept in silence so far, but is not abandoned, because is an active part consumed by Conan.
The maintenance has no schedule so far, but it should release a new patch version soon, trying to fix those current opened issues. Some of them are popping in Python 3.12 and really affecting users.
Releasing once a year would fine, but a new tag can happen anytime when breaking Conan too. I opened the PR #30 to push the CI back on rails, so we can test new PRs. Next, I'll take a look in other issues to see what we can do. Regards.
uilianries commentedon Aug 2, 2024
Closing this issue due the given response. Please, feel free to re-open it in case having more topics to discuss.