All of lore.kernel.org
 help / color / mirror / Atom feed
From: "akuster@mvista" <akuster@mvista.com>
To: "Stewart, David C" <david.c.stewart@intel.com>,
	 Jeff Osier-Mixon <jefro@jefro.net>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Yocto life cycle statement
Date: Wed, 16 Apr 2014 15:57:28 -0700	[thread overview]
Message-ID: <534F0AD8.9050705@mvista.com> (raw)
In-Reply-To: <CF7433D3.8A888%david.c.stewart@intel.com>

On 4/16/14, 1:21 PM, Stewart, David C wrote:

Thanks Stewart.

That is what I was looking for.

regards,
Armin
> I found the following comments at
> https://wiki.yoctoproject.org/wiki/FAQ#What_is_the_release_cycle_of_the_Yoc
> to_Project.3F
> (It does seem like we have been supplying maintenance releases for two
> releases back, not just one. So maybe this wiki needs to be updated)
>
>
>
> 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
> <https://wiki.yoctoproject.org/wiki/Planning#Yocto>. 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.
>
>
>
> On 4/16/14, 12:43 PM, "Jeff Osier-Mixon" <jefro@jefro.net> wrote:
>
>> Hi Armin - let me do some research on this, just wanted to let you
>> know that I had seen it. I'm not sure we have a formal statement
>> published.
>>
>> On Wed, Apr 16, 2014 at 11:49 AM, akuster@mvista <akuster@mvista.com>
>> wrote:
>>> Hello,
>>>
>>> Can someone point to a 'life cycle statement' for Yocto versions, one
>>> that
>>> discusses limited bug fixing peroid and ultimate EOL of a version. I am
>>> having trouble find it.
>>>
>>> Regards,
>>> Armin
>>> --
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>>
>> --
>> Jeff Osier-Mixon @Intel
>> Yocto Project Community Manager http://yoctoproject.org
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>


      reply	other threads:[~2014-04-16 22:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 18:49 Yocto life cycle statement akuster@mvista
2014-04-16 19:43 ` Jeff Osier-Mixon
2014-04-16 20:21   ` Stewart, David C
2014-04-16 22:57     ` akuster@mvista [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=534F0AD8.9050705@mvista.com \
    --to=akuster@mvista.com \
    --cc=david.c.stewart@intel.com \
    --cc=jefro@jefro.net \
    --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.