nspr_release_procedure.rst (1861B)
1 NSPR release procedure 2 ====================== 3 4 Release checklist 5 ~~~~~~~~~~~~~~~~~ 6 7 #. Change the NSPR version in ``mozilla/nsprpub/pr/include/prinit.h``. 8 #. Change the NSPR version in 9 ``mozilla/nsprpub/{configure.in,configure}``. 10 #. Change the NSPR version in ``mozilla/nsprpub/pr/tests/vercheck.c``. 11 #. Change the NSPR version in ``mozilla/nsprpub/admin/repackage.sh``. 12 13 .. _Source_tarball: 14 15 Source tarball 16 ~~~~~~~~~~~~~~ 17 18 .. _Binary_distributions: 19 20 Binary distributions 21 ~~~~~~~~~~~~~~~~~~~~ 22 23 Right now I use the ``mozilla/nsprpub/admin/repackage.sh`` script to 24 generate the binary distributions published on ftp.mozilla.org. As the 25 name of the shell script implies, ``repackage.sh`` merely repackages 26 binary distributions in a different format. 27 28 Before you run ``repackage.sh``, you need to have built the binary 29 distributions using the "gmake release" makefile target. These binary 30 distributions are jar files, which are really zip files, and they are 31 published in the directory ``/share/builds/components``. This design 32 comes from the Netscape days. 33 34 The ``repackage.sh`` script repackages the jar files into the form most 35 commonly used on that platform. So on Unix it repackages the jar files 36 into gzipped tar files, and on Windows it repackages the jar files into 37 zip files. 38 39 Edit the ``repackage.sh`` script to customize it for your environment. 40 41 After you have run ``repackage.sh``, follow the 42 `instructions <http://www.mozilla.org/build/ftp-stage.html>`__ in to 43 upload the files to ftp.mozilla.org's staging server, so that they 44 eventually show up on ftp.mozilla.org. The host ftp.mozilla.org can be 45 accessed via the ftp, http, and https protocols. We recommend using 46 https://ftp.mozilla.org/. 47 48 **Note:** For NSS, the script equivalent to NSPR's ``repackage.sh`` is 49 ``/u/robobld/bin/sbsinit/nss/push/buildbindist.sh`` in the "SVBuild" 50 source tree.