From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 99AB2E00AAA; Wed, 14 Oct 2015 09:27:43 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, * medium trust * [147.11.1.11 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id D1A0FE009B8 for ; Wed, 14 Oct 2015 09:27:41 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.15.2/8.15.1) with ESMTPS id t9EGRZxB020172 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 14 Oct 2015 09:27:35 -0700 (PDT) Received: from Marks-MacBook-Pro.local (172.25.36.227) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.3.248.2; Wed, 14 Oct 2015 09:27:35 -0700 To: , "yocto@yoctoproject.org" References: <561E588D.5060609@2net.co.uk> From: Mark Hatle Organization: Wind River Systems Message-ID: <561E8278.7080702@windriver.com> Date: Wed, 14 Oct 2015 11:27:36 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <561E588D.5060609@2net.co.uk> Subject: Re: RFC: Yocto LTS? X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2015 16:27:43 -0000 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit On 10/14/15 8: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. > > 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? https://wiki.yoctoproject.org/wiki/FAQ#What_is_the_overall_support_plan_for_the_Yocto_Project.3F =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. 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. Effectively this means that support is on the last two releases. Releases are typically released every 6 months. After that point it is usually supported by OSVs, or others that offer commercial services. In the past we have done a few very late security fixes past the 'last two releases' point, however that has been for unique situations. You should consider keeping current with the Yocto Project releases or consider commercial support if you need more then an approx 12 - 18 month support cycle. --Mark > Regards, > Chris Simmonds >