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.
created by the Toolchain Working Group. * Linaro Kernel 2011.05-2.6.38, the first source tarball release of Linux Linaro done by the Kernel Working Group. * Linaro Evaluation Builds (LEBs) for Android and Ubuntu on PandaBoard with 3D graphics acceleration. * Android cross toolchain based on latest gcc-linaro and gdb-linaro * Host development tools (cross compiler, image builders) readily integrated for the Ubuntu distribution users (Lucid, Maverick and Natty support). * And many more...
Using the Android-based images
The Android-based images come in three parts: system, userdata and boot. These need to be combined to form a complete Android install. For an explanation of how to do this please see:
http://wiki.linaro.org/Platform/Android/ImageInstallation
If you are interested in getting the source and building these images yourself please see the following pages:
http://wiki.linaro.org/Platform/Android/GetSource http://wiki.linaro.org/Platform/Android/BuildSource
Using the Ubuntu-based images
The Ubuntu-based images consist of two parts. The first part is a hardware pack, which can be found under the hwpacks directory and contains hardware specific packages (such as the kernel and bootloader). The second part is the rootfs, which is combined with the hardware pack to create a complete image. For more information on how to create an image please see:
http://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation
Getting involved
More information on Linaro can be found on our websites:
* Homepage: http://www.linaro.org * Wiki: http://wiki.linaro.org
Also subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro developments:
* Announcements: http://lists.linaro.org/mailman/listinfo/linaro-announce * Development: http://lists.linaro.org/mailman/listinfo/linaro-dev * IRC: #linaro on irc.linaro.org or irc.freenode.net #linaro-android irc.linaro.org or irc.freenode.net
Known issues with this release
For any errata issues, please see:
http://wiki.linaro.org/Cycles/1105/Final#Known_Issues
Bug reports for this release should be filed in Launchpad against the individual packages that are affected. If a suitable package cannot be identified, feel free to assign them to:
http://www.launchpad.net/linaro
Cheers,
Fathi Boudra
Linaro Release Manager | Platform Project Manager
linaro-announce mailing list linaro-announce@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-announce
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.
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
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
On Wed, Jun 01, 2011 at 11:18:04AM +0800, Barry Song wrote:
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 :-)
I guess the short answer is that for somebody wanting a stable toolchain, picking a release from the 4.5 series is the safer bet, and if you do find bugs, well, report them to launchpad.net/gcc-linaro or to this mailing list.
PS: Michael, can you update the flyer to include the links I suggested we add to the release announcement?
On Wed, Jun 1, 2011 at 11:25 PM, Christian Robottom Reis kiko@linaro.org wrote:
PS: Michael, can you update the flyer to include the links I suggested we add to the release announcement?
I've added the links to the Communication section of the flyer at: https://wiki.linaro.org/WorkingGroups/ToolChain/Flyer#Communication
-- Michael
2011/6/1 Christian Robottom Reis kiko@linaro.org:
On Wed, Jun 01, 2011 at 11:18:04AM +0800, Barry Song wrote:
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 :-)
I guess the short answer is that for somebody wanting a stable toolchain, picking a release from the 4.5 series is the safer bet, and if you do find bugs, well, report them to launchpad.net/gcc-linaro or to this mailing list.
sure:-) as linaro toolchain really shows strong performance, we did have used it for several monthes, reported bugs and discussed with linaro toolchain team. really thank the team very much for the help! i asked this just because we really want to use it as a long term plan in our all productions using linux. so the stability is what we really care about. to users like us, if old release can get maintained, we can pull the bug fixes from linaro and don't need to upgrade to new frequently and monthly. thanks very much for the great contribution of linaro toolchain team.
PS: Michael, can you update the flyer to include the links I suggested we add to the release announcement? -- Christian Robottom Reis | [+55] 16 9112 6430 | http://launchpad.net/~kiko Linaro Engineering VP | [ +1] 612 216 4935 | http://async.com.br/~kiko
linaro-toolchain@lists.linaro.org
-
Barry Song -
Christian Robottom Reis -
Michael Hope