{"action":"opened","issue":{"url":"https://api.github.com/repos/mojombo/semver/issues/340","repository_url":"https://api.github.com/repos/mojombo/semver","labels_url":"https://api.github.com/repos/mojombo/semver/issues/340/labels{/name}","comments_url":"https://api.github.com/repos/mojombo/semver/issues/340/comments","events_url":"https://api.github.com/repos/mojombo/semver/issues/340/events","html_url":"https://github.com/mojombo/semver/issues/340","id":185240635,"number":340,"title":"Add another number to semver","user":{"login":"corysimmons","id":224636,"avatar_url":"https://avatars.githubusercontent.com/u/224636?v=3","gravatar_id":"","url":"https://api.github.com/users/corysimmons","html_url":"https://github.com/corysimmons","followers_url":"https://api.github.com/users/corysimmons/followers","following_url":"https://api.github.com/users/corysimmons/following{/other_user}","gists_url":"https://api.github.com/users/corysimmons/gists{/gist_id}","starred_url":"https://api.github.com/users/corysimmons/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/corysimmons/subscriptions","organizations_url":"https://api.github.com/users/corysimmons/orgs","repos_url":"https://api.github.com/users/corysimmons/repos","events_url":"https://api.github.com/users/corysimmons/events{/privacy}","received_events_url":"https://api.github.com/users/corysimmons/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-25T21:36:15Z","updated_at":"2016-10-25T21:36:15Z","closed_at":null,"body":"People are always afraid to to do breaking changes because it means a major ver bump.\r\n\r\nThe very-real/valid problem is explained well in this presentation: https://www.youtube.com/watch?v=tc2UgG5L7WM\r\n\r\nThey typically store up 50 million commits in a separate branch they need to maintain, and then launch all these breaking changes at once.\r\n\r\nWhy not add a fourth field to semver specifically for marketing purposes?\r\n\r\n`1.9999.0` -> `2.0.0.0` could be marketed as \"Holy crap! FooProj 2 is here! Check out the migration guide!\"\r\n\r\nThis might be a minor change (from `1.9999.0` to `2.0.0.0`) but the only people who would know that are the people closely following the project.\r\n\r\nThis would allow for the project to advance & iterate quickly, while encouraging more users to adhere to semver strictly -- directly in `master` in a lot of cases.\r\n\r\nI know this sort of change would require package management systems to upgrade and add another symbol for this sort of change, but I think it'd be beneficial:\r\n\r\n0. Allow people/projects to get to 1.0.0 quickly (how many years was Node production-ready, but still not 1.x?)\r\n0. Allow maintainers to quickly iterate with breaking changes while adhering to semver and _not_ breaking builds.\r\n0. Allow maintainers to do marketing releases where they educated users on a plethora of breaking changes all at once rather than forcing the user to track/remember every little breaking change along the way.\r\n\r\nLet me know your thoughts, but I've been thinking this for years and have heard other people independently wonder why this feature doesn't exist.\r\n\r\nSemVer 3.0.0.0 pls! 😻"}}
{"actor":{"display_login":"corysimmons"}}