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

How to track the current stable version? #5

Open
jorgkv opened this issue Feb 18, 2021 · 2 comments
Open

How to track the current stable version? #5

jorgkv opened this issue Feb 18, 2021 · 2 comments

Comments

@jorgkv
Copy link
Contributor

jorgkv commented Feb 18, 2021

Open for discussions

  • Use a v1.0.0 git tag?
  • Develop new features in a develop branch?
@jorgkv
Copy link
Contributor Author

jorgkv commented Feb 18, 2021

I think the latest version we release to PyPI should reflect what is currently in the master branch? So we should probably add a v1.0.0 git tag to easily get back to the current state later.

@Jakidxav
Copy link
Contributor

@widforss @jorgkv The stable branch that is going into PyPI now has a git tag of v1.0.0. I have created a development branch for the current list of issues that would introduce breaking changes to scripts currently using the codebase.

Please create your own personal branch from development and submit changes via pull requests so that we can begin work on v2.0.0.

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