You're not reviewing the full diff of
request 637976
, but the diff to the superseded
request 634329
(Show full diff)
Overview
Loading...
Request History
glaubitz created request
- Update Python Azure SDK to 4.0.0
licensedigger accepted review
ok
staging-bot added as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:44"
staging-bot accepted review
Picked openSUSE:Factory:Staging:adi:44
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto added repo-checker as a reviewer
Please review build success
factory-auto accepted review
Check script succeeded
jengelh accepted review
repo-checker accepted review
cycle and install check passed
dimstar_suse accepted review
ready to accept
dimstar_suse approved review
ready to accept
dimstar_suse accepted request
Accept to openSUSE:Factory
rc versions should use
1.0.0~rc2.That's the versioning scheme that upstream uses:
The point for 1.0.0~rc2 is that in RPM-lingo, this is a lower version than 1.0.0 - whereas 1.0.0rc2 is HIGHER than 1.0.0.
Upstream in all honors - but they never care for such things
Yes, I know how this logic works. DPKG uses the same logic. It hasn't been a problem with the Azure SDK yet, however. And I am not following upstream too closely. The next version will be probably 1.5.0 or so anyway. See, for example, python-azure-mgmt-network which is also in Factory with an "rc2" suffix.
And I'll open a bug report upstream, telling them to keep the RPM and DPKG versioning logic into consideration.