Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2012.05 released
Date: Wed, 30 May 2012 23:27:29 +0200	[thread overview]
Message-ID: <878vg9xsu6.fsf@macbook.be.48ers.dk> (raw)

Hi,

Buildroot is a simple tool for creating complete Embedded Linux systems
(http://buildroot.net).

Buildroot 2012.05 is released - Go download it at:

http://buildroot.net/downloads/buildroot-2012.05.tar.gz

or

http://buildroot.net/downloads/buildroot-2012.05.tar.bz2

Or get it from Git:

git://git.buildroot.net/buildroot

After 3 months of development a new stable Buildroot release is
out. Significant changes are:

 - Large number of new packages (34): Systemd, polarssl and a number of
   networking packages.

 - GCC 4.7, uClibc 0.9.33.1 and support for Linaro external ARM
   toolchains.

 - Microblaze support (using external toolchain). Xtensa support is
   deprecated.

 - Additional QEMU defconfigs, including Microblaze and e500 PowerPC.
   Defconfigs for Beaglebone, Pandaboard, Freescale mx53qsb.

 - Patch series support in apply-patches.sh

And the usual package version updates and bug fixes. Thanks to the
http://autobuild.buildroot.net autobuilder setup by Thomas Petazzoni we
have been able to fix a lot of different build issues. See the CHANGES
file for details:

http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.05

Many thanks to all the people contributing to this release:

git shortlog -s -n 2012.02..

   171  Gustavo Zacarias
   152  Peter Korsgaard
    77  Thomas Petazzoni
    25  Yegor Yefremov
    12  Maxime Ripard
     9  Arnout Vandecappelle (Essensium/Mind)
     9  Ludovic Desroches
     9  Simon Dawson
     7  Markos Chandras
     7  Sven Neumann
     5  Arnout Vandecappelle
     5  Samuel MARTIN
     4  Alvaro G. M
     4  Luca Ceresoli
     4  Thomas De Schampheleire
     3  Alexandre Belloni
     3  Nicolas Dechesne
     3  Rico Bachmann
     3  Stephan Hoffmann
     3  Yann E. MORIN
     2  Frank Hunleth
     2  Marek Belisko
     2  Maxime Hadjinlian
     2  Qais Yousef
     2  Sagaert Johan
     2  Will Newton
     1  Alexandre Pereira da Silva
     1  Baruch Siach
     1  Dimitry Golubovsky
     1  Fabio Porcedda
     1  Francois Perrad
     1  Ismael Luceno
     1  Jean-Christophe PLAGNIOL-VILLARD
     1  Julian Lunz
     1  Julien Boibessot
     1  Kevin Cernekee
     1  Markus Kaindl
     1  Mathieu Briand
     1  Phil Edworthy
     1  Stephan Thamm
     1  Vanya Sergeev
     1  vsergeev

It has been a quite busy development cycle, with more than 500 commits,
lots of new packages and a number of large scale changes. Part of why we
have been able to handle so many contributions in this cycle is the fact
that we have started to use Patchwork to track patches:

http://patchwork.buildroot.net

Thanks to Jeremy Kerr for his support with this!

Next release will be 2012.08. Expect the first release candidate early
August, and the final release towards the end of the month.

-- 
Bye, Peter Korsgaard

             reply	other threads:[~2012-05-30 21:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 21:27 Peter Korsgaard [this message]
2012-05-31  9:09 ` [Buildroot] Buildroot 2012.05 released Yegor Yefremov
2012-05-31 10:04   ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878vg9xsu6.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox