If I understand correctly, you're saying "version" numbers are totally made
up by the developer(s) according to their own rules (or feelings :) ) and
have nothing to do with svn, except for the build number.
"Peter McNab" <firstname.lastname@example.org> wrote in
> Toeneeo wrote:
>> Where does one set what version numbers will look like i.e. how many
>> subcatagories / how many numbes per category e.g.:
>> 1.2 (only 2 levels)
>> 1.2.34 (3 levels)
>> 1.2.34 build 5000.
>> And where can one see this info per file/folder.
>> If I look at "properties" of a file it just says e.g. revision 3.
> Hi Toeneeno
> I don't know if you would find this in the FAQ, because many new users
> probably read the Subversion documentation before running TortoiseSVN.
> Anyway section 2.3.2 of TortoiseSVN's own help file discusses the version
> numbering scheme which basically starts at 0 and grows ..n. incrementing
> exactly 1 for every commit made to the repository. Revision numbers are
> all integers, there are no decimal places.
> When it comes to releasing *versions*, as distinct from individual revs
> which tick over on every commit. its a different matter.
> In general communities agree on a Versioning scheme something along the
> following lines.
> SVN 1.3.4 (optionally rev nnnn), Version 1.3.5 etc are human contrivances
> where the most significant digit (1 in this example) represents something
> very significant to the community.
> The intermediate figure (3 in this example) represents a milestone version
> containing significant feature changes, without breaking previous
> usability but probably adding a significant feature.
> The last digit (e.g. figs shown as 4 & 5) are applied to smaller changes
> involving bug fixes or proper completion of new features. There are rules
> about breaking/changing APIs which control when these numbers tick over as
> The rev number shown as nnnn above is the Subversion revision from which
> the release is compiled and distributed.
> As stated, the developer communities usually have guidelines published in
> files like haxx to much better describe my simplified description.
> Hoping that answers your query.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Aug 6 05:25:52 2006