mozilla
Your Search Results

    NSPR release process

    1. Set the NSPR version number. Five files need to be updated: configure.in, configure, repackage.sh, prinit.h, and vercheck.c. Look at their CVS histories for examples.
    2. Make a dummy change (add or remove a blank line) to mozilla/nsprpub/config/prdepend.h.
    3. Make sure the NSS tinderboxes (which also build and test NSPR) are all green. The build+test cycles of the NSS tinderboxes are very long, so you usually need to wait half a day for them to cycle through.
    4. Create a BETA CVS tag. The naming convention is NSPR_x_y_z_BETAn for NSPR x.y.z Beta n.
    5. Push the BETA tag to mozilla-central for testing in Firefox trunk builds. Ideally you should test it for a week.
    6. Remove "Beta" from the NSPR version number for the final release.  Usually you just need to update prinit.h.
    7. Make a dummy change (add or remove a blank line) to mozilla/nsprpub/config/prdepend.h.
    8. Create a RTM CVS tag. The naming convention is NSPR_x_y_z_RTM for NSPR x.y.z.
    9. Upload a source tar file to https://ftp.mozilla.org/pub/mozilla....nspr/releases/
    10. Write the release notes.
    11. Announce the release in the Mozilla NSPR newsgroup.

    Document Tags and Contributors

    Contributors to this page: Sheppy, fscholz, Wtchang, DerekSpeltDifferently
    Last updated by: fscholz,