Simon Large wrote:
> -1. I think you need *either* build number *or* minor version
> (and I prefer build number).
>
> Remember that in about 2 years time, maybe less, TSVN's build will gain
> another digit as r9999 rolls over to r10000.
>
> To accommodate both in the scheme above [snipped] you would need:
>
> 1.2.4.5432 --> 1.2.405432
There's no need for the extra zeros. CMIIW, but I think that
concatenating two numbers will always produce a larger number than
when concatenating two numbers that are smaller than (their respective
counterpart in) the larger numbers.
> 1.3.10.7654 --> 1.2.1007654
Likewise, I don't see why you're inserting extra zeros there.
Plus it's weird that 1.3 --> 1.2 ;-)..
Without the zeros:
1.2.4.5432 --> 1.2.45432
1.3.10.7654 --> 1.3.107654
> Do you really want numbers that long?
The above doesn't look too bad.
> We try to correlate with SVN's major and minor release numbers,
> but not with their micro release numbers, so having micro release
> and revision in our own releases is redundant.
Yeah, you're absolutely right, from a technical POV we might as well drop it.
From a "communication POV", Stefan might prefer to be able to tell users:
"please upgrade to the 1.3.4 release"
rather than
"please upgrade to the 1.3.7654 release".
Switching to a technical POV again, we can put any darn version number
we like in the installer, since the only thing it's used for is to
tell MSI whether to upgrade or apply on top of the old installation.
The version number isn't even shown in "Add/Remove Programs" - rather,
there's a string that we have full control over.
If Stefan likes the micro release number we can keep it (?). That
doesn't stop us from killing the bug by removing micro from the
installer and just using major.minor.revision in there.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 19 12:26:57 2005