c4urself/bump2version

Offer: take on future development with bump-my-version

coordt opened this issue · 8 comments

coordt commented

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.

ekohl commented

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.

  • 👍2
florisla commented

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?

coordt commented
  • 👍2
kdeldycke commented

@coordt is doing an amazing job with his new bump-my-version project.

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 README.md and redirect users to bump-my-version.

What do you think?

  • 👍1
  • 🚀2
kdeldycke commented

I just made a proposition at: #272

kdeldycke commented

I also volunteer to make a final release of bump2version on PyPi if I get the right admin permissions.

I already had to do this kind of work when I renamed my maildir-deduplicate project to mail-deduplicate. See:

kdeldycke commented

Also made a PR to bumpversion: peritus/bumpversion#219 😁

florisla commented

Thanks, this needs to happen.

  • ❤️2