{"action":"created","issue":{"url":"https://api.github.com/repos/bokeh/bokeh/issues/2199","labels_url":"https://api.github.com/repos/bokeh/bokeh/issues/2199/labels{/name}","comments_url":"https://api.github.com/repos/bokeh/bokeh/issues/2199/comments","events_url":"https://api.github.com/repos/bokeh/bokeh/issues/2199/events","html_url":"https://github.com/bokeh/bokeh/issues/2199","id":69846419,"number":2199,"title":"Branching/Release process discussion","user":{"login":"bryevdv","id":1078448,"avatar_url":"https://avatars.githubusercontent.com/u/1078448?v=3","gravatar_id":"","url":"https://api.github.com/users/bryevdv","html_url":"https://github.com/bryevdv","followers_url":"https://api.github.com/users/bryevdv/followers","following_url":"https://api.github.com/users/bryevdv/following{/other_user}","gists_url":"https://api.github.com/users/bryevdv/gists{/gist_id}","starred_url":"https://api.github.com/users/bryevdv/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bryevdv/subscriptions","organizations_url":"https://api.github.com/users/bryevdv/orgs","repos_url":"https://api.github.com/users/bryevdv/repos","events_url":"https://api.github.com/users/bryevdv/events{/privacy}","received_events_url":"https://api.github.com/users/bryevdv/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/bokeh/bokeh/labels/type:%20discussion","name":"type: discussion","color":"2659A0"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":12,"created_at":"2015-04-21T13:28:39Z","updated_at":"2015-04-24T01:38:23Z","closed_at":null,"body":"Need to clarify release branching strategy. Motivation: A few releases have had longer testing/build cycles and several PRs that were ready and could have been merged to master were stalled, waiting for the release to complete. Need a process that allows normal dev to continue separately while a release is pending. \r\n\r\nThere are basically two proposals that I am aware of:\r\n* Adopt something similar to git-workflow, where the tip of `master` is always the last release, and normal dev takes place off a `dev` branch. A longer example can be found here: http://travisswicegood.com/2015/03/18/workflow-with-git/  \r\n\r\n* Alternatively, have a more defined policy for when to split off a (temporary) release branch. Presumably this should occur exactly with a  code freeze so that any release related hot fixes or doc/examples updates would go on the branch and normal dev could continue on `master`\r\n\r\nThoughts? @bokeh/dev @tswicegood @pzwang "},"comment":{"url":"https://api.github.com/repos/bokeh/bokeh/issues/comments/95770501","html_url":"https://github.com/bokeh/bokeh/issues/2199#issuecomment-95770501","issue_url":"https://api.github.com/repos/bokeh/bokeh/issues/2199","id":95770501,"user":{"login":"bryevdv","id":1078448,"avatar_url":"https://avatars.githubusercontent.com/u/1078448?v=3","gravatar_id":"","url":"https://api.github.com/users/bryevdv","html_url":"https://github.com/bryevdv","followers_url":"https://api.github.com/users/bryevdv/followers","following_url":"https://api.github.com/users/bryevdv/following{/other_user}","gists_url":"https://api.github.com/users/bryevdv/gists{/gist_id}","starred_url":"https://api.github.com/users/bryevdv/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bryevdv/subscriptions","organizations_url":"https://api.github.com/users/bryevdv/orgs","repos_url":"https://api.github.com/users/bryevdv/repos","events_url":"https://api.github.com/users/bryevdv/events{/privacy}","received_events_url":"https://api.github.com/users/bryevdv/received_events","type":"User","site_admin":false},"created_at":"2015-04-24T01:38:23Z","updated_at":"2015-04-24T01:38:23Z","body":"Agreed. On a purely conceptual level I love the idea of stabilizing as many CIO dev efforts as possible around a common or mostly common process but that's not a trivial task and it's a question whether the benefit outweighs the cost. "}}