From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] 2016.05-rc1 approaching: what to merge?
Date: Thu, 28 Apr 2016 16:00:00 +0200 [thread overview]
Message-ID: <20160428160000.5db9d1cb@free-electrons.com> (raw)
Hello,
We're approaching the end of April, and therefore the beginning of May,
which means that 2016.05-rc1 will be released soon, most likely in
about a week.
As a reminder, once -rc1 is released, we don't merge new packages or
version bumps, but only build fixes, security fixes, documentation
updates, etc. Of course, anything that doesn't get merged before -rc1
can be merged for the next release, 2016.08.
So the question is: we have ~230 patches pending patchwork. Do you see
anything that we should really merge before 2016.05-rc1 is released?
Thanks for your feedback,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2016-04-28 14:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 14:00 Thomas Petazzoni [this message]
2016-04-28 14:06 ` [Buildroot] 2016.05-rc1 approaching: what to merge? Yegor Yefremov
2016-04-28 14:20 ` Thomas Petazzoni
2016-04-28 14:25 ` Yegor Yefremov
2016-04-30 12:53 ` Thomas Petazzoni
2016-05-01 12:35 ` Thomas Petazzoni
2016-05-01 14:17 ` Yegor Yefremov
2016-05-01 17:10 ` Thomas Petazzoni
2016-04-28 14:15 ` Julien CORJON
2016-04-30 17:05 ` Thomas Petazzoni
2016-04-28 14:40 ` Gustavo Zacarias
2016-04-30 19:08 ` Thomas Petazzoni
2016-04-28 15:00 ` Bernd Kuhls
2016-04-29 18:12 ` Thomas De Schampheleire
2016-04-29 18:24 ` Carlos Santos
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=20160428160000.5db9d1cb@free-electrons.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.