{"action":"closed","issue":{"url":"https://api.github.com/repos/kubernetes/test-infra/issues/3415","repository_url":"https://api.github.com/repos/kubernetes/test-infra","labels_url":"https://api.github.com/repos/kubernetes/test-infra/issues/3415/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/test-infra/issues/3415/comments","events_url":"https://api.github.com/repos/kubernetes/test-infra/issues/3415/events","html_url":"https://github.com/kubernetes/test-infra/issues/3415","id":241833835,"number":3415,"title":"Track release notes per-deliverable","user":{"login":"lavalamp","id":647318,"avatar_url":"https://avatars0.githubusercontent.com/u/647318?v=4","gravatar_id":"","url":"https://api.github.com/users/lavalamp","html_url":"https://github.com/lavalamp","followers_url":"https://api.github.com/users/lavalamp/followers","following_url":"https://api.github.com/users/lavalamp/following{/other_user}","gists_url":"https://api.github.com/users/lavalamp/gists{/gist_id}","starred_url":"https://api.github.com/users/lavalamp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lavalamp/subscriptions","organizations_url":"https://api.github.com/users/lavalamp/orgs","repos_url":"https://api.github.com/users/lavalamp/repos","events_url":"https://api.github.com/users/lavalamp/events{/privacy}","received_events_url":"https://api.github.com/users/lavalamp/received_events","type":"User","site_admin":false},"labels":[{"id":772065586,"url":"https://api.github.com/repos/kubernetes/test-infra/labels/lifecycle/rotten","name":"lifecycle/rotten","color":"604460","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2017-07-10T20:13:45Z","updated_at":"2018-03-01T15:07:52Z","closed_at":"2018-03-01T15:07:52Z","author_association":"OWNER","body":"Repos in the staging directory are published and consumed piecemeal by others. We need a way to provide accurate CHANGELOGs / release notes.\r\n\r\nI suggest a tool that does this for each library in staging, for each change to the main repo:\r\n\r\n* Use the go compilation libraries to evaluate if the change would cause a change in the public interface of staging/xxx.\r\n* If so, require an xxx-release-note in the PR.\r\n\r\nThen the release notes can be compiled at will.\r\n\r\n(Example: A change to the API types repo requires a client-go-release-note, since client-go users will need to change their code to upgrade.)"}}
{"actor":{"display_login":"k8s-ci-robot"}}