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=569955 Toshio Ernie Kuratomi <a.badger@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a.badger@xxxxxxxxx --- Comment #8 from Toshio Ernie Kuratomi <a.badger@xxxxxxxxx> 2010-03-30 13:50:17 EDT --- Thomas is correct when he says we must follow the Naming Guidelines WRT snapshot packages and the version/release string. The problem is that in the end we don't have any control over upstream so there's several ways that constructing the version numbers in this manner can go wrong: * Upstream changes how it constructs releases. If upstream does something like this we'd be okay: 0.7.917557 => 0.7.917557-1 0.8beta1 => 0.8-0.1.beta1 0.8 => 0.8-1 But what if upstream decides to change their release practices and do something like this this time: 0.7.917557 => 0.7.917557-1 0.7beta1 => 0.7-0.1.beta1 !! Oops, update path broken !! 0.8 => 0.8-1 Or: 0.7.917557 => 0.7.917557-1 0.7beta1 => 0.7-0.1.beta1 !! Update path broken !! 0.7 => 0.7-1 !! Update path even more broken !! * Upstream switches version control systems: 0.7.917557 => 0.7.917557-1 # Upstream switches to git 0.7.87AF2E => 0.7.87AF2E-1 !! Update path broken !! 0.8 => 0.8-1 One note, since these snapshot packages appear to be post-release snapshots rather than pre-release, the versioning should probably be: 0.7-1.917557 If upstream's next stable release is 0.8, this becomes: 0.8-1 If upstream's next stable release were to be 0.7, this becomes: 0.7-2 If upstream switches to git, the order would be preserved by doing this: 0.7-1.917557 0.7-2.87AF2E 0.7-3 (or 0.8-1) The Package Naming Guidelines were written to be robust in cases where upstreams make such changes in their practices. They must be followed here. The other qpidd packages should be changed to conform to the Package Naming Guidelines when their versions can be corrected without breaking the update path. For instance, we might do this:: 0.5.819819-1 # Current 0.5.987654-1 # Still a snapshot with non-conforming version 0.6-1 # versioning corrected since it does not break the update path 0.6-1.998765 # First snapshot with conforming version -- 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