Short version: Gogogo! Thanks! <div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Slightly longer: Make sure to strictly define the semantics of non-integer parts. It might seem obvious at first - "peru" being "slight fork of micro-version 5". But perhaps sometimes a local branch wants to release a sneak preview, e.g. "almost micro-version 6". Should that then be labeled 23.2.6-peru or (since 5-peru is taken already) 23.2.6.peru2? In Debian we allow both letters and digits in all parts, and use special sign "~" to indicate "almost" and "+" to indicate "just above". And we treat 0 (zero) equal to a missing trailing part. And more nitpicking... I do not, however, recommend you to adopt such complex scheme. I suggest instead (as might actually be what imply by the above summary) that the 3 first parts are strictly digits and intended only for mainline releases, while an optional 4th part is strictly for non-mainline use and allows [a-z0-9] (but nothing else - no dash, underscore, capital or non-ASCII letters, +~ or whatever). Then use simple C locale sort order, and leave it to local branches if they want to use only letters or also leading and/or trailing digits. </blockquote><div>I am planing be more strict: the last part is only [a-zA-Z]* Then the next to 23.2.6-peru will be 23.2.7-peru or 23.2.6.1-peru. The last part does not imply version, only is a helper to the local deployments. Gonzalo </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Enjoy, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: <a href="http://dr.jones.dk/" target="_blank">http://dr.jones.dk/</a> [x] quote me freely [ ] ask before reusing [ ] keep private </blockquote></div>