-
Notifications
You must be signed in to change notification settings - Fork 132
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
Offer: take on future development with bump-my-version #268
Comments
I can't speak for other maintainers, but I don't have the time to work on bump2version at all anymore. I feels bad, but it's the reality. So for me it's perfectly ok to promote something else. This is perhaps more up to @c4urself, but I think we should consider adding more maintainers. Or even merge your changes as a new major version. That saves the community of manually finding a replacement and provide a regular upgrade path. |
Hi @coordt, this is great to see. Starting with a clean sheet was the best option in my opinion. How far did you go in ensuring backwards compatibility? Are all the old unit tests covered? |
I ported over all the old unit tests that made sense. Some of the unit
tests didn't make sense with the new code.
As far as I can tell, it _should_ be 100%. Would need to have some
verification by outside parties.
…On Mon, Apr 24, 2023 at 4:48 AM Floris Lambrechts ***@***.***> wrote:
Hi @coordt <https://github.com/coordt>, this is great to see.
Starting with a clean sheet was the best option in my opinion.
How far did you go in ensuring backwards compatibility? Are all the old
unit tests covered?
—
Reply to this email directly, view it on GitHub
<#268 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAXQSRX7I6UFVMYQSNFP5LXCZD7BANCNFSM6AAAAAAXBDNDIA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@coordt is doing an amazing job with his new It is actively maintained, modern, fixes lots of issues that were pending for the last 3~4 years and already adds features that were requested as far back as the original bumpversion project. I propose to add a warning to bump2version's What do you think? |
I just made a proposition at: #272 |
I also volunteer to make a final release of I already had to do this kind of work when I renamed my
|
Also made a PR to |
Thanks, this needs to happen. |
Hello,
I made a fully backward-compatible refactor of this code at bump-my-version in hopes of making bugs easier to fix and new features easier to implement.
Since it seems active development has waned here (no judgment!) I would offer that project as its spiritual successor.
Please mention it in the README, if you like.
The text was updated successfully, but these errors were encountered: