1 In order to perform a release, a few steps have to be taken:
6 [Prepare codebase for release]
7 # [@] Run tests/multitest.php, fix any errors
8 # [@] Run `php release1-update.php $VERSION` (bumps version numbers)
9 # [if necessary] Bump version numbers in TODO
10 # Write new WHATSNEW entry
11 # Commit as "Release x.y.z."
13 [Manage auxiliary branches]
14 if ( need to deprecate old branch ) {
15 # Obsolete old release series
16 - Add OBSOLETE file with text:
17 x.y branch was fully obsoleted by release of x.y.0. It is no longer supported.
18 Bug and security fixes will not be issued regardless of security.
19 ...and then info on backwards incompatible changes.
21 x.y branch was fully obsoleted by release of x.y.0. It is no longer supported.
22 } elseif ( creating a new branch for sub-release ) {
23 # If branch doesn't exist yet, branch from the last tag
24 # Update switch2branch script, replacing version number
25 # Open log for trunk, then switch to branch
26 # Merge changes into branch, commit as "Merged r#s for x.y.z release into branch"
27 - Be sure to remove future items from NEWS
29 # Switch back to trunk using `switch2trunk.bat`
32 # [@] `php release2-tag.php` (tags the releases)
33 # [@] Build the zip and tar.gz files:
34 - Run `./build.sh $VERSION` on the server, download with 'download.bat'
35 - Run build.bat on Windows computer, upload the files
36 # Clear the Serializer cache (flush-definition-cache.bat)
37 # [@] Build the PEAR release using package_pear.bat (package.php and `pear package`)
38 # [@] Run sum-all.bat (generates sha1 checksums)
39 # [@] Run sign-all.bat, enter password when prompted (signs releases)
40 # Update the webpages:
42 . Write a news entry describing the release (see WHATSNEW)
44 . Bump version number and date
45 - Switch the external for live/
51 # Regenerate API documentation (TODO: AUTOMATE)
52 - Run the compile_*.bat scripts (takes a while)
53 - Archive them into tars
55 - Reload documents with ./reload-docs.sh
56 # Smoketest release by downloading packages, verify contents list, sha1 and sig
57 # Upload PEAR release at http://htmlpurifier.org/pear-server.php
58 # Regenerate configuration documentation
59 - Run http://htmlpurifier.org/live/configdoc/generate.php
60 # Update relevant feeder sites/lists
61 - Freshmeat <http://freshmeat.net/add-release/61206/65948/>
62 . Three fields need version number bumps
63 - Announce mailing list <https://panel.dreamhost.com/?tree=mail.list¤t_step=Index&next_step=ShowSend&address=admin&domain=htmlpurifier.org>
64 . Change version number in subject field
65 . Use: news item on webpage (add link to webpage as HTML Purifier),
66 download links (substitute in htmlpurifier.org), sha-1 sums.
67 - Hotscripts listing <http://www.hotscripts.com/account/index.html?section=listings&type=edit&listing_id=65309>
68 . Step 1-3: No changes
69 . Step 4: Bump version number in two fields
70 # Add new version items in NEWS for trunk