I'm posting this to openembedded-architecture since it probably is the best place for discussions about OE/Yocto planning.
The Yocto Project TSC believes one of the things needed for YP and for OE is more information being pulled together about how an LTS release could work. The document linked to below is the information it was able to collate together on the subject. Its the result of some long discussions by the TSC. The aim was to document the background of YP releases, what works, what challenges we have and to put in place some initial ideas/decisions about how an LTS could work and what the requirements for it would be. There has been a lot of discussion about this before, on mailing lists, at meetings like OEDEM/OEDAM, in hallways and over meals at conferences, direct company experiences and more. The TSC have tried to collect in much of the information we've seen/heard/experienced over the past few years. What we wanted to try and avoid is non-productive discussion, so this document gives a baseline to work from. It is not a finished proposal and we appreciate one size will not fit all. We believe the people who end up doing the work will have significant input into some of the decisions. The key thing needed to make this happen is a resource commitment to it. Without such a commitment it is simply not feasible. There may be new companies willing to join the project in order to make it happen, if so we should talk further. The document: https://docs.google.com/document/d/1AwAFDf52f_FoXksbHEVUMlu4hpcI0JMGVG-Kj_sUkyc/ Ultimately this may go to the wiki, I couldn't face wrestling with the formatting right now. The TSC wanted to share this before ELC-E as it may form the basis for some discusions. There are some other topics the TSC is considering working on a similar document for. Cheers, Richard [on behalf of the YP TSC] _______________________________________________ Openembedded-architecture mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
