Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] 2017.08-rc1 approaching
Date: Tue, 1 Aug 2017 23:30:55 +0200	[thread overview]
Message-ID: <20170801233055.2488a4fc@windsurf.home> (raw)

Hello,

We're now August 1st, so it's about time to cut 2017.08-rc1.

I've updated the CHANGES file already, and it would be nice if people
could review it, and see if there is any missing information or mistake.

I'm still planning on merging, either today or tomorrow, the skeleton
patch series from Yann, which Arnout is adjusting, as he had made a
number of comments on it. And once this is done, cut -rc1 hopefully
tomorrow evening.

If there is anything that you believe is really important to have in
2017.08 and that is already pending in patchwork, let me know. After
we cut 2017.08-rc1, new features will continue to be merged in the
"next" branch and will be part of the 2017.11 release, and only bug
fixes will be accepted for 2017.08.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

             reply	other threads:[~2017-08-01 21:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 21:30 Thomas Petazzoni [this message]
2017-08-01 22:19 ` [Buildroot] 2017.08-rc1 approaching nimaim at gmail.com
2017-08-01 22:25   ` Thomas Petazzoni
2017-08-01 22:26     ` nimaim
2017-08-02  5:31 ` Bernd Kuhls
2017-08-02 16:35   ` Bernd Kuhls
2017-08-02 20:51     ` Thomas Petazzoni
2017-08-02  6:08 ` daggs
2017-08-02 20:53   ` Thomas Petazzoni
2017-08-02 10:09 ` Marcus Hoffmann
2017-08-02 20:53   ` 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=20170801233055.2488a4fc@windsurf.home \
    --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