{% set title = "How to Develop" %}
{% extends "layout-toc.html" %}
{% block content %}
{{ title }}
TL;DR
Clone the repository:
$ hg clone https://hg.tryton.org/trytond
$ cd trytond
Make your modification. Submit your change:
$ -L -o ~/.local/bin/upload.py https://codereview.tryton.org/static/upload.py
$ python ~/.local/bin/upload.py --oauth2
There are two options to upload changes:
Download upload.py and read its help page.
There is a mercurial extension, hgreview which simplifies the workflow.
Install the extension:
$ pip install hgreview
$ hg config -e -l
Edit the file to include:
[extensions]
hgreview =
[review]
server = https://codereview.tryton.org
oauth2 = True
send_email = True
You can then upload your change (do not commit before doing this):
$ hg review -m "repository_name: Improve things a lot"
For non-trunk fixes append the series number to the repository name.
This part is only for core developers
Push to the remote server:
$ hg push ssh://hg@hg.tryton.org/trytond
Sometimes the push is rejected because it creates a new head.
This happens because your local repository is not up to date.$ hg pull --rebase
environment repository up to date with all the subrepos:
Always keep the$ hg commit -S --cwd tryton-env
The Tryton Project strongly recommends the following guidelines.
Code style, in general, follows PEP 8:
Your contribution must meet the following requirements:
Name <email>
If the contributor has a significant amount of code, he can add himself to the COPYRIGHT file.
Core developers are people which have push access to the repositories. They are allowed to push small fixes without review. Bigger fixes need approval from other core developers.
In the case of disagreement, a consensus should be reached. As a last resort, the project leader (Cédric Krier) will make the decision.
A fix will be back ported to older series by the maintainer on his own discretion after 1 week in the development branch. The decision is based on the importance of the bug, the availability of workaround and the feasibilities.
Those rules don't apply for security bugs which are applied at once to all affected series and followed by a release.