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

[Nathanael Hoyle]

On Wed, 2010-03-17 at 13:34, Shane Kerr wrote:
> Nathanael,
> 
> On Wed, 2010-03-17 at 12:51 -0400, Nathanael Hoyle wrote:
> > 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. 
> 
> It's okay - actually encouraged!
>  
> > 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.
> 
> I think this makes sense, so you'd get something like this:
> 
>         $ b10-auth --version
>         b10-auth version 1.0.3
>         BIND 10 version 10.0.0
>         
> Right?
> 
> --
> Shane
> 

Sorry for delay in response. This (output given) is one possible
implementation that would align with what I was suggesting. The key
point is that if any of the individual components gets revised, the meta
level also needs to increase.

That means that if the version for bind 10 auth is 1.0.3 and there is a
fix released that bumps it to 10.0.4 or 10.0.3.1 or 10.0.3p1 or
something, the overall Bind 10 version also needs to increase in some
fashion. This means that at any time, a single version number can be
shared to summarize the set of package sub-versions.

Alternately, a command like 'bind10-version' which gives the meta
version and then interrogates each of the components to provide its
version, would allow a user to quickly obtain and provide all version
info.

-Nathanael