Deprecation warning + discussion for standard version successor

[colinscz]

Hi @bcoe

As describe on the pull request here: #907 this project is now deprecated.

There have been some people that offered to fork it and maintain the original purpose of the project, especially for people that cannot depend on Github alone.
From what I can see the version by @TimothyJones

https://github.com/absolute-version/commit-and-tag-version

seems to be the most promising.

Could you please pin this issue at the top of the repository for other people to see the current status?

As of now this repository seems to get additional issues and traction and the deprecation message seems to be not transparent enough for everyone. If a successor has been chosen I think it would be beneficial if the repository is archived or set to read-only mode, that way it's quiet clear that there is no more maintenance done on here. Additionally the successor could be mentioned in the README file. For that I think somebody can provide a PR.

Thanks a lot for the work already done with standard-version!

Cheers

[TimothyJones]

Thanks for the kind words! I've written a bit about the plan for the fork here - the tl;dr is "stay true to the original purpose".

If you feel it is appropriate, I'm happy for a link to my fork to be pinned.

[bcoe]

@TimothyJones @cnschwarz commit-and-tag-version does look very promising.

[mgan59]

I'm little late to the party and didn't see the deprecation notice, but had adopted standard-version tooling for some projects. Appreciate everyones effort in transparency and knowledge sharing here to help in identifying how to proceed with our tooling. 👍🏻 👏🏻

[dtieber]

I'm using standard-version for quite some time now and like it better than the suggested release-please. Is there anyone else who'd be interested in forking and maintaining this project with me?

[TimothyJones]

PRs are very welcome for the fork I mentioned above - unless you're planning to take the project in a different direction, where an alternate fork might make more sense, of course.

Since commit-and-tag-version is almost at 2,000 weekly downloads after only a few months, I think the long term plan has to be to find other maintainers so we can keep it alive together (of course, I'm not going to just give commit access to anyone who asks - there'd be the usual open-source trust building on both sides).

You can read about the direction for the fork here

[dtieber]

Sorry, I completely missed your post. That sounds great!

[TimothyJones]

@bcoe I've made PR #930, which edits the deprecation message to link to the fork that I have been maintaining.

Feel free to accept if/when you feel it is appropriate (or edit the text) - I just wanted to make it easy for you by having the PR ready to go 🙌