Hi Allan, m. allan noah writes:
> this sounds like a reasonable plan to me, though I wonder what effect > it will have on the currently installed git-based packages. They are > already 1.0.26+gitxxxx, and they will remain so after this release > (though the xxxx part will be of a different format). Most of the cases I've seen use a date for the xxx part. If so, there'd be no problem as the git snapshots after the 1.0.26 release will have a later date. Distributions can also work around with an "epoch", so you get something like "1:1.0.26+gitxxxx", but that's a bit ugly. But we could also just admit that we've more or less goofed up on the versioning for our master branch, skip 1.0.26 and release as 1.0.27. Doing so will bypass any of the scenarios you worry about. I'd go with 1.0.27 but am fine with 1.0.26 for the release and add a +git on master (for now while we investigate using `git describe`). Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
