Tom Schraitle

@tlaferriere Thanks for the detailed description. :+1: From what I've seen, it does make sense. Unless I've overlooked something important. :wink:

Thank you @vincent-herlemont, much appreciated. Sorry for the late response. I suppose, this should be fixed. This behaviour is the same for the method `.bump_build()`. So both need to be...

@vincent-herlemont One question. What would you expect if you have already a prerelease and pass an empty string? Like this: ``` >>> ver = semver.VersionInfo.parse('1.0.0-rc.1') >>> ver.bump_prerelease('') # ??? ```...

@scls19fr, @ppkt, @gsakkis what's your opinion on this?

@Askaholic Sorry for the long time, but thanks for your ideas. I think, it depends on the use case. If you start with two version strings, then sure, the first...

@tlaferriere would love to hear your opinion on this topic. Should we allow `semver.compare` and remove the deprecation status? Any arguments for or against it?

@tlaferriere Thank you very much for your wonderful and logical analysis. :+1: Actually, I had something similar in my mind, but I didn't think that through how you did. It...

Thank you very much for your detailed answer @tlaferriere! :+1: > Sorry to play the devil's advocate here, but I think it is a good way to really make sure...

Ok, thanks for the hints, @tlaferriere! :+1: As we usually create a `VersionInfo` object by passing either a string or integers, I would end up with this snippet: ```python from...

@durera sorry for the delay. Yes, it looks a bit verbose. Some time ago, I've added in #303 an idea which is related to this issue: * rename `VersionInfo` to...