From: Chris Simmonds <chris@2net.co.uk>
To: Philip Balister <philip@balister.org>,
Mark Hatle <mark.hatle@windriver.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: RFC: Yocto LTS?
Date: Thu, 15 Oct 2015 20:06:24 +0100 [thread overview]
Message-ID: <561FF930.7090902@2net.co.uk> (raw)
In-Reply-To: <561FCAFC.5060209@balister.org>
On 15/10/15 16:49, Philip Balister wrote:
> On 10/14/2015 12:26 PM, Chris Simmonds wrote:
>>
>> On 14/10/15 17:27, Mark Hatle wrote:
>>> On 10/14/15 8:28 AM, Chris Simmonds wrote:
>>>> Hi,
>>>>
>>>> Is there a statement about the period of support for a Yocto release?
>>>> Looking through the updates, it seems that 12 months is typical, a was
>>>> the case for 1.4, 1.5 and 1.6 for example, but I cannot see a
>>>> declaration anywhere that this is the expected norm.
>>>>
>>>> Leading on from that, is 12 months enough? Most projects have a
>>>> lifecycle that is much longer. Is there an argument for an LTS Yocto
>>>> release, maybe once a year? If not, what is the recommended way for a
>>>> project developer to keep a distribution up to date in the light of the
>>>> several well-publicised security flaws that have been discovered over
>>>> the last year or so and the new ones that will no doubt be discovered in
>>>> the future?
>>>
>>> https://wiki.yoctoproject.org/wiki/FAQ#What_is_the_overall_support_plan_for_the_Yocto_Project.3F
>>>
>>> =What is the release cycle of the Yocto Project?=
>>> Each release of the Yocto Project is subject to its own release schedule
>>> according to the community-maintained Project Planning Guide. It is generally
>>> expected that a new version of the Yocto Project will be released every six months.
>>>
>>> =What is the overall support plan for the Yocto Project?=
>>> Security patches and critical bug fixes are supplied one release back. No
>>> toolchain or kernel changes are allowed for these updates. Support for longer
>>> periods of time can be supplied by commercial OSVs.
>>>
>>>
>>>
>>> Effectively this means that support is on the last two releases. Releases are
>>> typically released every 6 months. After that point it is usually supported by
>>> OSVs, or others that offer commercial services. In the past we have done a few
>>> very late security fixes past the 'last two releases' point, however that has
>>> been for unique situations.
>>>
>>> You should consider keeping current with the Yocto Project releases or consider
>>> commercial support if you need more then an approx 12 - 18 month support cycle.
>>>
>>> --Mark
>>>
>>
>> Thanks, that is all clear now.
>
> We wouldn't be opposed to a group of people supporting a release for
> longer. But they would need to provide the people to do the work. LTS
> work is hard.
>
> Philip
>
>>
>> Chris
>>
>
Indeed, it is hard work. But there is a community out there with the
expertise and many very profitable corporations that depend on Yocto
Project (in addition to Intel, I mean, since they put a lot of resource
in already). It would be really nice if someone neutral - Linux
Foundation for example - could bring them together to make LTS work for
everybody.
Chris.
next prev parent reply other threads:[~2015-10-15 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 13:28 RFC: Yocto LTS? Chris Simmonds
2015-10-14 13:50 ` akuster808
2015-10-14 15:12 ` Chris Simmonds
2015-10-14 16:23 ` Bruce Ashfield
2015-10-14 16:27 ` Mark Hatle
2015-10-14 18:26 ` Chris Simmonds
2015-10-15 15:49 ` Philip Balister
2015-10-15 19:06 ` Chris Simmonds [this message]
2015-10-16 22:23 ` akuster
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=561FF930.7090902@2net.co.uk \
--to=chris@2net.co.uk \
--cc=mark.hatle@windriver.com \
--cc=philip@balister.org \
--cc=yocto@yoctoproject.org \
/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.