{"action":"created","issue":{"url":"https://api.github.com/repos/klaussilveira/gitlist/issues/608","labels_url":"https://api.github.com/repos/klaussilveira/gitlist/issues/608/labels{/name}","comments_url":"https://api.github.com/repos/klaussilveira/gitlist/issues/608/comments","events_url":"https://api.github.com/repos/klaussilveira/gitlist/issues/608/events","html_url":"https://github.com/klaussilveira/gitlist/issues/608","id":97110318,"number":608,"title":"Split repositories for new version?","user":{"login":"klaussilveira","id":467729,"avatar_url":"https://avatars.githubusercontent.com/u/467729?v=3","gravatar_id":"","url":"https://api.github.com/users/klaussilveira","html_url":"https://github.com/klaussilveira","followers_url":"https://api.github.com/users/klaussilveira/followers","following_url":"https://api.github.com/users/klaussilveira/following{/other_user}","gists_url":"https://api.github.com/users/klaussilveira/gists{/gist_id}","starred_url":"https://api.github.com/users/klaussilveira/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/klaussilveira/subscriptions","organizations_url":"https://api.github.com/users/klaussilveira/orgs","repos_url":"https://api.github.com/users/klaussilveira/repos","events_url":"https://api.github.com/users/klaussilveira/events{/privacy}","received_events_url":"https://api.github.com/users/klaussilveira/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-07-24T18:29:56Z","updated_at":"2015-07-24T22:03:51Z","closed_at":null,"body":"There's a major refactoring of GitList ahead, which would mean the first major release: 1.0. However, i'm not sure if i'll even start with the current code, or just start from scratch and slowly backport stuff from the legacy codebase. \r\n\r\nIn order to continue, i need some feedback from the community: should we split the repo into two, or keep a legacy branch, and a new master for 1.0? Or the contrary (develop is 1.0, master is legacy until 1.0 is released)?"},"comment":{"url":"https://api.github.com/repos/klaussilveira/gitlist/issues/comments/124740797","html_url":"https://github.com/klaussilveira/gitlist/issues/608#issuecomment-124740797","issue_url":"https://api.github.com/repos/klaussilveira/gitlist/issues/608","id":124740797,"user":{"login":"DannyvdSluijs","id":618940,"avatar_url":"https://avatars.githubusercontent.com/u/618940?v=3","gravatar_id":"","url":"https://api.github.com/users/DannyvdSluijs","html_url":"https://github.com/DannyvdSluijs","followers_url":"https://api.github.com/users/DannyvdSluijs/followers","following_url":"https://api.github.com/users/DannyvdSluijs/following{/other_user}","gists_url":"https://api.github.com/users/DannyvdSluijs/gists{/gist_id}","starred_url":"https://api.github.com/users/DannyvdSluijs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DannyvdSluijs/subscriptions","organizations_url":"https://api.github.com/users/DannyvdSluijs/orgs","repos_url":"https://api.github.com/users/DannyvdSluijs/repos","events_url":"https://api.github.com/users/DannyvdSluijs/events{/privacy}","received_events_url":"https://api.github.com/users/DannyvdSluijs/received_events","type":"User","site_admin":false},"created_at":"2015-07-24T22:03:51Z","updated_at":"2015-07-24T22:03:51Z","body":"Lets keep the repository the same, as the requirements can shift between the milestones, and in basic this is the same project.\r\nCant we create a new (feature) branch to do the major refactoring which wont halt any PR's for fixing any current or new issues. Klaus can take his time to do the refactoring. And in time master can be forcevly merged with the feature branch.\r\n\r\nThis enables the community to move forward with bugfixing or adding unit tests which i've did a pull request for. And when Klaus is ready make the shift."}}