On Thu, Oct 7, 2010 at 12:22 PM, Jonas Smedegaard <d...@jones.dk> wrote:
> So the proposed 1.2.3-peru numbering scheme really is a 1.2.3 scheme with > an optional trailing taint hint? > > Yes, the last part is optional. In my first mail I put examples of valid numbers: Valid numbers: 23 23.2 23.2.5 23.2.5-peru 23.2.5-uru Then for the activity developers, probably they will continue with integer numbers, but other players have other possibilities: * OLPC or Dextrose can create version activities where are maintaining old releases: example Browse 108.1 * Daniel Castelo and the people from LATU in Uruguay can create a customization to a activity: example Speak 18.1-uru * People from other deployments can test and use the activity modified in Uruguay. The packagers will need to package only the common activities. The dotted scheme is supported for dpkg, rpm, etc. It probably makes better sense to clearly distinguish those two essentially > separate issues: > > * mainline numbering > + integer > + triple integers > + Debian-style triple string scheme > + other? > * how to officially handle "slight forks" > + extending triple integers with fourth integer/string > + non-version suffix to version > + separate field > + no official support > + other? > > It's clear in the previous examples? > The easiest for Debian would be if you version your code using triple > integers, as that properly supports multiple branches (which you _are_ > doing, whether you admit it or not!). > > debian care not about deployment forks, but I sure recommend that you do > support it properly - which means make room for it in the versioning string > and admit that forks are versioned too - not only a non-versioned flag. > > I don't think we need to support versioning in the forks (uru or peru cases). They can use the first part, adding numbers to manage their versions. Gonzalo > > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iQIcBAEBCgAGBQJMreWmAAoJECx8MUbBoAEhfpIP/2P6RWUKyJF5IMoE0LBMaG29 > 3CX9WkTSp7M3eh6S2zaJYxvU6HgOxDAYqbtYctyRbtIX+z7tFSvS4RIanwGcUYbr > b6xX5l1p2YYpvT3P8JCSNAb90bwdmsOByYvhcDJuvZ1rDJlLl9t/jFn6bnvHaIZi > VrNh3FxNMg1rK1JMBtSTmKLJKRdKszHJQz6eC/0xr6E8kFq4VeuppHkyvSxa8HCq > /oXL1nzylVziPDrdGWqrDfqMr+sQ/hv1O77M9brDYEWZfXfjoJxmKFEDDbbAr18O > rI90kzat19lWvZGnS/PyZxS2SMY9NbK8b4yWC8p+luKx/2gP5dsw6V/JMIX0besB > ju1kEMQFzt/hZSgWhynjqNED1iyr+5IUFLmA9NLzuFhmS0nJ26L4277Q4heEk7/L > 9lR0cnic902RVIY60sr3p9bZklNrVIGIST5RJzuj8n6/CPJfctTL0NBsxzwVS0SB > 7lXhfrDd6JV122fxXeKHI95hFZroHsSby2GoLLIbTmbrV1CjqyvZ4Uz521xSCYjQ > FAIeO9+khwNXLzg99O9lsTfpm8q0yiPLHmq0HeORGFzCwnnhf5E6FRLTrd0JGass > jFqYSz/bsmgEji9YUIHs1gpIFInLU/1oOQgQswVopIKHTxLeYcH3evt6c3fD9QwM > mY8cqELdjJxbTEoHgT54 > =P0DA > -----END PGP SIGNATURE----- > > _______________________________________________ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > >
_______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel