|
|
42.
|
|
|
Quick Summary
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/99_community_book.rst:50
|
|
|
43.
|
|
|
To download the latest sources and create your own local branches of OpenERP, do this::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/99_community_book.rst:52
|
|
|
44.
|
|
|
This will download all the component of openerp (server, client, addons) and create links of modules in addons in 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.::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/1_1_Introduction/2_launchpad.rst:106
|
|
|
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::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/1_1_Introduction/2_launchpad.rst:112
|
|
|
46.
|
|
|
After having done that, your branch is public on Launchpad, in the `OpenObject project <https://code.launchpad.net/openobject>`_, and commiters 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``)::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/1_1_Introduction/2_launchpad.rst:121
../../source/developer/1_1_Introduction/2_launchpad.rst:180
|
|
|
47.
|
|
|
If your changes fixe a public bug on launchpad, you can use this to mark the bug as fixed by your branch::
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/1_1_Introduction/2_launchpad.rst:131
|
|
|
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 commiter and then the quality team to be merged in the official release.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/1_1_Introduction/2_launchpad.rst:135
../../source/developer/1_1_Introduction/2_launchpad.rst:194
|
|
|
49.
|
|
|
[Read more about :ref:`OpenERP Team <openerp-team>`]
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/99_community_book.rst:97
|
|
|
50.
|
|
|
Pushing a new branch
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/99_community_book.rst:100
|
|
|
51.
|
|
|
If you want to contribute on OpenERP or OpenObject, here is the proposed method:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/developer/99_community_book.rst:102
../../source/developer/99_community_book.rst:159
../../source/developer/99_community_book.rst:294
|
