On Mon, Jun 22, 2009 at 6:44 PM, Mads Kiilerich<[email protected]> wrote: > Steve, > > Do you plan to release rpms as a part of the release process? How will the > procedure be, and how can the rpm build system hook into it and get the > version number?
I will tag 0.8 on July 1. If it takes a day or so to get RPMs built, I'm ok with that. I personally don't have any Fedora machines to build them on (I quit using RedHat/Fedora around 2004). Our releases even on Windows are woefully un-automated at the moment. I'm hoping that gets improved over the course of the week. > Which version number should be used if users build their own rpm from their > local repo? It would be nice if it had some relation to the official release > numbers, and it should be ever-increasing-ish. Should we adopt a > functionality similar to the one used in Mercurial? Mercurial doesn't have a terribly good solution for this that I know of. There is the 'nearest' extension that gives you 'nearest tag'+'longest ancestry to tip', but it's not a core feature. If you don't care too much about 'increasingness', I'm ok with 'nearest tag'+'tip hash' like Mercurial uses for stable builds. It's not obvious how to automate that, though. -- Steve Borho ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
