This page describes what a 'secondary' project is, how it is handled within the Toolchain WG, and what it means to the end user.
Primary projects are ones such as GCC or GDB that that the Toolchain WG does significant work on and offers ongoing support for. These are developed via Launchpad and make use of the issue tracker, release system, source control, and so on. Releases are made monthly.
A secondary project:
- Has been improved for ARM
- Is small, or is unlikely to need improvements in the future
- Has all work done upstream
- Has all issues reported to upstream
- Has no Linaro branding
A secondary project release:
- is done by Linaro
- has upstreams basic approval
- makes these ARM improvements available in a timely manner
- is a snapshot of the development version
- is traceable back to the upstream version
- is of similar quality to the last released version
- is a drop-in replacement for the upstream version
- might be a one-off
- doesn't require us to do further releases in the future
- will be superseded by the next upstream release
Secondary project releases are designed to be easily superseded by version number. A release includes the Toolchain cycle and upstream identifier in the filename, such as valgrind-3.6~linaro-2010.10-0+svn12345 for a Linaro snapshot of the pre-3.6 valgrind at upstream revision 12345. If the work spans months then there a snapshot release will be done at the same time as the primary projects.
Binary versions may be provided to help the testing and consumption of any new work. Bleeding-edge versions are available via the Toolchain PPA. More stable versions may be available via the overlay PPA. Distributions may choose to base off our snapshots instead of taking their own.
Releases will be available through the Linaro Toolchain Misc download page at:
This includes source tarballs, release notes, the change log, and all previous versions.
WorkingGroups/ToolChain/SecondaryProjects (last modified 2010-10-15 12:52:06)