Releases
-
- What’s our release lifecycle, how head and branches are organized, RCs building
You can download release candidate builds here. On this pages you can find static version of our build system displaying Nightly builds and Release candidates.
Release candidates are built for the purposes of going through QA procedures before making a release. They are built in a differnt way than nightly builds. First, nightly builds are built for each platform separately in any time. Release candidates are built for all platforms together from one source. Process of release candidate build consists of checking out CVS from actual branch, making tag in CVS for a given release candidate, packing all sources into one tarball. Then compilation is invoked on all platforms, which uses this common source tarball. Also no patching is used for release candidates builds, they must be all from CVS.
NOTE: Source for public download are available from version 0.56.
When you load actual AllPeers Build System page, you can see there a table with all release candidates for last version, included all bugfix versions (it is the optional third version number - i.e. 0.53.2 means second bugfix version).
We have 2 common columns and then 3 sections - for each platform, we make a build.
- Version - the version (also written in XPI) of release candidate build - i.e. 0.53rc2 (first release), 0.54.1rc5 (bugfix release).
- Source - link, where you can download the source tarball, which was used, when the build was made.
- Comment - custom comment for a given RC
Platforms (Windows, Mac, Linux)
- Status - the result of build on a given platform, can be OK, Failed (no additional patches for RCs)
- XPI - contains link to download given RC XPI for install in case the build was successful
- Build Logs - the output of the compiler. Useful in checking the reason of build failure, or for examination of warnings.
- Warn# - displays the count of warnings in build (not counting 3rd party libraries)
NOTE: for MAC, we’re building universal binary - build is running on two computers, then glueing the result together (same for nightly builds). Build Logs and Warn# contains two lines - first for PowerPC build and second for Intel build.
