{"action":"created","issue":{"url":"https://api.github.com/repos/coreos/fedora-coreos-tracker/issues/80","repository_url":"https://api.github.com/repos/coreos/fedora-coreos-tracker","labels_url":"https://api.github.com/repos/coreos/fedora-coreos-tracker/issues/80/labels{/name}","comments_url":"https://api.github.com/repos/coreos/fedora-coreos-tracker/issues/80/comments","events_url":"https://api.github.com/repos/coreos/fedora-coreos-tracker/issues/80/events","html_url":"https://github.com/coreos/fedora-coreos-tracker/issues/80","id":378996384,"node_id":"MDU6SXNzdWUzNzg5OTYzODQ=","number":80,"title":"Talk to Fedora kernel team about FCOS stream design","user":{"login":"bgilbert","id":361374,"node_id":"MDQ6VXNlcjM2MTM3NA==","avatar_url":"https://avatars1.githubusercontent.com/u/361374?v=4","gravatar_id":"","url":"https://api.github.com/users/bgilbert","html_url":"https://github.com/bgilbert","followers_url":"https://api.github.com/users/bgilbert/followers","following_url":"https://api.github.com/users/bgilbert/following{/other_user}","gists_url":"https://api.github.com/users/bgilbert/gists{/gist_id}","starred_url":"https://api.github.com/users/bgilbert/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bgilbert/subscriptions","organizations_url":"https://api.github.com/users/bgilbert/orgs","repos_url":"https://api.github.com/users/bgilbert/repos","events_url":"https://api.github.com/users/bgilbert/events{/privacy}","received_events_url":"https://api.github.com/users/bgilbert/received_events","type":"User","site_admin":false},"labels":[{"id":1054522476,"node_id":"MDU6TGFiZWwxMDU0NTIyNDc2","url":"https://api.github.com/repos/coreos/fedora-coreos-tracker/labels/priority/medium","name":"priority/medium","color":"fef2c0","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2018-11-09T02:21:05Z","updated_at":"2018-12-14T19:51:29Z","closed_at":null,"author_association":"MEMBER","body":"The FCOS stream design (#22, #72) has two elements that affect the kernel:\r\n\r\n- When there's a kernel fix that requires an out-of-cycle FCOS release, it may be desirable to backport the fix to kernels already in the affected streams rather than pushing a new kernel release to those streams.  Container Linux currently does this for its stable channel to reduce the impact of [user-facing regressions](https://lists.linuxfoundation.org/pipermail/ksummit-discuss/2018-September/005287.html) in stable kernels.  See #79 for associated branch tooling.\r\n- The `next` stream will track the upcoming kernel from rc6 until the kernel reaches Bodhi `updates`.  The idea is that, while every other major package bump in FCOS bakes in `next` for a substantial time before being promoted, new kernel versions would normally only bake for two weeks in `testing` because they flow directly into Fedora stable releases.  The additional kernel coverage in `next` will provide a few weeks of additional baking time for catching regressions.  This will require tooling support as part of #77.\r\n\r\nAsk the Fedora kernel team what they think of all this."},"comment":{"url":"https://api.github.com/repos/coreos/fedora-coreos-tracker/issues/comments/447435727","html_url":"https://github.com/coreos/fedora-coreos-tracker/issues/80#issuecomment-447435727","issue_url":"https://api.github.com/repos/coreos/fedora-coreos-tracker/issues/80","id":447435727,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0NzQzNTcyNw==","user":{"login":"labbott","id":5463647,"node_id":"MDQ6VXNlcjU0NjM2NDc=","avatar_url":"https://avatars2.githubusercontent.com/u/5463647?v=4","gravatar_id":"","url":"https://api.github.com/users/labbott","html_url":"https://github.com/labbott","followers_url":"https://api.github.com/users/labbott/followers","following_url":"https://api.github.com/users/labbott/following{/other_user}","gists_url":"https://api.github.com/users/labbott/gists{/gist_id}","starred_url":"https://api.github.com/users/labbott/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/labbott/subscriptions","organizations_url":"https://api.github.com/users/labbott/orgs","repos_url":"https://api.github.com/users/labbott/repos","events_url":"https://api.github.com/users/labbott/events{/privacy}","received_events_url":"https://api.github.com/users/labbott/received_events","type":"User","site_admin":false},"created_at":"2018-12-14T19:51:29Z","updated_at":"2018-12-14T19:51:29Z","author_association":"NONE","body":"You've probably heard this before but just for the record: Trying to selectively pick up commits is not recommended by upstream. It's difficult to know if any commit will become a security issue or not so best practice is to pick them all up. It also may be difficult to do backporting of individual fixes if there's a diff between versions.\r\n\r\nThat said, that message is usually intended at people who never want to pick up stable updates. Choosing to only pick up known critical fixes vs. entire stable updates for a fixed time period could be an option as long as you realize the tradeoffs. If you're already holding back on stable updates (i.e. FCOS is a few stable versions behind Fedora) I don't think you've lost too much by choosing to just give just the critical fixes. I'd only suggest doing this for the most critical of issues though and would advocate for \"just take the full stable update\" be the default option for most issues.\r\n\r\nI like the idea Justin proposed as well and I think it would be a good supplement. Long term the goal is to increase the confidence in stable updates to make everyone's life easier."}}
{"actor":{"display_login":"labbott"}}