{"action":"created","issue":{"url":"https://api.github.com/repos/mojombo/semver/issues/208","labels_url":"https://api.github.com/repos/mojombo/semver/issues/208/labels{/name}","comments_url":"https://api.github.com/repos/mojombo/semver/issues/208/comments","events_url":"https://api.github.com/repos/mojombo/semver/issues/208/events","html_url":"https://github.com/mojombo/semver/issues/208","id":37707166,"number":208,"title":"Different View and Approach to Issue #200","user":{"login":"noremacskich","id":1461956,"avatar_url":"https://avatars.githubusercontent.com/u/1461956?v=3","gravatar_id":"","url":"https://api.github.com/users/noremacskich","html_url":"https://github.com/noremacskich","followers_url":"https://api.github.com/users/noremacskich/followers","following_url":"https://api.github.com/users/noremacskich/following{/other_user}","gists_url":"https://api.github.com/users/noremacskich/gists{/gist_id}","starred_url":"https://api.github.com/users/noremacskich/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/noremacskich/subscriptions","organizations_url":"https://api.github.com/users/noremacskich/orgs","repos_url":"https://api.github.com/users/noremacskich/repos","events_url":"https://api.github.com/users/noremacskich/events{/privacy}","received_events_url":"https://api.github.com/users/noremacskich/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2014-07-11T23:54:03Z","updated_at":"2015-07-28T03:02:39Z","closed_at":null,"body":"This is how I see semantic versioning being used as it currently stands. \r\n```\r\n<Public> <Insiders>\r\n\r\n<Public> ::= <Version Core>\r\n\r\n<Insiders> ::=  \"-\" <pre-release> | \"+\" <build> | \"-\" <pre-release> \"+\" <build>\r\n```\r\n\r\nThis is how I would define Public: This is the information that developers that depend on the package will want to know.  These developers are not actively contributing to the project.  \r\n\r\nAnd this is how I would define Insiders: This is the information that developers that are actively contributing to the project will want to know.  \r\n\r\nAs a side note, to me, the pre-release version and build metadata are both a “catch all”, with slightly different meanings.  That is the reasoning behind having a section called “Insiders”, since this is information that can be arbitrarily choosen by the project, and most likely will only be decipherable by the people actively working on the project.\r\n\r\n\r\n\r\nAssuming that my understanding is right, I would like to propose adding the following field:\r\n\r\n\r\n```\r\n<Type> ::= <S> | <P> | <E> | <N> | <D> | <A> | <B>\r\n\r\n<S> ::= “Stable”\r\n<P> ::= “Public”\r\n<E> ::= “Experimental”\r\n<N> ::= “Nightly”\r\n<D> ::= “Development” | “Developer”\r\n<A> ::= “Alpha”\r\n<B> ::= “Beta”\r\n```\r\nAnd using it like this:\r\n```\r\n<Type> <Public> <Insider>\r\n```\r\n\r\nThis is how I would define Type:  It is a way for developers to distinguish between various stages a project can be in.  This is just a simple list that I have started, and by no means complete.\r\n\r\nBy doing this, we risk people coming up with their own abbreviations for the Type.  To prevent this we would need to work out and agree on a list that will become a standard.\r\n\r\nThis would solve the issue of different developing styles stated in issue #200.\r\n\r\nComments are welcome."},"comment":{"url":"https://api.github.com/repos/mojombo/semver/issues/comments/125418692","html_url":"https://github.com/mojombo/semver/issues/208#issuecomment-125418692","issue_url":"https://api.github.com/repos/mojombo/semver/issues/208","id":125418692,"user":{"login":"Abdillah","id":3030950,"avatar_url":"https://avatars.githubusercontent.com/u/3030950?v=3","gravatar_id":"","url":"https://api.github.com/users/Abdillah","html_url":"https://github.com/Abdillah","followers_url":"https://api.github.com/users/Abdillah/followers","following_url":"https://api.github.com/users/Abdillah/following{/other_user}","gists_url":"https://api.github.com/users/Abdillah/gists{/gist_id}","starred_url":"https://api.github.com/users/Abdillah/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Abdillah/subscriptions","organizations_url":"https://api.github.com/users/Abdillah/orgs","repos_url":"https://api.github.com/users/Abdillah/repos","events_url":"https://api.github.com/users/Abdillah/events{/privacy}","received_events_url":"https://api.github.com/users/Abdillah/received_events","type":"User","site_admin":false},"created_at":"2015-07-28T03:02:39Z","updated_at":"2015-07-28T03:02:39Z","body":"I do feel (IMO) that your types overlap each other. Additionally, type can simply be presented in pre-release, or if SemVer agree, post-release (I do have a great taste of having `+` as post-release separator).\r\ne.g.\r\n```\r\nqirtos-2.0.3-2.1       # pre-alpha, means for experimenting, right?\r\nqirtos-2.0.3-alpha.1\r\nqirtos-2.0.3-beta.1\r\nqirtos-2.0.3-dev.1     # I assume dev is more stable than above stuffs\r\nqirtos-2.0.3           # Yay! stable, consider adding metadata: +stablebuild.20150628\r\n```\r\n\r\nAs for `public`, in open source all is public, right? If you mean public consumption, stable also means that one."}}