Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=809950 --- Comment #8 from Stanislav Ochotnicky <sochotni@xxxxxxxxxx> 2012-04-23 08:12:52 EDT --- It was not an accident that I put release tag as: 0.1.rc1 Let's keep your release tag and see what happens: You package gradle-1.0-3.rc.1.fc16 Upstream releases final package, you package it and you would have to reset release tag since it's new upstream, so you get: gradle-1.0-1.fc16 $ rpmdev-vercmp gradle-1.0-3.rc.1.fc16 gradle-1.0-1.rc.2.fc16 gradle-1.0-3.rc.1.fc16 > gradle-1.0-1.fc16 So you break upgrade path. Instead you should have: gradle-1.0-0.1.rc1.fc16 Then with new upstream: gradle-1.0-1.fc16 In case there would be rc2: gradle-1.0-0.1.rc2.fc16 so we would have: $ rpmdev-vercmp gradle-1.0-0.1.rc1.fc16 gradle-1.0-0.1.rc2.fc16 gradle-1.0-0.1.rc1.fc16 < gradle-1.0-0.1.rc2.fc16 And everything keeps working. If the upstream would release something that would break upgrade path before releasing final 1.0, you can just raise release from 0.1.X to 0.2.X and continue. Don't forget to check with rpmdev-vercmp in between. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review