Marshall
Depends on how you look it. I work for a pretty large software company and I know the following holds true for our QA department, at least:
If the Revision is actually a build number [please ignore all my previous posts regarding build numbers because I didn't know what I was talking about then] then it should work as Bobingabout described.
However, if the last part of the version number is actually a forever-increasing build, then there should not be public releases with the same version number. I.E. You can't release X.Y1.B2 if X.Y1.B1 has already been released - you have to release X.Y2.B2.
The way CnCVK is handling this is to have X.Y.Z, with Z just being another branch of the version number.
This is appropriate for the RockPatch. It's nice and easy to understand. (except for the fact that it is currently "RPCE".Z instead of X.Y.Z)
If the Revision is actually a build number [please ignore all my previous posts regarding build numbers because I didn't know what I was talking about then] then it should work as Bobingabout described.
However, if the last part of the version number is actually a forever-increasing build, then there should not be public releases with the same version number. I.E. You can't release X.Y1.B2 if X.Y1.B1 has already been released - you have to release X.Y2.B2.
The way CnCVK is handling this is to have X.Y.Z, with Z just being another branch of the version number.
This is appropriate for the RockPatch. It's nice and easy to understand. (except for the fact that it is currently "RPCE".Z instead of X.Y.Z)
Ever wondered what the hell is going on?
Believe me friend you're not the only one.
--Lysdexia
Check out Launch Base for RA2/YR - http://marshall.strategy-x.com
Also home to the Purple Alert mod, 1.002 UMP, and the YR Playlist Manager.
Believe me friend you're not the only one.
--Lysdexia
Check out Launch Base for RA2/YR - http://marshall.strategy-x.com
Also home to the Purple Alert mod, 1.002 UMP, and the YR Playlist Manager.