[bind10-dev] naming and versioning

[Jeremy C. Reed]

We had discussed a few times about the naming, filenames, and versioning 
of BIND 10. But I don't think we ever had a decision.

The BIND9 way is: name-9.A.B where A is the major feature release and B 
is the minor update release. The alphas are always numbered so starts 
with name-9.A.Ba1. The betas are also numbered so like name-9.A.Bb1. And 
the release candidates are numbered like: name-9.A.Brc1.

I propose that our base name (PACKAGE_NAME) includes a number, so:  
"bind10".  While ISC may not have precendent, it is common for projects 
that have substantial API, configuration, interface changes to include 
the version as part of the base name. (Even though this idea was not 
done for BIND 4 to BIND 8.) Examples include: db4, libxml2, ORBit2, 
imlib2, gphoto2, expat2. ezm3, VFlib2, glade3, xmms2, glob2, mpich2, 
xml2, and many others. Even in some cases, the version number 
(PACKAGE_VERSION) may be a lower number than the version number that is 
part of the base name.

I propose for the version number we start at 1.0, so the very first 
alpha would be: bind10-1.0a1. And the next release phase would be 
bind10-1.0b1 (assuming only one alpha, it would be the first beta).

I am also okay with 0.0 (bind10-0.0a1) or 10.0.0 (bind10-10.0.0a1) but 
that does seem somewhat redundant).

Any comments on this?

If we decided this already please point me to the minutes or email 
archive.

Thanks

  Jeremy C. Reed
  ISC