Thank you for information, Robert.
To be honest, I do not care about 3.12 branch, but it looks like patches,
targeting just 3.13, do not get much attention.
For instance, the fix for CMS encoder's DSA, ECDSA signatures [bug 327664]
waits a review since 15 Feb.
I guess, if I would target both branches, the review would proceed quicker. Am
I right ?
By the way, is there an IRC channel or smth. like that, where I can meet NSS
developers ? I have followed #developers @ irc.mozilla.org for some time, but
hasn't met anybody from NSS team.
Best regards,
Konstantin
On 12.04.11 22:36, Robert Relyea wrote:
On 04/12/2011 04:26 AM, Konstantin Andreev wrote:
AFAIK, NSS HEAD is a future 3.13 branch, but most of development is currently
focused on NSS_3_12_BRANCH.
Could anybody advice, how particular issues/bugs of these two branches are
merged ?
They are unlikely to be merged.
NSS 3.12 is what we release current respins and bug fixes.
NSS 3.13 will be some future NSS release in which large new features are added.
That is, - if particular patch occurs in the 3.12, when will it migrate into
3.13 ?
It should already be in 3.13. If you know of any patches in 3.12 that aren't in
3.13, those would be good to identify.
Conversely, may particular 3.13 patch be backported ?
Yes, if it's not large functionality changes. Particularly, large changes to
softoken would not be back ported.
Should off-site developer supply two patches simultaneously to address both
branches ?
If the patch is targeted to 3.12, it should be tested and checked into both
branches.
In general, I usually put things into 3.13 first, then back port them to 3.12.
bob
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto
