From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Approaching 2012.08-rc1, and beyond
Date: Tue, 31 Jul 2012 23:57:54 +0200 [thread overview]
Message-ID: <20120731235754.56bc0b11@skate> (raw)
Hello,
Within a few minutes, we will be August, 1st. I am therefore planning
on releasing 2012.08-rc1 tomorrow evening in order to comply with our
traditional release schedule.
Even though I have tried to aggressively merge many patches in order to
reduce the backlog, I unfortunately haven't been able to merge as much
things as I wanted. Some packages (like gpsd) have caused various
problems that have consumed quite some time to solve. So things like the
Lua improvements, MIPS architecture support cleanups, gettext
conversion to autotools-package and related cleanups, many new
packages, etc. will have to wait until the next release.
As usual, as soon as 2012.08-rc1 is released, we will have to work in
two directions:
* Continue the work on the 2012.08 release. I mostly will be interested
in build fixes (please help by proposing patches to fix build issues
found through http://autobuild.buildroot.org). I will however also
be accepting documentation improvements and addition of license
metadata to package .mk files since those have no chance of breaking
the build. This direction is obviously the most important one.
* Continue to reduce the backlog by merging new features and major
changes in the 'next' branch, that will lend into the 'master'
branch as soon as 2012.08 is released.
Thanks for the contribution of everyone!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
reply other threads:[~2012-07-31 21:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120731235754.56bc0b11@skate \
--to=thomas.petazzoni@free-electrons.com \
--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