Re: Mozilla trunk and NSS trunk

[John Gardiner Myers]

The procedure Mozilla uses to pull NSS is seriously broken.

Some unknown person has apparently moved NSS_CLIENT_TAG to point to some 
unreleased snapshot of NSS.  That's two things wrong:

1) Any build/release procedure which consists of moving tags is insane.  
CVS does not version or log tag movements.  One cannot query CVS to find 
out when this change happened or who did it.  If one branches Mozilla, 
the branch will, without extra work on the part of the brancher, 
continue to track future movements of the tag.

From a comment on bug 197009 I recently learn that there is an obscure 
web page that keeps a partial log of  NSS_CLIENT_TAG movements.  The web 
page does not mention who moved the tag, or why.  The change is not 
visible on either Tinderbox or Bonsai.  By looking at the CVS log 
corresponding to the web page, I find that Wan-Teh was the one to change 
the log, so is probably the one who changed the tag.

A proper build/release procedure would never move or delete a tag that 
has been used.  NSS changes would be incorporated into Mozilla by 
checking in a change to the NSS_CO_TAG macro in mozilla/client.mk.  The 
NSS_CO_TAG would be set to one of the NSS release tags, be it an 
"official" NSS release or a Mozilla-only NSS release.

2) Any set of NSS changes that are important enough to pull into a 
release of Mozilla are important enough to release under a proper, 
unambiguous name.  If the NSS team intends to create a release called 
"3.9.1 Beta", they should tag it with  NSS_3_9_1_BETA.  Immediately 
following the release, they should change the verison string used by the 
NSS trunk.
_______________________________________________
mozilla-crypto mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-crypto