Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[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
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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~