[bind10-dev] BIND bindctl review && bindctl certificate

[Nathanael Hoyle]

On 3/17/2010 12:23 PM, Jeremy C. Reed wrote:
> On Wed, 17 Mar 2010, zhanglikun wrote:
>
>    
>>>   help also shows a version hardcoded in the string that should come from
>>>   configure
>>>        
>> Yes, it should get the version number from configure file. (Add to
>> TODO list) BTW, if the version number of all modules of bind10 should
>> be same?
>>      
> I think all components should have their own version numbers. That way
> if we later release a bug fix for an individual software it easy to
> recognize. So not use the BIND 10 version number from configure.
>
> Do we want to reset configure.ac for every individual component version
> change?
>    

First posting to this list... I've been lurking for a couple of days 
now, hope it's ok to chip in. I would strongly advocate an approach that 
at least offers a single command that emits all relevant version 
information.  Having individual component revisions can be fine, but in 
general having a single meta-version that refers to the combined set of 
those packages is extremely useful.  One of the types of servers that I 
support on a regular basis is comprised of over 80 individual software 
packages. Each package has its own version number. Every conversation 
with the vendor begins with a complicated process to try to determine 
what version one is running. Being able to have a single, concise 
version string for use in vendor support or posts to forums and 
discussion lists can be extremely valuable.

Generally speaking, my preference would be to track individual versions 
of software packages, and have them available, but to have an 
overarching version number associated with a "bind release" that is 
bumped whenever any of the component versions has a new version released.

My $0.02.

-Nathanael