How are GitHub releases, version tags, and release cycles handled?

[xhluca]

It seems that only the initial 0.1.0 version was released on PyPi, and the version was not tagged on GitHub. There's also no release notes on GitHub.

My questions are:

1. Will each release be tagged on GitHub (with possibly release notes) before being released to PyPi?
2. What will be the release cycles (will each new feature warrant a minor version bump, or do you plan to bundle all changes to be released every X months)?
3. Will this library be backward compatible before reaching version 1.0, and will there be feature deprecation warnings and/or two-minor-version deprecation cycles?

Related: #16

If automating pypi release via GitHub release sounds interesting, I think this is a good place to start: https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#publishing-to-package-registries

[MXueguang]

Hi @xhluca, Thanks for the suggestion. we do need to handle the releasing process better. thanks for sharing the link, i'll take a look