On Sun, Mar 04, 2007 at 02:34:21PM -0600, Kevin P. Fleming wrote: > Brad Templeton wrote: > > In many packages there is some file (usually the change log) which always > > tells you what version of the program you have in your hands, in terms > > of the program's current version number -- of course you can see the > > svn revision numbers and dates but they don't trivially translate. > > I would be surprised to see such a file in a direct checkout from the > project's SCM system. Even if that file existed, it would exist for a > very short time as the moment a new commit occurred that branch would no > longer 'be' 1.4.1, for example.
Yup, typically it's a changelog and significant changes are noted along with version number bumps. I'm presuming the /branch/1.4 is "the latest stable version of 1.4 with the latest patches." Since there is a 1.4.1 it means it is also 1.4.1 with the latest patches -- or so I presume. Having a file means people can look at see what they have, without having to ask here :-) Now that I know I can interpret what it means. I'm assuming that the latest /branch/1.4 is "the one to run" if you want a stable system with all known and tested patches and fixes but only modest new functionality -- or should one really be running /tags/1.4.1 and regularly updating your tag in order to get that? _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users