From: Adrian Bunk <bunk@stusta.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH 1/2] nss: Move to meta-oe
Date: Wed, 4 Mar 2020 13:32:17 +0200 [thread overview]
Message-ID: <20200304113217.GB7923@localhost> (raw)
In-Reply-To: <CANNYZj9FbH=Poibo03-7tU=QhJjO5vu3kKHGpCgMCNd9=xVAVQ@mail.gmail.com>
On Wed, Mar 04, 2020 at 10:36:52AM +0100, Alexander Kanavin wrote:
> You are misinterpreting the announcement. The security updates are provided
> by users as patches to the mailing list, maintainers merely collect and
> integrate them. There is no promise from the project to do anything else,
> and LTS doesn’t change that, it only extends the maintainer duty from one
> year to two. Moving a recipe in or out of core does not fundamentally
> change how much attention it gets w.r.t. security fixes.
The part in question does not even talk about LTS, it describes the
status quo for the current stable releases with one year support.
>...
> > <-- snip -->
> >
> > Yocto Project releases are usually maintained for one year.
> > Beyond this period, releases move to community support, which means
> > they only receive occasional patches for critical defects and updates,
> > and no regular defect fixes and security updates.
> >
> > <-- snip -->
>...
This announcement states pretty clearly that security updates are
provided for stable branches, but not for community supported branches.
I am sure there will be an update to the announcement if this doesn't
reflect current reality.
cu
Adrian
next prev parent reply other threads:[~2020-03-04 11:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 19:34 [RFC][PATCH 1/2] nss: Move to meta-oe Adrian Bunk
2020-02-23 19:34 ` [RFC][PATCH 2/2] nspr: " Adrian Bunk
2020-02-24 0:25 ` [RFC][PATCH 1/2] nss: " Khem Raj
2020-02-24 5:17 ` Adrian Bunk
2020-02-24 16:32 ` akuster808
2020-02-27 13:27 ` Adrian Bunk
2020-02-27 14:03 ` Alexander Kanavin
2020-03-04 9:05 ` Adrian Bunk
2020-03-04 9:36 ` Alexander Kanavin
2020-03-04 11:32 ` Adrian Bunk [this message]
2020-03-04 12:13 ` Alexander Kanavin
2020-03-04 14:01 ` Does YP provide security support for stable and LTS branches? Adrian Bunk
2020-03-04 16:00 ` Alexander Kanavin
2020-03-04 17:24 ` Adrian Bunk
2020-03-04 20:26 ` [Openembedded-architecture] " akuster808
2020-03-06 10:04 ` Adrian Bunk
2020-03-06 10:36 ` Richard Purdie
2020-03-08 21:46 ` Adrian Bunk
2020-03-08 22:08 ` Alexander Kanavin
2020-03-09 0:23 ` Adrian Bunk
2020-03-09 7:29 ` Ayoub Zaki
2020-03-09 9:53 ` Alexander Kanavin
2020-03-09 12:45 ` Richard Purdie
2020-03-10 16:11 ` Ross Burton
2020-03-10 19:45 ` Ayoub Zaki
2020-03-11 14:53 ` Ross Burton
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=20200304113217.GB7923@localhost \
--to=bunk@stusta.de \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox