Short version: Gogogo! Thanks!
> 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. > > 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 > Enjoy, > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private >
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel