<HTML>
<HEAD>
<TITLE>question about version numbers</TITLE>
</HEAD>
<BODY>
<FONT FACE="Verdana, Helvetica, Arial"><SPAN DEFANGED_STYLE='font-size:12.0px'>To all,<BR>
<BR>
I am about to upload an updated tcltkgrass for 5.7 to the CVS. Glynn Clements helped revamp gui.tcl after I cleaned out about 2/3 of the code because it is unused now. menu.tcl also has some updates to go along with this clean up. Both deserve a change in version numbers. Internally (i.e., in the header to the program), menu.tcl is going from 4.0 to 4.1.<BR>
<BR>
So here is my question. The CVS was started considerably after the GRASS project and so it’s version numbers are quite different from the internal version numbers, at least for the modules that I’ve been dealing with. I was wondering:<BR>
<BR>
1. Would it be a good idea to change the CVS version numbers to match the internal version numbers with the idea that they stay in sync thereafter and can help others see where the module revisions are at? Or is this a bad idea for some reason?<BR>
<BR>
2. Would it be a good idea to give all modules of tcltkgrass the same version number, updating it across all modules as needed? Currently, menu.tcl is at 4.0 and gui.tcl is at 1.1. Or is it better if each module of this package gets version numbers as the individual module is changed?<BR>
<BR>
Michael<BR>
<BR>
______________________________<BR>
Michael Barton, Professor & Curator<BR>
School of Human Origins, Cultures, & Societies<BR>
Arizona State University<BR>
Tempe, AZ 85287-2402<BR>
USA<BR>
<BR>
voice: 480-965-6262; fax: 480-965-7671<BR>
www: <a href="http://www.public.asu.edu/~cmbarton">http://www.public.asu.edu/~cmbarton</a><BR>
</SPAN></FONT>
</BODY>
</HTML>