I have a proposal regarding versioning, changelog and commits we do to the repo. For versioning, I propose Semantic Versioning[0] (BiT might be already using this). It provides a well-defined way, complete with support for intermediate/WIP releases. BiT’s versioning already fits this, and we can do things like 1.4.4beta1 to denote things are not pretty stable yet. On the commit side, I find Conventional Commits[1] useful. It requires some mental adjustment, but it also forces good development practices by dividing big commits and limiting one fix per commit. This brings commit granularity, transparency and discipline. I apply it to my own projects, and I like it. On the Changelog side, we can use a tool like Git Cliff[2], which creates changelogs from git commits automatically. I didn’t have a chance to use it, but it provides a GitHub action, so we can use this at infrastructure level, automatically. Implementing these ways and adding such discipline may reduce our load in the long term, and make project more sustainable IMHO. We can codify this into a CONTRIBUTING.md file. Moreover, even if we use Git-cliff via GH, it can be deployed independently, so we’re not tied to GitHub in the longer run. Of course, as always, comments are very welcome, Hope these ideas makes sense, Cheers, H. [0]: https://semver.org [1]: https://www.conventionalcommits.org/en/v1.0.0/ [2]: https://github.com/orhun/git-cliff
On 9 Sep 2022, at 23:50, (by way of c.buhtz@posteo.jp) <buhtz@posteo.de> wrote:
On 2022-09-09 22:45 Michael Büker <foss@michael-bueker.de> wrote:
If you find that script, let me know :)
I think I meant this https://github.com/bit-team/backintime/blob/master/updateversion.sh _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: hakan@bayindir.org