Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot LTS?
Date: Sat, 31 Oct 2015 10:01:29 +0100	[thread overview]
Message-ID: <87eggb1keu.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20151030145803.6aeb3c2d@free-electrons.com> (Thomas Petazzoni's message of "Fri, 30 Oct 2015 14:58:03 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

Hi,

 >> 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?

 > There is currently no long term support policy for the community
 > maintained Buildroot. We have discussed this topic a few times during
 > our meetings, as I remember raising the question of whether we should
 > maintain for a longer period certain specific releases of Buildroot, at
 > least to take care of the security problems.

 > So far, our common reaction was that it is rather time-consuming to do
 > and also not very exciting for volunteers to do. It is the type of
 > topic that would really be helped if there was some funding from
 > companies.

Indeed, so far nobody has volunteered to do such work.

 > That being said, if there is sufficient interest for this, and
 > developers willing to look at the security issues and submit the
 > corresponding patches, I'm sure we'd be happy to create such LTS
 > releases from time to time.

Certainly. We already do bugfix releases (like 2015.08.1) for important
issues discovered after release. I have no problems doing more of those,
but people have to submit patches and/or point out what patches on
master also applies to the bugfix release.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2015-10-31  9:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30  9:22 [Buildroot] Buildroot LTS? Chris Simmonds
2015-10-30 13:58 ` Thomas Petazzoni
2015-10-30 16:14   ` Arnout Vandecappelle
2015-10-31  9:01   ` Peter Korsgaard [this message]
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=87eggb1keu.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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