On Wed, Sep 15, 2010 at 03:18:20PM +0200, Adam Borowski wrote: [...] > I recommend against using dates to mark revisions, since there probably > will be multiple commits in a single day, so there is no way to tell > which exactly version you did package. [...]
On one project where I'm upstream (not packaged for Debian currently), I use seconds since the epoch from the last git commit for a minor versioning component on tarballed development snapshots, which at least reduces this problem down to multiple commits within the same second rather than within the same day. On my project, there's not enough churn to make this a relevant concern for now, I don't care about human readability, and it's only an extra two digits more than you need for an ISO 8601 date. One related concern for some projects, however, is whether releasing from different, out-of-sync VCS branches could make timestamp-only version numbers appear to skip backwards under such a scheme. Making sure your major version numbers are human-assigned is an important component, obviously. ;) -- { IRL(Jeremy_Stanley); PGP(97AE496FC02DEC9FC353B2E748F9961143495829); SMTP(fu...@yuggoth.org); IRC(fu...@irc.yuggoth.org#ccl); ICQ(114362511); AIM(dreadazathoth); YAHOO(crawlingchaoslabs); FINGER(fu...@yuggoth.org); MUD(kin...@katarsis.mudpy.org:6669); WWW(http://fungi.yuggoth.org/); } -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100915165858.ga2...@yuggoth.org