Nelson Bolyard wrote: > [...] When a new mozilla
>branch is created, it is a simple thing to create a branch of NSS with the same same as the mozilla branch (that is, to make NSS part of that new mozilla branch), and to make the NSS branch occur at the then-current setting of NSS_CLIENT_TAG.
[...] 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. [...]
Jean-Marc Desperrier wrote: >> [...]Or does this mean that the NSS trunk is inside the nightlies for testing purpose, but that there will be a roll-back to the latest stable NSS release, when Mozilla 1.7 is released ?
mozilla nightlies build from a recent snapshot of the NSS trunk. When a moz release is done, NSS typically rolls forward to a new point release, rather than rolling back.
OK. I think I understand now better, but there one point still strange.
Everytime the Mozilla trunk branches, a new NSS branch has is created that reflects the state of NSS_CLIENT_TAG at the time of branching, and the Mozilla branch relies on that branch from then.
From your description, I deduce that this branch is *not* a NSS minor release, but a branch dedicated to Mozilla.
How is it possible to create later a clear reference to what version of NSS that version of Mozilla includes ?
Does this mean you have to create a point release inside that branch, and not from the NSS branch that was created together with the minor release ? That would be really strange.
So the NSS included inside Mozilla does *not* exactly correspond to any normal release of NSS ?
As Mozilla 1.7a was created after the NSS_CLIENT_TAG that includes the bug 53133 fix, it automatically include that fix.
This now appears completely unrelated to the creation of NSS 3.9.1 on the NSS 3.9 branch. Except if NSS 3.9.1 is created instead in the Mozilla 1.7a branch.
This quite contradicts WTC's comment, so I'm not the only one having trouble following all that :-).
Another impact of this :
Asa says that 1.7a is not a branch, just a tag (they don't aim to correct bug specifically for 1.7a, they will branch if there a good reason, but for now try to avoid that) :
http://groups.google.fr/groups?selm=c11gor%245671%40ripley.netscape.com&;
But if that's so, I don't see how they could change the reference out from NSS_CLIENT_TAG to something stable for 1.7a.
_______________________________________________
mozilla-crypto mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-crypto
