Added a comment explaining how NSS_BUILTINS_LIBRARY_VERSION_MINOR should be

incremented.
This commit is contained in:
wchang0222%aol.com 2004-08-31 17:39:15 +00:00
Родитель 9bb982aa69
Коммит bad8733fd8
1 изменённых файлов: 22 добавлений и 1 удалений

Просмотреть файл

@ -51,7 +51,28 @@
#define NSS_BUILTINS_CRYPTOKI_VERSION_MINOR 1
/* These are the correct verion numbers that details the changes
* to the list of trusted certificates. */
* to the list of trusted certificates.
*
* The NSS_BUILTINS_LIBRARY_VERSION_MINOR macro needs to be bumped
* for each NSS minor release AND whenever we change the list of
* trusted certificates. 10 minor versions are allocated for each
* NSS 3.x branch as follows, allowing us to change the list of
* trusted certificates up to 9 times on each branch.
* - NSS 3.5 branch: 3-9
* - NSS 3.6 branch: 10-19
* - NSS 3.7 branch: 20-29
* - NSS 3.8 branch: 30-39
* - NSS 3.9 branch: 40-49
* - NSS 3.10 branch: 50-59
* ...
* - NSS 3.14 branch: 90-99
* ...
* - NSS 3.30 branch: 250-255
*
* NSS_BUILTINS_LIBRARY_VERSION_MINOR is a CK_BYTE. It's not clear
* whether we may use its full range (0-255) or only 0-99 because
* of the comment in the CK_VERSION type definition.
*/
#define NSS_BUILTINS_LIBRARY_VERSION "1.50"
#define NSS_BUILTINS_LIBRARY_VERSION_MAJOR 1
#define NSS_BUILTINS_LIBRARY_VERSION_MINOR 50