From: Saul Wold <sgw@linux.intel.com>
To: Joshua Lock <josh@linux.intel.com>
Cc: poky@yoctoproject.org
Subject: Re: Edison Next
Date: Mon, 09 Apr 2012 13:46:49 -0700 [thread overview]
Message-ID: <4F834AB9.8060907@linux.intel.com> (raw)
In-Reply-To: <4F8347A1.3050007@linux.intel.com>
On 04/09/2012 01:33 PM, Joshua Lock wrote:
>
>
> On 09/04/12 13:26, Derek Buitenhuis wrote:
>> On 09/04/2012 3:57 PM, Joshua Lock wrote:
>>> "Q: What is the overall support plan for the Yocto Project?
>>>
>>> A: 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."
>>
>> Random Question:
>>
>> The above FAQ is a tad vague... what if the kernel or toolchain change
>> is a security fix?
>
> That's a reasonable question, but not one I can answer with any
> authority, having not authored the FAQ.
>
> I infer that it means toolchain or kernel *version* changes, as we
> strive to avoid breaking compatibility with any existing layers, etc.
> when providing a stable release update.
>
Joshua is correct, we should update the FAQ to state "Major Version"
changes to toolchain or kernel. If there is a CVE that is addressed by
a patch or maintence update we will ensure those get in.
Sau!
Yocto Project User Space
> Regards,
> Joshua
next prev parent reply other threads:[~2012-04-09 20:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 17:40 Edison Next Joshua Lock
2012-04-06 22:48 ` Matthew McClintock
2012-04-06 22:56 ` Flanagan, Elizabeth
2012-04-07 10:36 ` Holger Hans Peter Freyther
2012-04-07 12:19 ` Wolfgang Denk
2012-04-10 18:08 ` Holger Hans Peter Freyther
2012-04-09 19:57 ` Joshua Lock
2012-04-09 20:26 ` Derek Buitenhuis
2012-04-09 20:33 ` Joshua Lock
2012-04-09 20:46 ` Saul Wold [this message]
2012-04-09 20:48 ` Derek Buitenhuis
2012-04-09 21:53 ` Mark Hatle
2012-05-03 23:12 ` Joshua Lock
2012-05-04 16:11 ` McClintock Matthew-B29882
2012-05-04 23:09 ` Joshua Lock
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=4F834AB9.8060907@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=josh@linux.intel.com \
--cc=poky@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.