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.
I am hoping we can get something defined by the time fido is shelved for community supported..
ideas: repo similar to "contrib" only create an LTS version if maintainer(s) identified only keep open if maintained or by EOL date
should we bring this up at OEDAM ?
Fido is now technically EOL. So I can stop sending patches in order to conform to Yocto compatibility?
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.
http://lists.openembedded.org/pipermail/openembedded-architecture/2017-January/000364.html
Once we fix bug 10888 (a dependee of this bug), we should be able to close this.
http://www.yoctoproject.org/docs/2.3/ref-manual/ref-manual.html#ref-release-process