Ensure release RPMs will upgrade alpha or beta installs

[tst-jblair]

Currently release RPMs will not upgrade Alpha or Beta RPMs. The versioning should be upgraded such that a release RPM of the same version should update Alpha and Beta installations.

Two proposals have been made thus far:

• Modify the release number to force it to be later (this makes spotting the "release" a little more difficult in a list of similarly-names RPMs); or
• Have "development" and "release" RPM chains; each system would only install one type, obviating the need to upgrade Alpha/Beta to Release (this makes the whole system more complex, but perhaps simpler in a critical way).

1. Determine if there are other viable options.
2. Select a final design path.
3. Implement it in the RPM build process.

[tst-ccamp]

How about this scheme? If we eliminate the "-#" (that was originally intended to be the package number, but was later just included in the version string instead), and don't drop release, then it should work just fine.

5.2.1.patch#.alpha.date.commit 5.2.1.patch#.beta.#.date.commit 5.2.1.patch#.release

Unfortunately, I think we'll always have to include patch number, otherwise "5.2.1.1.release" wouldn't upgrade "5.2.1.release". That means occasionally we'll have weird looking versions like "5.3.0.0", but I think we can live with that as it won't happen very often. :)

[tst-lsavoie]

@tst-rwildes has this been fixed with the new versioning scheme?