2011/5/31 Michael Hope michael.hope@linaro.org:
On Tue, May 31, 2011 at 1:56 AM, Barry Song 21cnbao@gmail.com wrote:
2011/5/29 Fathi Boudra fathi.boudra@linaro.org:
Hi,
The Linaro Team is pleased to announce the release of Linaro 11.05.
11.05 is the second public release that brings together the huge amount of engineering effort that has occurred within Linaro over the past 6 months.
This is the first release delivering Android, Ubuntu and the Working Group components nicely bundled into one release. We will continue to pick up more Working Group and Landing Team outputs in the upcoming monthly releases.
We encourage everybody to use the 11.05 release. The download links for all images and components are available on our release page:
http://wiki.linaro.org/Cycles/1105/Final
Highlights of this release:
* Linaro GCC 4.5, GCC 4.6 and GDB 7.2 2011.05, recently released components
i have been wondering why always two versions are released at the same time. what kind of users are expected to use 4.5, and what kind of users are expected to use 4.6?
my another question is whether we have a policy to maintain old realease. for example, in case1105 has some bugs, is it possible linato toolchain team fix those bugs in the old version later. many users are using old version with bugs, if they move to new version directly, new feature maybe import new bugs. so people maybe want to use old version with bug fixes, but without new features.
Hi Barry. Have a look at the toolchain flyer: https://wiki.linaro.org/WorkingGroups/ToolChain/Flyer
At any one time we run a development series and a maintenance series. At the moment these are 4.6 and 4.5 based respectively. When the FSF GCC 4.7 comes out, development will stop on 4.5, 4.6 will go into maintenance, and we'll start up a new 4.7 branch.
We currently only fix issues on tip and make them available in the next monthly release. While we don't support older releases or older branches, the branches are never closed or deleted so you are welcome to submit patches or make your own branch and backport changes into that.
that problem is most users have no toolchain team and no enough resources to work on backporting issues. most people just want to use a "stable" toolchain. so hope the consolidation of toolchain validation can help :-)
We are considering a 'stable' branch that is released monthly, maintained for six months, and only has bug fixes but that hasn't been agreed to yet.
Hope that helps,
-- Michael