{"action":"opened","issue":{"url":"https://api.github.com/repos/kubernetes/test-infra/issues/2824","repository_url":"https://api.github.com/repos/kubernetes/test-infra","labels_url":"https://api.github.com/repos/kubernetes/test-infra/issues/2824/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/test-infra/issues/2824/comments","events_url":"https://api.github.com/repos/kubernetes/test-infra/issues/2824/events","html_url":"https://github.com/kubernetes/test-infra/issues/2824","id":230514102,"number":2824,"title":"Testing for hotfix branches (release-X.Y.Z)","user":{"login":"enisoc","id":6733629,"avatar_url":"https://avatars0.githubusercontent.com/u/6733629?v=3","gravatar_id":"","url":"https://api.github.com/users/enisoc","html_url":"https://github.com/enisoc","followers_url":"https://api.github.com/users/enisoc/followers","following_url":"https://api.github.com/users/enisoc/following{/other_user}","gists_url":"https://api.github.com/users/enisoc/gists{/gist_id}","starred_url":"https://api.github.com/users/enisoc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/enisoc/subscriptions","organizations_url":"https://api.github.com/users/enisoc/orgs","repos_url":"https://api.github.com/users/enisoc/repos","events_url":"https://api.github.com/users/enisoc/events{/privacy}","received_events_url":"https://api.github.com/users/enisoc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-05-22T20:45:05Z","updated_at":"2017-05-22T20:45:05Z","closed_at":null,"body":"For the v1.6.4 release, we used a feature of anago to [branch from a previous patch release](https://github.com/kubernetes/release/blob/master/docs/branching.md#branching-from-a-tag), creating a `release-1.6.3` branch to exclude changes on the `release-1.6` branch since v1.6.3.\r\n\r\nUnlike regular `release-X.Y` branches, the urgent nature of hotfix releases means we can't go through the usual flow to set up CI on the new branch. We should have a documented workflow for release managers to trigger one-off testing on `release-X.Y.Z` branches, based on the jobs that run for `release-X.Y`.\r\n\r\ncc @david-mcmahon @ixdy "}}
{"actor":{"display_login":"enisoc"}}