Please see the generic MeeGo guidelines here:
Guidelines for OTS Development
- To make separating finished and unfinished features/bugfixes possible, it is extremely important that each commit contains only changes related to one user story or bugfix. If some of the stories do not get finished in time, they can be left out by not merging some of the commits to master branch. So if you implement a new feature and at the same time discover a bug, make a separate commit for the bug fix so that it can be taken into use even if the new features is not finished.
- A new feature does not need to be committed in one commit. Changes should be committed while developing. (often!)
- It's also important that each commit message clearly indicates what the commit is about and what story/bug it is related to.
Todo: Define a template for a commit message.
Developer Has Commiter Status in Gitorious
All development should be done in a separate development branches. Changes can be merged to master branch only after they have been reviewed.
Developer does not have committer status in Gitorious
Developer can clone ots repository in gitorious and use the merge request functionality after changes are ready to be merged. It's also possible to submit a patch by following the process described in MeeGo contribution page. Please read the review process before submitting.
All merge requests and patches are reviewed based on the review process.