{"action":"created","issue":{"url":"https://api.github.com/repos/radiasoft/devops/issues/59","repository_url":"https://api.github.com/repos/radiasoft/devops","labels_url":"https://api.github.com/repos/radiasoft/devops/issues/59/labels{/name}","comments_url":"https://api.github.com/repos/radiasoft/devops/issues/59/comments","events_url":"https://api.github.com/repos/radiasoft/devops/issues/59/events","html_url":"https://github.com/radiasoft/devops/issues/59","id":188002037,"number":59,"title":"github install channels","user":{"login":"robnagler","id":5495179,"avatar_url":"https://avatars.githubusercontent.com/u/5495179?v=3","gravatar_id":"","url":"https://api.github.com/users/robnagler","html_url":"https://github.com/robnagler","followers_url":"https://api.github.com/users/robnagler/followers","following_url":"https://api.github.com/users/robnagler/following{/other_user}","gists_url":"https://api.github.com/users/robnagler/gists{/gist_id}","starred_url":"https://api.github.com/users/robnagler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/robnagler/subscriptions","organizations_url":"https://api.github.com/users/robnagler/orgs","repos_url":"https://api.github.com/users/robnagler/repos","events_url":"https://api.github.com/users/robnagler/events{/privacy}","received_events_url":"https://api.github.com/users/robnagler/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-11-08T14:14:07Z","updated_at":"2016-11-08T18:29:07Z","closed_at":null,"body":"Right now we aren't tagging commits in GitHub. Even if we tagged them with versions, it would be uninteresting, because we really want a consistent install channel.\r\n\r\nI don't really have a solution for this right now, just noting that we are installing from master on GitHub unless we know that master is unreliable. With the addition of dynamic customizations to all Jupyter containers, we will probably need to start marking commits or keeping a commit list."},"comment":{"url":"https://api.github.com/repos/radiasoft/devops/issues/comments/259218679","html_url":"https://github.com/radiasoft/devops/issues/59#issuecomment-259218679","issue_url":"https://api.github.com/repos/radiasoft/devops/issues/59","id":259218679,"user":{"login":"elventear","id":45383,"avatar_url":"https://avatars.githubusercontent.com/u/45383?v=3","gravatar_id":"","url":"https://api.github.com/users/elventear","html_url":"https://github.com/elventear","followers_url":"https://api.github.com/users/elventear/followers","following_url":"https://api.github.com/users/elventear/following{/other_user}","gists_url":"https://api.github.com/users/elventear/gists{/gist_id}","starred_url":"https://api.github.com/users/elventear/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/elventear/subscriptions","organizations_url":"https://api.github.com/users/elventear/orgs","repos_url":"https://api.github.com/users/elventear/repos","events_url":"https://api.github.com/users/elventear/events{/privacy}","received_events_url":"https://api.github.com/users/elventear/received_events","type":"User","site_admin":false},"created_at":"2016-11-08T18:29:07Z","updated_at":"2016-11-08T18:29:07Z","body":"I think we should use branches, each distinct branch represents a channel, and there is a code-flow model where code is promoted between channel using git merges.  \r\n\r\nIn this model new code would flow upstream (alpha->beta->prod) manually when we believe the code has received the amount of scrutiny necessary to be promoted to the next channel. Fixes (bugs) would follow downstream. \r\n\r\nThis is a modified [git-flow](http://nvie.com/posts/a-successful-git-branching-model/), where instead of having two branches we have three.\r\n\r\nSee also:\r\n1. [Comparing git workflows](https://www.atlassian.com/git/tutorials/comparing-workflows) "}}
{"actor":{"display_login":"elventear"}}