From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 4C2F1E00B5A; Wed, 14 Oct 2015 08:12:16 -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=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [212.227.17.10 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 791E5E00B5A for ; Wed, 14 Oct 2015 08:12:12 -0700 (PDT) Received: from [192.168.159.8] ([80.43.50.149]) by mrelayeu.kundenserver.de (mreue102) with ESMTPSA (Nemesis) id 0Mbyj8-1a2GgH3UG6-00JJkr; Wed, 14 Oct 2015 17:12:11 +0200 References: <561E588D.5060609@2net.co.uk> <561E5D99.6020304@gmail.com> To: akuster808 , "yocto@yoctoproject.org" From: Chris Simmonds Organization: 2net Message-ID: <561E70CB.6040509@2net.co.uk> Date: Wed, 14 Oct 2015 16:12:11 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <561E5D99.6020304@gmail.com> X-Provags-ID: V03:K0:ZX+xox9UcEy0hK3duCFCFlaN8nnR+ppWmCw7fLjFvT3PWyedCOK 1XUUKfIwrkGSsk3ovOD1rHPFjfpj5HI6VVA0Q39xsCtUHDKQAbQr0sMB/0Igi9CBlrTQFTs dqWJxcDX9/3j26r/Ao+S6BitTcFszGOBF7uUvHYW1FAwuUBfbqh+rc9wj+4eP+3nDr3S/+K WsD46VDAOhB5yayvg6LJA== X-UI-Out-Filterresults: notjunk:1;V01:K0:4i1o5q+pwhE=:D0A6porDTGA5NkrE8jrslQ gIzYB8RVCRAw0uYB8VZ8okocqQK94smkPzId9zWWmDAhXCGBDD6YsavGNnzHGAC54NrI5Tz1J gppGhtu1kxGYAwEWG96uXoKT/EgUbOQMhqrDZcjFdUFbVhA6Y+uFQKbEOBczVx4w2XddzXNYU f4SFDO/nK7foHY8AXk0QDROQ6WDpaipVXonshSdRFs+vYpgiLDOAd9ko14FWVoQ8fez4LUIXL Tq8zUgesZP6kgBcmRMJKuKWLdtGCnBDV7xO8UDzIV9GmL6tC80tQF9L0PycJuHbdQpkaa0Qca Dlt/DjUuGVaB+seByQtPjGy1diqg6FvUU7g/AKCcvoVB9ySvgGacguYjFrcyUOjcODIhOrrVc gN8nGDh3HUz0h5V8qYE3lkeA5agIPHTOJiNZscqDegYy2GbMedBWdUC7sZBVm0lBnZyQOFz/2 APlhNa3tqgLVJTTi2AsiL9+ajVosMZMqaxEaTp46ctrwPQzJwV56kdY0v+EyO+D7qDkikogg1 7b+sPm+qDvZkQmZeM5y6FHJq2XHNy2odqM998DjJB3MvdqH3sQQnx01n86qZULBFClc5+iJ3U JMRuk8kBNoMqNgFYtVlxWELcSnX8HUowWFN/kPdPZolY2/PkYKzdel4QWPB0eDAX9Pj7JAd1z EoX8KhtmbolkfYS4kbQvtHDKpittsKRTxPVj/7UWyW6YtL6/RdADEdzwFZbbHSyXqAveIvQ6F FAwOlSaa0Z19OIAr Subject: Re: RFC: Yocto LTS? X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: chris@2net.co.uk 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 15:12:16 -0000 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Hi, On 14/10/15 14:50, akuster808 wrote: > 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 > Thanks, Armin, that is the kind of thing I was looking for. It doesn't mention a timespan for updates, but there does seem to be an implicit maintenance period of 12 months after release. I am still worried that this is a rather short period of time, though, and encourages device manufacturers to avoid ever updating boxes in the field. >> >> Regards, >> Chris Simmonds >> >