{"comment":{"created_at":"2011-10-20T10:42:13Z","body":"Makes sense. I guess I was just confused to hear the immediate next release won't come from `integration` without having a `2.3` release yet.","updated_at":"2011-10-20T10:42:13Z","url":"https://api.github.com/repos/symphonycms/symphony-2/issues/comments/2467097","id":2467097,"user":{"avatar_url":"https://secure.gravatar.com/avatar/b18fc48caab5bf7c3e2a15292972f05b?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"b18fc48caab5bf7c3e2a15292972f05b","url":"https://api.github.com/users/nils-werner","id":88704,"login":"nils-werner"}},"action":"created","issue":{"number":851,"created_at":"2011-10-20T10:06:16Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"I've been having a chat with @nils-werner on Twitter about the topic. I was wondering...\r\n\r\nWouldn't it be better to have a `bugfixes` branch for minor releases (e.g. Symphony 2.2.4) development, instead of having `2.1.x` or `2.2.x` ? This way we can use `integration` for the next major release (e.g. Symphony 2.3) without being afraid of where to push changes.\r\n","comments":3,"title":"Concerning GIT, branches and versions development","updated_at":"2011-10-20T10:42:13Z","url":"https://api.github.com/repos/symphonycms/symphony-2/issues/851","id":2003272,"assignee":null,"milestone":null,"closed_at":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/1b32fae892ca31c0f0c46eb7c7cc3964?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"1b32fae892ca31c0f0c46eb7c7cc3964","url":"https://api.github.com/users/eKoeS","id":170682,"login":"eKoeS"},"html_url":"https://github.com/symphonycms/symphony-2/issues/851","labels":[],"state":"open"},"legacy":{"issue_id":2003272,"comment_id":2467097}}