All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <yocto@yoctoproject.org>
Subject: Re: How long are stable branches maintained?
Date: Fri, 12 Dec 2014 14:20:53 -0600	[thread overview]
Message-ID: <548B4E25.4060804@windriver.com> (raw)
In-Reply-To: <30C2D590D16A5C46ADFE6521910377984117EA89@AZ-US1EXMB03.global.avaya.com>

On 12/12/14, 7:48 AM, Vuille, Martin (Martin) wrote:
> I have read the information at
> https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance
>
> I would like to know how long stable branches are maintained.
>
> If we are using daisy (1.6), how long can we count on point releases with
>
> security patches before we should plan to upgrade to a newer release?

Rough rule of thumb is the Yocto Project will support two releases at the same 
time, and releases occur roughly every 6 months.  So about 1 year from the time 
of release.  For instance:

Release     - Version - EOL
Fall 2014   - YP 1.7  -
Spring 2014 - YP 1.6  -
Fall 2013   - YP 1.5  - (Fall 2014)
Spring 2013 - YP 1.4  - Spring 2014
Fall 2012   - YP 1.3  - Fall 2013
Spring 2012 - YP 1.2  - Spring 2013
Fall 2011   - YP 1.1  - Fall 2012
Spring 2011 - YP 1.0  - Spring 2012
Fall 2010   - YP 0.9  - Fall 2011

As I said, this is a rule of thumb.  We recently released some updates to 1.5 to 
help close out the work and deal with some security defects.

But I wouldn't expect any further releases.  The maintainer of the branch may 
choose to include fixes submitted by community members, but is not under any 
obligation to.

If you are looking for support longer then the '2 release cycle', I strongly 
suggest that you look at a commercial OSV, or another commercial resource as 
they will be better at helping you with longer term issues.

--Mark

> MV
>
>
>



      parent reply	other threads:[~2014-12-12 20:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 13:48 How long are stable branches maintained? Vuille, Martin (Martin)
2014-12-12 19:41 ` Khem Raj
2014-12-12 20:20 ` Mark Hatle [this message]

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=548B4E25.4060804@windriver.com \
    --to=mark.hatle@windriver.com \
    --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.