Bug 9037

Summary: Consider alternate methods for maintain Yocto releases after 1yr
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Armin Kuster <akuster>
Component: coreAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium+ CC: jose.perez.carranza, meta.mr.watcher, meta.watcher, randy.macleod, richard.purdie
Version: unspecified   
Target Milestone: 2.3 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on: 10888    
Bug Blocks:    

Description Armin Kuster 2016-02-02 17:18:51 UTC 
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.
Comment 1 Armin Kuster 2016-02-07 17:36:37 UTC 
I am hoping we can get something defined by the time fido is shelved for community supported..
Comment 2 Armin Kuster 2016-02-11 22:23:52 UTC 
ideas:

repo similar to "contrib"

only create an LTS version if maintainer(s) identified

only keep open if maintained or by EOL date
Comment 3 Armin Kuster 2016-03-08 17:35:53 UTC 
should we bring this up at OEDAM ?
Comment 4 Armin Kuster 2016-06-21 14:48:52 UTC 
Fido is now technically EOL. So I can stop sending patches in order to conform to Yocto compatibility?
Comment 5 Richard Purdie 2017-01-06 15:55:14 UTC 
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.
Comment 7 Richard Purdie 2017-01-26 14:07:25 UTC 
Once we fix bug 10888 (a dependee of this bug), we should be able to close this.