Linaro Toolchain Product Release Process Changes (Effective 2015.04)

[Ryan Arnold]

Hello,

In an effort to provide a longer quality control window for quarterly
releases the Linaro Toolchain Working Group will be making some changes to
the release process starting with the forthcoming 2015.04 products.

Little will change for the consumers of TCWG products.

The current monthly source release of the 'stable' Linaro GCC source
archives posted to releases.linaro.org will move to snapshots.linaro.org
and will be designated 'monthly snapshots'.

The exact location will be announced when the 2015.04 Toolchain component
source archive release notes are posted to this mailing list.

These monthly snapshots will continue to have branch merges, performance
fixes, security fixes, and correctness fixes applied on a monthly basis.
They will also continue to have validation across a variety of common ARM
targets performed (per backport) against them.

TCWG will introduce the concept of a 'release candidate source archive' and
'release candidate binary toolchain archive' six weeks before the projected
release date of the Quarterly Binary Toolchain Release. For example, the
2015.05 Quarterly Binary Toolchain and Quarterly Source Archive will be
based upon the 2015.04 source archive snapshot.

Release candidate source and binary archives will be posted to
snapshots.linaro.org.

This release candidate will receive the scrutiny of internal and external
stakeholders for six weeks and give an opportunity to evaluate the
forth-coming Quarterly Binary Toolchain Archive and Source Archive
Release. Problems found with the release candidates will result in the
availability of incremental release candidate archives.

The official quarterly release will be posted to releases.linaro.org.

Please direct any questions or concerns to this mailing list or to me
directly.

[Ramana Radhakrishnan]

Ryan,

Post by Ryan Arnold
Hello,
In an effort to provide a longer quality control window for quarterly
releases the Linaro Toolchain Working Group will be making some changes
to the release process starting with the forthcoming 2015.04 products.
Little will change for the consumers of TCWG products.
The current monthly source release of the 'stable' Linaro GCC source
archives posted to releases.linaro.org <http://releases.linaro.org> will
move to snapshots.linaro.org <http://snapshots.linaro.org> and will be
designated 'monthly snapshots'.

Along with this monthly source snapshot - just to be explicit, will
Linaro also provide binaries produced from the source tarball ?

regards
Ramana

Post by Ryan Arnold
The exact location will be announced when the 2015.04 Toolchain
component source archive release notes are posted to this mailing list.
These monthly snapshots will continue to have branch merges, performance
fixes, security fixes, and correctness fixes applied on a monthly
basis. They will also continue to have validation across a variety of
common ARM targets performed (per backport) against them.
TCWG will introduce the concept of a 'release candidate source archive'
and 'release candidate binary toolchain archive' six weeks before the
projected release date of the Quarterly Binary Toolchain Release. For
example, the 2015.05 Quarterly Binary Toolchain and Quarterly Source
Archive will be based upon the 2015.04 source archive snapshot.
Release candidate source and binary archives will be posted to
snapshots.linaro.org <http://snapshots.linaro.org>.
This release candidate will receive the scrutiny of internal and
external stakeholders for six weeks and give an opportunity to evaluate
the forth-coming Quarterly Binary Toolchain Archive and Source Archive
Release. Problems found with the release candidates will result in the
availability of incremental release candidate archives.
The official quarterly release will be posted to releases.linaro.org
<http://releases.linaro.org>.
Please direct any questions or concerns to this mailing list or to me
directly.
--
Ryan S. Arnold
Linaro Toolchain Working Group - Engineering Manager
www.linaro.org <http://www.linaro.org>

[Ryan Arnold]

On Mon, Apr 20, 2015 at 11:16 AM, Ramana Radhakrishnan <

Post by Ryan Arnold
The current monthly source release of the 'stable' Linaro GCC source

Post by Ryan Arnold
archives posted to releases.linaro.org <http://releases.linaro.org> will
move to snapshots.linaro.org <http://snapshots.linaro.org> and will be
designated 'monthly snapshots'.

Along with this monthly source snapshot - just to be explicit, will Linaro
also provide binaries produced from the source tarball ?

Linaro currently does not provide a monthly binary archive for the monthly
source archive. The binary archives are available on a quarterly cadence
only. We will continue the same policy when the monthly source archives
move to snapshots.linaro.org.

[Bernie Ogden]

Post by Ryan Arnold
TCWG will introduce the concept of a 'release candidate source archive' and
'release candidate binary toolchain archive' six weeks before the projected
release date of the Quarterly Binary Toolchain Release. For example, the
2015.05 Quarterly Binary Toolchain and Quarterly Source Archive will be
based upon the 2015.04 source archive snapshot.
Release candidate source and binary archives will be posted to
snapshots.linaro.org.

So the 'release candidate binary toolchain archive' will be in the
form of source, or of binary tarball? My guess would be that, if
binary toolchain users are going to look at a prerelease at all,
they'll only do so if it's already built for them.

[Ryan Arnold]

Post by Ryan Arnold

Post by Ryan Arnold
TCWG will introduce the concept of a 'release candidate source archive'

and

Post by Ryan Arnold
'release candidate binary toolchain archive' six weeks before the

projected

Post by Ryan Arnold
release date of the Quarterly Binary Toolchain Release. For example, the
2015.05 Quarterly Binary Toolchain and Quarterly Source Archive will be
based upon the 2015.04 source archive snapshot.
Release candidate source and binary archives will be posted to
snapshots.linaro.org.

So the 'release candidate binary toolchain archive' will be in the
form of source, or of binary tarball? My guess would be that, if
binary toolchain users are going to look at a prerelease at all,
they'll only do so if it's already built for them.

Both. There will be a tarball archive for the sources as well as the
binaries.