[[!meta title="Release Admin"]] [[!meta author="Tlsa"]] [[!meta date="2010-04-19T18:32:10Z"]] [[!toc]] NetSurf ------- A new NetSurf release is created as follows ### Ready the release branch Readying the release branch depends on the type of release. #### Major releases If it is a major new release with loads of new features, branch from `trunk/netsurf` into `branches/netsurf/[version number]`. Commit the branch. #### Bug fix releases If it is a bug fix release, merge the revisions that are to be included from trunk into an existing release branch. Fix up any failed merges, and remove from Makefile.sources any references to source files that are on trunk and are not in the release branch. Commit the branch. ### Release miscellanea - Prepend this release's changes to ChangeLog - Bump version number in desktop/version.c - Update Docs/BUILDING-\* docs to link to appropriate library tags, rather than trunk versions Commit these changes. ### Create release tag Tag the branch for the appropriate version. ### Autobuilder Update the autobuilder's release tree to the latest autobuilder sources. Run the autobuilder to produce the release archives. (`./autobuild.pl --release=[release version`) This will also: - Upload the source and binary archives to /downloads/releases - Upload new ChangeLog to /downloads/releases/ChangeLog.txt ### Web site Update version numbers all over the site. Update feature list on homepage. Add release to project history on about page. Update download pages to point at new releases. ### Announce release Announce in the appropriate places. Libraries --------- ??