9037 2016-02-02 17:18:51 +0000 Consider alternate methods for maintain Yocto releases after 1yr 2017-12-06 16:52:04 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core unspecified x86 Multiple RESOLVED FIXED Medium+ enhancement 2.3 M4 10888 1 akuster richard.purdie jose.perez.carranza meta.mr.watcher meta.watcher randy.macleod richard.purdie --- --- No (bug/feature does not impact docs) oldest_to_newest 58463 0 akuster 2016-02-02 17:18:51 +0000 There is a desire to have the ability to continue to leverage fixes for Yocto releases past the one year mark. Something like the kernel stable scheme. In the case to continue to be Yocto completable, we would continue to send patches upstream and why not capture those in a community support repo for others to use. The Maintainers don't need to the volunteers for the current stable releases. could be a different set of folks. We don't need point releases IMHO. 58703 1 akuster 2016-02-07 17:36:37 +0000 I am hoping we can get something defined by the time fido is shelved for community supported.. 58934 2 akuster 2016-02-11 22:23:52 +0000 ideas: repo similar to "contrib" only create an LTS version if maintainer(s) identified only keep open if maintained or by EOL date 59800 3 akuster 2016-03-08 17:35:53 +0000 should we bring this up at OEDAM ? 63195 4 akuster 2016-06-21 14:48:52 +0000 Fido is now technically EOL. So I can stop sending patches in order to conform to Yocto compatibility? 69580 5 richard.purdie 2017-01-06 15:55:14 +0000 I've posted to the oe-arch list about this and proposed a section for the YP manual on the subject of releases, of which point releases are an important section. I think once we add that and close out on the discussion on the list we can resolve this. We probably need to update the stable maintainers wiki page too with the information once we agree it. 70178 6 richard.purdie 2017-01-26 14:06:18 +0000 http://lists.openembedded.org/pipermail/openembedded-architecture/2017-January/000364.html 70179 7 richard.purdie 2017-01-26 14:07:25 +0000 Once we fix bug 10888 (a dependee of this bug), we should be able to close this. 73053 8 richard.purdie 2017-05-04 15:24:44 +0000 http://www.yoctoproject.org/docs/2.3/ref-manual/ref-manual.html#ref-release-process