On Sat, Sep 25, 2010 at 07:08:01AM EDT, Colin Guthrie wrote: > Hi, > > I've had a few people recently ask me about the version of git master. > > As it's based on git tags, I'd like to push a tag to git master called > e.g. "v0.10.0-pre1" or "v0.9.23-pre1" (reserving v0.9.22 for stable-queue) > > This will "fix" the version when building from git master. That said if > we do make a 0.9.22 from stable-queue and then release another from s-q, > before master is truly stabilised, then we would likely want to delete > any tags on master that are confusing or incorrect. > > We can also talk about rebasing and other resolutions here, but if > possible that should be avoided. I would like to revive this if I may. I am about to build git master and put it into a testing repository for Ubuntu, and having a tag that referrs to a version number after 0.9.22 would be very useful, so that users can install the testing package as an upgrade. Sure it would be an upgrade, but the package manager would technically see it as a downgrade, due to the version in git master, 0.9.19. I have pondered tagging in my local copy, so I can build the package, but I'd rather do something that is endorced by upstream, or even better, taken care of by upstream. Luke
