{"action":"created","issue":{"url":"https://api.github.com/repos/NativeScript/NativeScript/issues/797","labels_url":"https://api.github.com/repos/NativeScript/NativeScript/issues/797/labels{/name}","comments_url":"https://api.github.com/repos/NativeScript/NativeScript/issues/797/comments","events_url":"https://api.github.com/repos/NativeScript/NativeScript/issues/797/events","html_url":"https://github.com/NativeScript/NativeScript/issues/797","id":107657722,"number":797,"title":"Semantic versioning in {N}?","user":{"login":"emiloberg","id":4673048,"avatar_url":"https://avatars.githubusercontent.com/u/4673048?v=3","gravatar_id":"","url":"https://api.github.com/users/emiloberg","html_url":"https://github.com/emiloberg","followers_url":"https://api.github.com/users/emiloberg/followers","following_url":"https://api.github.com/users/emiloberg/following{/other_user}","gists_url":"https://api.github.com/users/emiloberg/gists{/gist_id}","starred_url":"https://api.github.com/users/emiloberg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/emiloberg/subscriptions","organizations_url":"https://api.github.com/users/emiloberg/orgs","repos_url":"https://api.github.com/users/emiloberg/repos","events_url":"https://api.github.com/users/emiloberg/events{/privacy}","received_events_url":"https://api.github.com/users/emiloberg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-09-22T07:07:07Z","updated_at":"2015-09-23T13:42:14Z","closed_at":null,"body":"Hi,\r\n\r\nWhat is NativeScript's take on semantic versioning? \r\n\r\nSearching the issues and looking at the code gives that NativeScript tries to do semver. However, the latest 1.3.0 release included #473 which is a breaking change and should, according to so semver standards, have bumped the version number to 2.0. Same thing with 1.2.0 which contained the breaking change #304 and 1.1.0 which contained breaking change #242.\r\n\r\nNow, when {N} is becoming more and more modularized (yay!), a more rigid adherence to semver would probably make our developing lives a tiny bit easier.\r\n\r\nIt would also mean that we could safely change the tns-core-modules dependency from a fixed version:\r\n```\r\n\"dependencies\": {\r\n   \"tns-core-modules\": \"1.3.0\",\r\n}\r\n```\r\n...into a 'no breaking changes' version (n.b. the caret):\r\n```\r\n   \"tns-core-modules\": \"^1.3.0\",\r\n```\r\n\r\nOne downside to this is that one might hold back on releasing new functionality/fixes if it bumps a major number. However, that is - as I see it - a mental block, which could be overcome."},"comment":{"url":"https://api.github.com/repos/NativeScript/NativeScript/issues/comments/142604840","html_url":"https://github.com/NativeScript/NativeScript/issues/797#issuecomment-142604840","issue_url":"https://api.github.com/repos/NativeScript/NativeScript/issues/797","id":142604840,"user":{"login":"enchev","id":5804953,"avatar_url":"https://avatars.githubusercontent.com/u/5804953?v=3","gravatar_id":"","url":"https://api.github.com/users/enchev","html_url":"https://github.com/enchev","followers_url":"https://api.github.com/users/enchev/followers","following_url":"https://api.github.com/users/enchev/following{/other_user}","gists_url":"https://api.github.com/users/enchev/gists{/gist_id}","starred_url":"https://api.github.com/users/enchev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/enchev/subscriptions","organizations_url":"https://api.github.com/users/enchev/orgs","repos_url":"https://api.github.com/users/enchev/repos","events_url":"https://api.github.com/users/enchev/events{/privacy}","received_events_url":"https://api.github.com/users/enchev/received_events","type":"User","site_admin":false},"created_at":"2015-09-23T13:42:14Z","updated_at":"2015-09-23T13:42:14Z","body":"Hi @NathanaelA \r\nActually cssClass -> class is not a breaking change - just a new custom attribute support in the XML. :)\r\n\r\nOur cssClass property is untouched!\r\n"}}