From: akuster808 <akuster808@gmail.com>
To: chris@2net.co.uk, "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: RFC: Yocto LTS?
Date: Wed, 14 Oct 2015 06:50:17 -0700 [thread overview]
Message-ID: <561E5D99.6020304@gmail.com> (raw)
In-Reply-To: <561E588D.5060609@2net.co.uk>
Chris,
On 10/14/2015 06: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.
There is a release every 6 months.
https://wiki.yoctoproject.org/wiki/FAQ#What_is_the_release_cycle_of_the_Yocto_Project.3F
>
> 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?
At table of the current supported release can be found at
https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance
- Armin
>
> Regards,
> Chris Simmonds
>
next prev parent reply other threads:[~2015-10-14 13:50 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 [this message]
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
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=561E5D99.6020304@gmail.com \
--to=akuster808@gmail.com \
--cc=chris@2net.co.uk \
--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.