Right. If the moz browser folks are doing things right, they will ensure that 1.7b is built from an NSS tag other than NSS_CLIENT_TAG. To put it another way, if a mozilla release ever shipped with NSS built from the NSS_CLIENT_TAG, that would (IMO) be an error of the mozilla builders, and not of anyone in NSS.
It seems strange to have a process which says:
"If you just pull the tree and release, you are doing something wrong. You need to pull the tree, modify it in these X ways (even if X is 1), do further testing to make sure you haven't broken anything, and only then release."
If the trunk doesn't use the version of NSS to be used in the next release of Mozilla, that means (I would think) that the released version of NSS (and therefore of Mozilla) gets less testing than it should.
Gerv _______________________________________________ mozilla-crypto mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-crypto
