{"action":"created","issue":{"url":"https://api.github.com/repos/retailcoder/Rubberduck/issues/288","labels_url":"https://api.github.com/repos/retailcoder/Rubberduck/issues/288/labels{/name}","comments_url":"https://api.github.com/repos/retailcoder/Rubberduck/issues/288/comments","events_url":"https://api.github.com/repos/retailcoder/Rubberduck/issues/288/events","html_url":"https://github.com/retailcoder/Rubberduck/issues/288","id":59938297,"number":288,"title":"Do we need a \"development\" branch?","user":{"login":"ckuhn203","id":2716800,"avatar_url":"https://avatars.githubusercontent.com/u/2716800?v=3","gravatar_id":"","url":"https://api.github.com/users/ckuhn203","html_url":"https://github.com/ckuhn203","followers_url":"https://api.github.com/users/ckuhn203/followers","following_url":"https://api.github.com/users/ckuhn203/following{/other_user}","gists_url":"https://api.github.com/users/ckuhn203/gists{/gist_id}","starred_url":"https://api.github.com/users/ckuhn203/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ckuhn203/subscriptions","organizations_url":"https://api.github.com/users/ckuhn203/orgs","repos_url":"https://api.github.com/users/ckuhn203/repos","events_url":"https://api.github.com/users/ckuhn203/events{/privacy}","received_events_url":"https://api.github.com/users/ckuhn203/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/retailcoder/Rubberduck/labels/discussion","name":"discussion","color":"FEFEFE"},{"url":"https://api.github.com/repos/retailcoder/Rubberduck/labels/meta","name":"meta","color":"FEFEFE"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-03-05T11:20:19Z","updated_at":"2015-03-05T12:27:09Z","closed_at":null,"body":"Yesterdays release, and the subsequent bug fixes I pushed to master have me wondering if we need a better branch/release strategy. We both know that, in theory, `master` should be the latest stable build, but often that isn't true. We're both guilty of treating `master` as a development branch as we work toward new releases. \r\n\r\nI was doing some [reading](http://nvie.com/posts/a-successful-git-branching-model/) and this seems like a good approach to me. The core idea is that, by definition, a commit to master is a release. All development happens in a `next` branch. When getting close to a release (think our last pre-release) we create a branch for it, and nothing but bug fixes go in after that. New features created after the `release` branch has been developed have to go into `next`. Production bug fixes get merged into both the `master` and `release` branch. \r\n\r\nThere's a couple of benefits to this as far as I can tell. The biggest being we would never find ourselves in a situation where we have to wait for the next minor release to release bug fixes found in production. \r\n\r\n![Branch diagram][1]\r\n\r\n  [1]:http://nvie.com/img/git-model@2x.png\r\n"},"comment":{"url":"https://api.github.com/repos/retailcoder/Rubberduck/issues/comments/77355491","html_url":"https://github.com/retailcoder/Rubberduck/issues/288#issuecomment-77355491","issue_url":"https://api.github.com/repos/retailcoder/Rubberduck/issues/288","id":77355491,"user":{"login":"retailcoder","id":5751684,"avatar_url":"https://avatars.githubusercontent.com/u/5751684?v=3","gravatar_id":"","url":"https://api.github.com/users/retailcoder","html_url":"https://github.com/retailcoder","followers_url":"https://api.github.com/users/retailcoder/followers","following_url":"https://api.github.com/users/retailcoder/following{/other_user}","gists_url":"https://api.github.com/users/retailcoder/gists{/gist_id}","starred_url":"https://api.github.com/users/retailcoder/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/retailcoder/subscriptions","organizations_url":"https://api.github.com/users/retailcoder/orgs","repos_url":"https://api.github.com/users/retailcoder/repos","events_url":"https://api.github.com/users/retailcoder/events{/privacy}","received_events_url":"https://api.github.com/users/retailcoder/received_events","type":"User","site_admin":false},"created_at":"2015-03-05T12:27:09Z","updated_at":"2015-03-05T12:27:09Z","body":"Sure! The sooner the better!"}}