Browsing French translation

43.

To download the latest sources and create your own local branches of OpenERP, do this::

44.

This will download all components of openerp (server, client, addons) and create links of modules in addons on your server so that you can use it directly. You can change the bzr_set.py file to select what you want to download exactly. Now, you can edit the code and commit in your local branch.::

45.

Once your code is good enough and follow the :ref:`coding-guidelines-link`, you can push your branch in launchpad. You may have to create an account on launchpad first, register your public key, and subscribe to the `openerp-community <https://launchpad.net/~openerp-community>`_ team. Then, you can push your branch. Suppose you want to push your addons::

46.

After having done that, your branch is public on Launchpad, in the `OpenObject project <https://code.launchpad.net/openobject>`_, and committers can work on it, review it and propose for integration in the official branch. The last line allows you to rebind your branch to the one which is on launchpad, after having done this, your commit will be applied on launchpad directly (unless you use ``--local``)::

47.

If your changes fix a public bug on launchpad, you can use this to mark the bug as fixed by your branch::

48.

Once your branch is mature, mark it as mature in the web interface of launchpad and request for merging in the official release. Your branch will be reviewed by a committer and then the quality team to be merged in the official release.

49.

[Read more about :ref:`OpenERP Team <openerp-team>`]

50.

Pushing a new branch

51.

If you want to contribute on OpenERP or OpenObject, here is the proposed method:

52.

You create a branch on launchpad on the project that interests you. It's important that you create your branch on launchpad and not on your local system so that we can easily merge, share code between projects and centralize future developments.