[simple-romp] Semantic versioning & releases
See original GitHub issueIt seems, that the version of simple-romp
might be wrong:
https://github.com/Arthur151/ROMP/blob/50fff8bde341232c4ac34f8dadc3c3604ce2290d/simple_romp/setup.py#L13
According to:
https://semver.org
It should be:
version='0.3.1',
Because of:
<BREAKING_CHANGES>.<FEATURES>.<FIXES>
How do you think about this?
I would also love to have an version-tag (simple-romp-v0.3.1
?) to be able to create conda
packages easierly:
https://docs.conda.io/projects/conda-build/en/latest/user-guide/tutorials/build-pkgs.html#pypi-source
Of course i would also publish it for you, if it’s okay.
Issue Analytics
- State:
- Created a year ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Semantic Versioning 2.0.0 | Semantic Versioning
In systems with many dependencies, releasing new package versions can quickly become a nightmare. If the dependency specifications are too tight, ...
Read more >Semantic Release - GitHub
Fully automated version management and package publishing ... semantic-release automates the whole package release workflow including: determining the next ...
Read more >Semantic Versioning with CI/CD and semantic-release
Use automated semantic versioning with CI/CD to quickly communicate the compatibility of your released software.
Read more >Automating Versioning and Releases Using Semantic Release
In this post, I would like to discuss our experiences with trying out Semantic Release and how it has helped us better manage...
Read more >How to automate your releases, versioning & release notes ...
In this article we'll explore how to automate releases, changelog, release notes generation and semantic versioning via semantic-release.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks, I see you point.
@vivi90 Thanks a lot, Vivien! I am trying to make the version number right following your guidance.
I just rectify the release version, https://github.com/Arthur151/ROMP/releases
I will make the pip package version consistent with the release version.
But I might take a different way, like regarding this repo as a series works. V0.x CenterHMR -> V1.x ROMP -> V2.x simple_romp (ROMP+BEV) -> … This means the version number is for this repo, instead of the version of ROMP. This is also the reason why the version number of simple_romp pip is independent. But you are right, we should make them consistent. Of course, this won’t stop. I will write the history about this repo in a separate page.
Any comments are welcome~