David Corcoran wrote:
> ( I really need to seek some help in naming/numbering
> conventions )
Personally I tend to give things release numbers like 1.2.3. The first
number is a major revision, the second is a minor revision and the third
is generated by the source code control system.
The idea is that you change the minor version every time you make a
user-visible change to the system. This means that if you have version
1.2.3 and version 1.2.7 is available, you need not upgrade -- the change
in version numbers just resulted from things being tidied up in the
source control.
The major and minor revision numbers are split to give people an idea of
the size of the change and to stop the numbers becoming annoyingly
large.
Just my pennyworth -- hope it helps.
-----------------------------------------------------------------------
Pete Chown, email [EMAIL PROTECTED], phone +44 (0) 181 680 8393,
fax +44 (0) 181 688 8013, mobile +44 (0) 468 765 645,
post 58 Foss Avenue, Croydon, CR0 4EU, England
***************************************************************
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***************************************************************
