{"_id":"553d394e9660ba0d00569d22","user":"543466ea0e8e2b0e00341818","githubsync":"","version":{"_id":"553d394d9660ba0d00569d07","project":"543467200ef9c00800164ecc","forked_from":"54bedb2fffb79c320030db1f","__v":1,"createdAt":"2015-04-26T19:15:25.245Z","releaseDate":"2015-04-26T19:15:25.245Z","categories":["553d394d9660ba0d00569d08","553d394d9660ba0d00569d09"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"0.11.2","version":"0.11.2"},"__v":0,"category":{"_id":"553d394d9660ba0d00569d08","pages":["553d394e9660ba0d00569d13","553d394e9660ba0d00569d14","553d394e9660ba0d00569d15","553d394e9660ba0d00569d16","553d394e9660ba0d00569d17","553d394e9660ba0d00569d18","553d394e9660ba0d00569d19","553d394e9660ba0d00569d1a","553d394e9660ba0d00569d1b","553d394e9660ba0d00569d1c","553d394e9660ba0d00569d1d","553d394e9660ba0d00569d1e","553d394e9660ba0d00569d1f","553d394e9660ba0d00569d20","553d394e9660ba0d00569d21","553d394e9660ba0d00569d22","553d394e9660ba0d00569d23"],"project":"543467200ef9c00800164ecc","version":"553d394d9660ba0d00569d07","__v":1,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2014-10-15T18:00:23.862Z","from_sync":false,"order":0,"slug":"glim","title":"GLIM"},"project":"543467200ef9c00800164ecc","metadata":{"title":"","description":"","image":[]},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2014-10-15T18:16:05.981Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"auth":"never","params":[],"url":""},"isReference":false,"order":13,"body":"This section includes information about how to contribute to the project, versioning rules and project development workflow.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Versioning\"\n}\n[/block]\nCurrently, glim is not using any versioning standards before 1.x releases. After the 1.0 release, the project will use [semantic versioning](http://semver.org/). Currently, the versioning is used only  to seperate milestones of development. The minor version numbers increase only in bug fixes. You can check the [Roadmap & Future Releases](doc:roadmap) section for future releases and its versions.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Development Workflow\"\n}\n[/block]\nWe are using github for the issue tracking. All the issues are consolidated there. The workflow of development will be the following;\n\n- User creates a github issue.\n- If this is a bug, the issue will be replicated by admin and approved, else it will be discussed and approved.\n- Developer creates a local branch if this is a minor issue, else creates a remote branch.\n- Developer provides a pull request.\n- Admin merges from feature branch to dev branch and tests the feature requests locally.\n- Admin merges from dev branch to master branch\n\nCurrently, it is unfortunate that all the actors mentioned above is 1 person. Therefore, it is needed more and more contributors.\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Please provide tests after solving issues\",\n  \"body\": \"After the 0.11 releases of glim, writing unit tests will be an obligation.\"\n}\n[/block]","excerpt":"","slug":"contributing","type":"basic","title":"Contributing"}
This section includes information about how to contribute to the project, versioning rules and project development workflow. [block:api-header] { "type": "basic", "title": "Versioning" } [/block] Currently, glim is not using any versioning standards before 1.x releases. After the 1.0 release, the project will use [semantic versioning](http://semver.org/). Currently, the versioning is used only to seperate milestones of development. The minor version numbers increase only in bug fixes. You can check the [Roadmap & Future Releases](doc:roadmap) section for future releases and its versions. [block:api-header] { "type": "basic", "title": "Development Workflow" } [/block] We are using github for the issue tracking. All the issues are consolidated there. The workflow of development will be the following; - User creates a github issue. - If this is a bug, the issue will be replicated by admin and approved, else it will be discussed and approved. - Developer creates a local branch if this is a minor issue, else creates a remote branch. - Developer provides a pull request. - Admin merges from feature branch to dev branch and tests the feature requests locally. - Admin merges from dev branch to master branch Currently, it is unfortunate that all the actors mentioned above is 1 person. Therefore, it is needed more and more contributors. [block:callout] { "type": "info", "title": "Please provide tests after solving issues", "body": "After the 0.11 releases of glim, writing unit tests will be an obligation." } [/block]