NSS_CLIENT_TAG is pointing at NSS_3_10_BETA2 right now. We would like to upgrade it to NSS_3_10_BETA3. We want to release NSS 3.10 at the same time Gecko1.8/Aviary1.1 is released.
Created attachment 180415 [details] [diff] [review] Upgrade from NSS_3_10_BETA2 to NSS_3_10_BETA3 This patch is the diffs between NSS_3_10_BETA2 and NSS_3_10_BETA3. All the changes have been reviewed by NSS developers. NSS_3_10_BETA3 passed NSS QA certification. I'm requesting drivers approval for Aviary 1.1a and Mozilla 1.8b2. This patch is artificially large because we renamed all the internal functions and data types in the mozilla/security/nss/lib/softoken directory. So in this case the risk of the patch is much smaller than the size of the patch. Since we are very close to releasing NSS 3.10 final, we have strict checkin control, so the risk of this patch is very low.
I set the blocking-aviary1.1? flag because Aviary 1.1 final should not use an NSS beta release, and NSS_3_10_BETA3 is an important milestone to NSS_3_10_RTM.
Comment on attachment 180415 [details] [diff] [review] Upgrade from NSS_3_10_BETA2 to NSS_3_10_BETA3 a=asa for checkin to the Mozilla trunk.
I moved NSS_CLIENT_TAG to coincide with NSS_3_10_BETA3 at 14:32 -0700 (US Pacific Daylight Time).
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.8beta2
You need to log in before you can comment on or make changes to this bug.