[Scons-dev] SCons release version tagging question

2015-06-17 Thread Bill Deegan
Greetings, I'm fixing some logic in SCons's own SConstruct which sets the revision number. Currently is has the revision #, changeset has, branch, and whether it's modified. I also notice that 2.3.4 didn't have this info, so I'm guessing it bootstrap.py was passed the revision id (venv)WilliamsM

Re: [Scons-dev] SCons release version tagging question

2015-06-17 Thread William Blevins
Bill, I would be ok with having the additional information, but I do not think that they provide any additional information with the way branches are created for the releases. It *could* be useful if more than 1 release was made from a release branch. Food for thought. V/R, William On Wed, Jun

Re: [Scons-dev] SCons release version tagging question

2015-06-17 Thread Gary Oberbrunner
IMHO, version number alone is fine. Probably the usual process which has the release on its own branch is why this normally works. But it is time-consuming so if you want to simplify I'm all for it. On Wed, Jun 17, 2015 at 7:40 PM, Bill Deegan wrote: > Greetings, > > I'm fixing some logic in S

Re: [Scons-dev] SCons release version tagging question

2015-06-17 Thread Bill Deegan
Gary, Were you calling bootstrap.py REVISION=2.3.4 then? -Bill On Wed, Jun 17, 2015 at 4:56 PM, Gary Oberbrunner wrote: > IMHO, version number alone is fine. Probably the usual process which has > the release on its own branch is why this normally works. But it is > time-consuming so if you

Re: [Scons-dev] SCons release version tagging question

2015-06-17 Thread Bill Deegan
hg summary (and log) can also pull the tags, so if the only tag on it was say "2.3.5" then it'd be available I need to update the release docs to include the release branching.. -Bill On Wed, Jun 17, 2015 at 4:56 PM, Gary Oberbrunner wrote: > IMHO, version number alone is fine. Probably the u

Re: [Scons-dev] SCons release version tagging question

2015-06-17 Thread Gary Oberbrunner
Pretty sure yes. All that is checked in on each release branch so you can see it. On Wed, Jun 17, 2015 at 8:40 PM, Bill Deegan wrote: > Gary, > > Were you calling bootstrap.py REVISION=2.3.4 then? > > -Bill > > On Wed, Jun 17, 2015 at 4:56 PM, Gary Oberbrunner > wrote: > >> IMHO, version numbe

Re: [Scons-dev] SCons release version tagging question

2015-06-18 Thread Dirk Bächle
Hi guys, On 18.06.2015 01:59, William Blevins wrote: Bill, I would be ok with having the additional information, but I do not think that they provide any additional information with the way branches are created for the releases. +1 from me. ;) It *could* be useful if more than 1 release was