Skip to content
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

Consider bumping version to 1.0.0 #22

Open
salcode opened this issue Mar 15, 2024 · 3 comments
Open

Consider bumping version to 1.0.0 #22

salcode opened this issue Mar 15, 2024 · 3 comments

Comments

@salcode
Copy link
Contributor

salcode commented Mar 15, 2024

Since this plugin is being used in production environments, I think we should consider bumping the version to 1.0.0

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backward compatibility, you should probably already be 1.0.0.

From How do I know when to release 1.0.0? on semver.org

@tw2113
Copy link
Member

tw2113 commented Mar 15, 2024

Can definitely consider next release. Perhaps if we have time on like a 5FTF or so, we can brainstorm for something that could bolster a 1.0.0 release number as well

@salcode
Copy link
Contributor Author

salcode commented Mar 15, 2024

Just to be clear, I'm not pitching any new features (or really any changes at all). I just think we should have this tagged at 1.0.0

In my opinion, it is acceptable to jump from 0.3.0 to ``1.0.0` without introducing any changes (but I'm happy to discuss this further).

@tw2113
Copy link
Member

tw2113 commented Mar 15, 2024

I definitely get what you're saying and everything, but I'm also wondering if we can somehow give this plugin some new love at the same time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants