From: Chris Simmonds <chris@2net.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot LTS?
Date: Fri, 30 Oct 2015 09:22:38 +0000 [thread overview]
Message-ID: <563336DE.4040809@2net.co.uk> (raw)
Hi,
Is there a long term support policy for Buildroot? For example, when the
next significant bug like heartbleed or shellshock comes along, how do I
best incorporate the fix in my Buildroot project?
Looking through the commit history, I gather that Buildroot is a
"rolling release". There are stable releases several times per year, but
there are few updates once it is released. So, the way to get security
fixes would be to update to the latest stable release: is that correct?
The downside is that that will bring in many changes in addition to
fixing security bugs and I may have to go through a new QA cycle.
I would be interested in any comments on the above. What do Buildroot
users do in practice? Does any 3rd party offer LTS support for Buildroot?
Best regards,
Chris Simmonds
next reply other threads:[~2015-10-30 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 9:22 Chris Simmonds [this message]
2015-10-30 13:58 ` [Buildroot] Buildroot LTS? Thomas Petazzoni
2015-10-30 16:14 ` Arnout Vandecappelle
2015-10-31 9:01 ` Peter Korsgaard
2015-11-06 15:35 ` Gustavo Zacarias
2015-11-06 15:50 ` 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=563336DE.4040809@2net.co.uk \
--to=chris@2net.co.uk \
--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