{"action":"opened","issue":{"url":"https://api.github.com/repos/GitTools/GitVersion/issues/988","repository_url":"https://api.github.com/repos/GitTools/GitVersion","labels_url":"https://api.github.com/repos/GitTools/GitVersion/issues/988/labels{/name}","comments_url":"https://api.github.com/repos/GitTools/GitVersion/issues/988/comments","events_url":"https://api.github.com/repos/GitTools/GitVersion/issues/988/events","html_url":"https://github.com/GitTools/GitVersion/issues/988","id":169906780,"number":988,"title":"How to configure GitVersion to fit our needs","user":{"login":"maxraab","id":12211887,"avatar_url":"https://avatars.githubusercontent.com/u/12211887?v=3","gravatar_id":"","url":"https://api.github.com/users/maxraab","html_url":"https://github.com/maxraab","followers_url":"https://api.github.com/users/maxraab/followers","following_url":"https://api.github.com/users/maxraab/following{/other_user}","gists_url":"https://api.github.com/users/maxraab/gists{/gist_id}","starred_url":"https://api.github.com/users/maxraab/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/maxraab/subscriptions","organizations_url":"https://api.github.com/users/maxraab/orgs","repos_url":"https://api.github.com/users/maxraab/repos","events_url":"https://api.github.com/users/maxraab/events{/privacy}","received_events_url":"https://api.github.com/users/maxraab/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-08-08T12:02:37Z","updated_at":"2016-08-08T12:02:37Z","closed_at":null,"body":"Suppose you have a big community and many contributions. Every contribution starts with a feature branch from `master` and after it's finished gets `merged` back to master. (Normal GitHub Flow). The main difference is the release stragegy:\r\n\r\nIf a release is sheduled - a new release branch (e.g. 8-1-stable, 8-2-stable, ...) is created from current `master`. From this time only some contributions gets cherry picked from `master` into the `stable branch`. All release candidates (e.g. 8.1-rc1, 8.1-rc2, ...) where tagged on this `stable branch`.\r\n\r\nIf the Version is ready to ship, the Version gets tagged but the release branch will not merged back into `master`. (To support up to 10 versions at the same time).\r\nFrom this time, the commits on `master` should have a version similar to: \"next-version\"-pre."}}
{"actor":{"display_login":"maxraab"}}