argus-2.0 or argus-2.0.0?

[Carter Bullard]

Hey Clauss, et al,
   We did use two strategies in argus-1.x. We used 1.x[a-z]
between 1.5 - 1.7, and then with argus-1.8 we shifted to
argus-1.8.1 for a minor feature addition.  We probably
changed because of trends with other packages rather
than some compelling reason.

   I am going to stick to the strategy that the major
number will only change with changes in the output record
format.  With the TVL structure we have now, we should not
have a major change in a good while.

  Currently, the programs themselves are only sensitive
to an integer major and an integer minor version number,
so they can detect any mods to any data structure
modifications there may be in files or from the server.
The programs will print out just these two numbers with
the -h option, which suggests that 2.0 is the right way
to go.

   I personally like argus-2.0 with interim releases coming
out as 2.0.x, and I don't have any problem with changing
the programs to print out the third number with the -h option,
but keeping only two version numbers for server to client
compatibility.  

Carter

Carter Bullard
QoSient, LLC
300 E. 56th Street, Suite 18K
New York, New York  10022

carter at qosient.com
Phone +1 212 813-9426
Fax   +1 212 813-9426


 


> -----Original Message-----
> From: Clauss Strauch [mailto:Clauss_Strauch at aquila.fac.cs.cmu.edu]
> Sent: Tuesday, February 06, 2001 1:57 PM
> To: Carter Bullard
> Cc: Argus (E-mail)
> Subject: Re: argus-2.0 or argus-2.0.0? 
> 
> 
> 	2.0 sounds good to me, but how do you plan on doing 
> versioning in
> that case? Will the next minor revision be called "2.0a", "2.01", or
> something else?
> 						-- Clauss
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20010206/97a37103/attachment.html>