11
.. i18n: Launchpad and bazaar
12
.. i18n: --------------------
18
.. i18n: Before you can commit on launchpad, you have to create a login. This login is needed if you intend to commit on openerp-comiter or on your own branch via bazaar. Go to: https://launchpad.net --> log in / register on top right.
21
Before you can commit on launchpad, you have to create a login. This login is needed if you intend to commit on openerp-comiter or on your own branch via bazaar. Go to: https://launchpad.net --> log in / register on top right.
23
.. i18n: Enter your e-mail address and wait for an e-mail which will guide you trough the login creation process.
26
Enter your e-mail address and wait for an e-mail which will guide you trough the login creation process.
28
.. i18n: You can then refer to this link :
29
.. i18n: https://help.launchpad.net/YourAccount/NewAccount
32
You can then refer to this link :
33
https://help.launchpad.net/YourAccount/NewAccount
35
.. i18n: Any contributor who is interested to become a committer must show his interest
36
.. i18n: on working for openerp project and ability to do it properly as
37
.. i18n: selection is based on merit. It can be by proposing bug
38
.. i18n: fixes, features requested on our :ref:`bug tracker <bug-tracker-link>` system.
39
.. i18n: You can even suggest additional modules and/or functionality on our :ref:`bug
40
.. i18n: tracker <bug-tracker-link>` system.
43
Any contributor who is interested to become a committer must show his interest
44
on working for openerp project and ability to do it properly as
45
selection is based on merit. It can be by proposing bug
46
fixes, features requested on our :ref:`bug tracker <bug-tracker-link>` system.
47
You can even suggest additional modules and/or functionality on our :ref:`bug
48
tracker <bug-tracker-link>` system.
50
.. i18n: You can contribute or join OpenERP team, : https://help.launchpad.net/Teams/Joining
53
You can contribute or join OpenERP team, : https://help.launchpad.net/Teams/Joining
55
.. i18n: Contributors are people who want to help the project improve, add
56
.. i18n: functionality and improve stability. Anyone can contribute to the project
57
.. i18n: by reporting bugs, proposing improvements and
58
.. i18n: posting patches.
61
Contributors are people who want to help the project improve, add
62
functionality and improve stability. Anyone can contribute to the project
63
by reporting bugs, proposing improvements and
66
.. i18n: The community team is available on launchpad: https://launchpad.net/~openerp-community
69
The community team is available on launchpad: https://launchpad.net/~openerp-community
71
.. i18n: Members of the quality and committer team are automatically members of the community.
74
Members of the quality and committer team are automatically members of the community.
76
.. i18n: Once you have configured your Launchpad account, get Bazaar version control to pull the source from Launchpad.
79
Once you have configured your Launchpad account, get Bazaar version control to pull the source from Launchpad.
81
.. i18n: NoteThib: viré les explications sur comment installer bazaar, je propos de mettre le lien vers le site qui expliquera comment l'installer si besoin est
84
NoteThib: viré les explications sur comment installer bazaar, je propos de mettre le lien vers le site qui expliquera comment l'installer si besoin est
86
.. i18n: If you experience problems with Bazaar, please read the :ref:`bazaar-faq-link` before asking any questions.
89
If you experience problems with Bazaar, please read the :ref:`bazaar-faq-link` before asking any questions.
91
.. i18n: Working with Branch
92
.. i18n: -------------------
98
.. i18n: The combination of Bazaar branch hosting and Launchpad's teams infrastructure gives you a very powerful capability to collaborate on code. Essentially, you can push a branch into a shared space and anyone on that team can then commit to the branch.
101
The combination of Bazaar branch hosting and Launchpad's teams infrastructure gives you a very powerful capability to collaborate on code. Essentially, you can push a branch into a shared space and anyone on that team can then commit to the branch.
103
.. i18n: This means that you can use Bazaar in the same way that you would use something like SVN, i.e. centrally hosting a branch that many people commit to. You have the added benefit, though, that anyone outside the team can always create their own personal branch of your team branch and, if they choose, upload it back to Launchpad.
106
This means that you can use Bazaar in the same way that you would use something like SVN, i.e. centrally hosting a branch that many people commit to. You have the added benefit, though, that anyone outside the team can always create their own personal branch of your team branch and, if they choose, upload it back to Launchpad.
108
.. i18n: This is the official and proposed way to contribute on OpenERP and OpenObject.
111
This is the official and proposed way to contribute on OpenERP and OpenObject.
113
.. i18n: Quick Summary
114
.. i18n: +++++++++++++
120
.. i18n: To download the latest sources and create your own local branches of OpenERP, do this::
122
.. i18n: mkdir openerp
124
.. i18n: bzr branch lp:~openerp/openobject-server/trunk server
125
.. i18n: bzr branch lp:~openerp/openobject-addons/trunk addons
126
.. i18n: bzr branch lp:~openerp-commiter/openobject-addons/trunk-extra-addons addons-extra
127
.. i18n: bzr branch lp:~openerp-community/openobject-addons/trunk-addons-community addons-community
128
.. i18n: bzr branch lp:~openerp/openerp-web/trunk web
129
.. i18n: bzr branch lp:~openerp/openobject-client/trunk client
130
.. i18n: bzr branch lp:~openerp-community/openobject-doc/6.1 doc
133
To download the latest sources and create your own local branches of OpenERP, do this::
137
bzr branch lp:~openerp/openobject-server/trunk server
138
bzr branch lp:~openerp/openobject-addons/trunk addons
139
bzr branch lp:~openerp-commiter/openobject-addons/trunk-extra-addons addons-extra
140
bzr branch lp:~openerp-community/openobject-addons/trunk-addons-community addons-community
141
bzr branch lp:~openerp/openerp-web/trunk web
142
bzr branch lp:~openerp/openobject-client/trunk client
143
bzr branch lp:~openerp-community/openobject-doc/6.1 doc
145
.. i18n: 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.::
147
.. i18n: EDIT addons/account/account.py
149
.. i18n: bzr ci -m "Testing Modifications"
152
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.::
154
EDIT addons/account/account.py
156
bzr ci -m "Testing Modifications"
158
.. i18n: Once your code is good enough and follow the :ref:`coding-guidelines-link`, you
159
.. i18n: can push your branch to launchpad. You may have to create an account on
160
.. i18n: launchpad first, register your public key, and subscribe to the `openerp-community <https://launchpad.net/~openerp-community>`_ team. Then, you
161
.. i18n: can push your branch. Suppose you want to push your addons::
164
.. i18n: bzr push lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME
165
.. i18n: bzr bind lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME
168
Once your code is good enough and follow the :ref:`coding-guidelines-link`, you
169
can push your branch to launchpad. You may have to create an account on
170
launchpad first, register your public key, and subscribe to the `openerp-community <https://launchpad.net/~openerp-community>`_ team. Then, you
171
can push your branch. Suppose you want to push your addons::
174
bzr push lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME
175
bzr bind lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME
177
.. i18n: After having done that, your branch is public on Launchpad, in the `OpenObject
178
.. i18n: project <https://code.launchpad.net/openobject>`_, and committers can work on
179
.. i18n: it, review it and propose for integration in the official branch. The last line
180
.. i18n: allows you to rebind your branch to the one on launchpad, after having
181
.. i18n: done this, your commit will be applied on launchpad directly (unless you use ``--local``)::
183
.. i18n: bzr pull # Get modifications on your branch from others
185
.. i18n: bzr ci # commit your changes on your public branch
188
After having done that, your branch is public on Launchpad, in the `OpenObject
189
project <https://code.launchpad.net/openobject>`_, and committers can work on
190
it, review it and propose for integration in the official branch. The last line
191
allows you to rebind your branch to the one on launchpad, after having
192
done this, your commit will be applied on launchpad directly (unless you use ``--local``)::
194
bzr pull # Get modifications on your branch from others
196
bzr ci # commit your changes on your public branch
198
.. i18n: If your changes fix a public bug on launchpad, you can use this to mark the bug as fixed by your branch::
200
.. i18n: bzr ci --fixes=lp:453123 # Where 453123 is a bug ID
203
If your changes fix a public bug on launchpad, you can use this to mark the bug as fixed by your branch::
205
bzr ci --fixes=lp:453123 # Where 453123 is a bug ID
207
.. i18n: Once your branch is mature, mark it as mature in the web interface of launchpad
208
.. i18n: and request for merging in the official release. Your branch will be reviewed
209
.. i18n: by a committer and then the quality team to be merged into the official release.
212
Once your branch is mature, mark it as mature in the web interface of launchpad
213
and request for merging in the official release. Your branch will be reviewed
214
by a committer and then the quality team to be merged into the official release.
216
.. i18n: [Read more about :ref:`OpenERP Team <openerp-team>`]
219
[Read more about :ref:`OpenERP Team <openerp-team>`]
221
.. i18n: Pushing a new branch
222
.. i18n: ++++++++++++++++++++
228
.. i18n: If you want to contribute on OpenERP or OpenObject, here is the proposed method:
231
If you want to contribute on OpenERP or OpenObject, here is the proposed method:
233
.. i18n: * You create a branch on launchpad on the project that interests you. It's
234
.. i18n: important that you create your branch on launchpad and not on your local
235
.. i18n: system so that we can easily merge, share code between projects and
236
.. i18n: centralize future developments.
237
.. i18n: * You develop your own features or bugfixes
238
.. i18n: in your own branch on launchpad. Don't forget to set the status of your
239
.. i18n: branch (new, experimental, development, mature, ...) so that contributors
240
.. i18n: know what they can and cannot use.
241
.. i18n: * Once your code is good enough, propose your branch for merging
242
.. i18n: * Your work will be evaluated by a member of the committers team.
244
.. i18n: - If they accept your branch for integration in the official version, they
245
.. i18n: will submit to the quality team that will review and merge in the official
247
.. i18n: - If the committer team refuses your branch, they will explain why
248
.. i18n: so that you can review the code to better fit the guidelines (problem for
249
.. i18n: future migrations, ...)
252
* You create a branch on launchpad on the project that interests you. It's
253
important that you create your branch on launchpad and not on your local
254
system so that we can easily merge, share code between projects and
255
centralize future developments.
256
* You develop your own features or bugfixes
257
in your own branch on launchpad. Don't forget to set the status of your
258
branch (new, experimental, development, mature, ...) so that contributors
259
know what they can and cannot use.
260
* Once your code is good enough, propose your branch for merging
261
* Your work will be evaluated by a member of the committers team.
263
- If they accept your branch for integration in the official version, they
264
will submit to the quality team that will review and merge in the official
266
- If the committer team refuses your branch, they will explain why
267
so that you can review the code to better fit the guidelines (problem for
268
future migrations, ...)
270
.. i18n: The extra-addons branch, that stores all extra modules, is directly accessible
271
.. i18n: to all committers. If you are a committer, you can work directly on this branch
272
.. i18n: and commit your own work. This branch does not require a validation of the
273
.. i18n: quality team. You should put there your special modules for your own customers.
276
The extra-addons branch, that stores all extra modules, is directly accessible
277
to all committers. If you are a committer, you can work directly on this branch
278
and commit your own work. This branch does not require a validation of the
279
quality team. You should put there your special modules for your own customers.
281
.. i18n: If you want to propose or develop new modules, we suggest creating your
282
.. i18n: own branch in the `openobject-addons project <https://launchpad.net/openobject-addons>`_
283
.. i18n: and develop within your branch. You can fill in a bug to request that
284
.. i18n: your modules are integrated in one of the two branches:
287
If you want to propose or develop new modules, we suggest creating your
288
own branch in the `openobject-addons project <https://launchpad.net/openobject-addons>`_
289
and develop within your branch. You can fill in a bug to request that
290
your modules are integrated in one of the two branches:
292
.. i18n: * extra-addons : if your module touches a few companies
293
.. i18n: * addons : if your module will be useful for most of the companies
296
* extra-addons : if your module touches a few companies
297
* addons : if your module will be useful for most of the companies
299
.. i18n: We invite all our partners and contributors to work in that way so that we can
300
.. i18n: easily integrate and share the work done between the different projects.
303
We invite all our partners and contributors to work in that way so that we can
304
easily integrate and share the work done between the different projects.
306
.. i18n: After having done that, your branch is public on Launchpad, in the `OpenObject
307
.. i18n: project <https://code.launchpad.net/openobject>`_, and committers can work on
308
.. i18n: it, review it and propose for integration in the official branch. The last line
309
.. i18n: allows you to rebind your branch to the one which is on launchpad, after having
310
.. i18n: done this, your commit will be applied on launchpad directly (unless you use ``--local``)::
312
.. i18n: bzr pull # Get modifications on your branch from others
314
.. i18n: bzr ci # commit your changes on your public branch
317
After having done that, your branch is public on Launchpad, in the `OpenObject
318
project <https://code.launchpad.net/openobject>`_, and committers can work on
319
it, review it and propose for integration in the official branch. The last line
320
allows you to rebind your branch to the one which is on launchpad, after having
321
done this, your commit will be applied on launchpad directly (unless you use ``--local``)::
323
bzr pull # Get modifications on your branch from others
325
bzr ci # commit your changes on your public branch
327
.. i18n: If your changes fix a public bug on launchpad, you can use this to mark the bug as fixed by your branch::
329
.. i18n: bzr ci --fixes=lp:453123 # Where 453123 is a bug ID
332
If your changes fix a public bug on launchpad, you can use this to mark the bug as fixed by your branch::
334
bzr ci --fixes=lp:453123 # Where 453123 is a bug ID
336
.. i18n: Once your branch is mature, mark it as mature in the web interface of launchpad
337
.. i18n: and request for merging in the official release. Your branch will be reviewed
338
.. i18n: by a committer and then the quality team to be merged in the official release.
341
Once your branch is mature, mark it as mature in the web interface of launchpad
342
and request for merging in the official release. Your branch will be reviewed
343
by a committer and then the quality team to be merged in the official release.
345
.. i18n: How to commit Your Work
346
.. i18n: +++++++++++++++++++++++
349
How to commit Your Work
350
+++++++++++++++++++++++
352
.. i18n: If you want to contribute on OpenERP or OpenObject, here is the proposed method:
355
If you want to contribute on OpenERP or OpenObject, here is the proposed method:
357
.. i18n: * You create a branch on launchpad on the project that interests you. It's
358
.. i18n: important that you create your branch on launchpad and not on your local
359
.. i18n: system so that we can easily merge, share code between projects and
360
.. i18n: centralize future developments.
361
.. i18n: * You develop your own features or bugfixes
362
.. i18n: in your own branch on launchpad. Don't forget to set the status of your
363
.. i18n: branch (new, experimental, development, mature, ...) so that contributors
364
.. i18n: know what they can and cannot use.
365
.. i18n: * Once your code is good enough, propose your branch for merging
366
.. i18n: * Your work will be evaluated by a member of the committers team.
368
.. i18n: - If they accept your branch for integration in the official version, they
369
.. i18n: will submit to the quality team that will review and merge in the official
371
.. i18n: - If the committer team refuses your branch, they will explain why
372
.. i18n: so that you can review the code to better fit the guidelines (problem for
373
.. i18n: future migrations, ...)
376
* You create a branch on launchpad on the project that interests you. It's
377
important that you create your branch on launchpad and not on your local
378
system so that we can easily merge, share code between projects and
379
centralize future developments.
380
* You develop your own features or bugfixes
381
in your own branch on launchpad. Don't forget to set the status of your
382
branch (new, experimental, development, mature, ...) so that contributors
383
know what they can and cannot use.
384
* Once your code is good enough, propose your branch for merging
385
* Your work will be evaluated by a member of the committers team.
387
- If they accept your branch for integration in the official version, they
388
will submit to the quality team that will review and merge in the official
390
- If the committer team refuses your branch, they will explain why
391
so that you can review the code to better fit the guidelines (problem for
392
future migrations, ...)
394
.. i18n: The `extra-addons branch <https://code.launchpad.net/~openerp-commiter/openobject-addons/trunk-extra-addons>`_,
395
.. i18n: that stores all extra modules, is directly accessible to all committers. If you
396
.. i18n: are a committer, you can work directly on this branch and commit your own work.
397
.. i18n: This branch does not require validation by the quality team. You should put
398
.. i18n: there your special modules for your own customers.
401
The `extra-addons branch <https://code.launchpad.net/~openerp-commiter/openobject-addons/trunk-extra-addons>`_,
402
that stores all extra modules, is directly accessible to all committers. If you
403
are a committer, you can work directly on this branch and commit your own work.
404
This branch does not require validation by the quality team. You should put
405
there your special modules for your own customers.
407
.. i18n: If you want to propose or develop new modules, we suggest creating your
408
.. i18n: own branch in the `openobject-addons project <https://launchpad.net/openobject-addons>`_
409
.. i18n: and develop within your branch. You can fill in a bug to request that
410
.. i18n: your modules are integrated in one of the two branches:
413
If you want to propose or develop new modules, we suggest creating your
414
own branch in the `openobject-addons project <https://launchpad.net/openobject-addons>`_
415
and develop within your branch. You can fill in a bug to request that
416
your modules are integrated in one of the two branches:
418
.. i18n: * `extra-addons branch <https://code.launchpad.net/~openerp-commiter/openobject-addons/trunk-extra-addons>`_ : if your module touches a few companies
419
.. i18n: * `addons <https://code.launchpad.net/~openerp/openobject-addons/trunk>`_ : if your module will be useful for most of the companies
422
* `extra-addons branch <https://code.launchpad.net/~openerp-commiter/openobject-addons/trunk-extra-addons>`_ : if your module touches a few companies
423
* `addons <https://code.launchpad.net/~openerp/openobject-addons/trunk>`_ : if your module will be useful for most of the companies
425
.. i18n: We invite all our partners and contributors to work in that way so that we can
426
.. i18n: easily integrate and share the work done between the different projects.
429
We invite all our partners and contributors to work in that way so that we can
430
easily integrate and share the work done between the different projects.
432
.. i18n: Registration and Configuration
433
.. i18n: ------------------------------
436
Registration and Configuration
437
------------------------------
439
.. i18n: Before you can commit on launchpad, you need to create a login.
442
Before you can commit on launchpad, you need to create a login.
444
.. i18n: Go to: https://launchpad.net --> log in / register on top right.
447
Go to: https://launchpad.net --> log in / register on top right.
449
.. i18n: You enter your e-mail address and you wait for an e-mail which will guide you trough the process needed to create your login.
452
You enter your e-mail address and you wait for an e-mail which will guide you trough the process needed to create your login.
454
.. i18n: This login is only needed if you intend to commit on bazaar on openerp-commiter or on your own branch.
457
This login is only needed if you intend to commit on bazaar on openerp-commiter or on your own branch.
459
.. i18n: You can refer to this link :
460
.. i18n: https://help.launchpad.net/YourAccount/NewAccount
463
You can refer to this link :
464
https://help.launchpad.net/YourAccount/NewAccount
466
.. i18n: Any contributor who is interested to become a committer must show his interest
467
.. i18n: on working for openerp project and ability to do it properly as
468
.. i18n: selection is based on merit. It can be by proposing bug
469
.. i18n: fixes, features requested on our :ref:`bug tracker <bug-tracker-link>` system.
470
.. i18n: You can even suggest additional modules and/or functionality on our :ref:`bug
471
.. i18n: tracker <bug-tracker-link>` system.
474
Any contributor who is interested to become a committer must show his interest
475
on working for openerp project and ability to do it properly as
476
selection is based on merit. It can be by proposing bug
477
fixes, features requested on our :ref:`bug tracker <bug-tracker-link>` system.
478
You can even suggest additional modules and/or functionality on our :ref:`bug
479
tracker <bug-tracker-link>` system.
481
.. i18n: You can contribute or join OpenERP team, : https://help.launchpad.net/Teams/Joining
484
You can contribute or join OpenERP team, : https://help.launchpad.net/Teams/Joining
486
.. i18n: Contributors are people who want to help the project improve, add
487
.. i18n: functionality and improve stability. Anyone can contribute on the project
488
.. i18n: by reporting bugs, proposing some improvement and
489
.. i18n: posting patch.
492
Contributors are people who want to help the project improve, add
493
functionality and improve stability. Anyone can contribute on the project
494
by reporting bugs, proposing some improvement and
497
.. i18n: The community team is available on launchpad: https://launchpad.net/~openerp-community
500
The community team is available on launchpad: https://launchpad.net/~openerp-community
502
.. i18n: Member of the quality and committer team are automatically members of the community.
505
Member of the quality and committer team are automatically members of the community.
507
.. i18n: Installing Bazaar
508
.. i18n: +++++++++++++++++
515
.. i18n: single: Bazaar; installation
516
.. i18n: single: Installation; Bazaar
521
single: Bazaar; installation
522
single: Installation; Bazaar
525
.. i18n: Get Bazaar version control to pull the source from Launchpad.
528
Get Bazaar version control to pull the source from Launchpad.
530
.. i18n: To install bazaar on any ubuntu distribution, you can edit /etc/apt/sources.list by
533
To install bazaar on any ubuntu distribution, you can edit /etc/apt/sources.list by
537
.. i18n: sudo gedit /etc/apt/sources.list
542
sudo gedit /etc/apt/sources.list
544
.. i18n: and put these lines in it:
547
and put these lines in it:
551
.. i18n: (for ubuntu intrepid 8.10)
552
.. i18n: deb http://ppa.launchpad.net/bzr/ubuntu intrepid main
553
.. i18n: deb-src http://ppa.launchpad.net/bzr/ubuntu intrepid main
555
.. i18n: or (for ubuntu jaunty 9.04)
556
.. i18n: deb http://ppa.launchpad.net/bzr/ubuntu jaunty main
557
.. i18n: deb-src http://ppa.launchpad.net/bzr/ubuntu jaunty main
559
.. i18n: or (for ubuntu karmic 9.10)
560
.. i18n: deb http://ppa.launchpad.net/bzr/ubuntu karmic main
561
.. i18n: deb-src http://ppa.launchpad.net/bzr/ubuntu karmic main
563
.. i18n: Here, intrepid, jaunty and karmic are version names of ubuntu, replace it with your ubuntu version.
568
(for ubuntu intrepid 8.10)
569
deb http://ppa.launchpad.net/bzr/ubuntu intrepid main
570
deb-src http://ppa.launchpad.net/bzr/ubuntu intrepid main
572
or (for ubuntu jaunty 9.04)
573
deb http://ppa.launchpad.net/bzr/ubuntu jaunty main
574
deb-src http://ppa.launchpad.net/bzr/ubuntu jaunty main
576
or (for ubuntu karmic 9.10)
577
deb http://ppa.launchpad.net/bzr/ubuntu karmic main
578
deb-src http://ppa.launchpad.net/bzr/ubuntu karmic main
580
Here, intrepid, jaunty and karmic are version names of ubuntu, replace it with your ubuntu version.
582
.. i18n: Then, do the following
585
Then, do the following
589
.. i18n: sudo apt-get install bzr
594
sudo apt-get install bzr
596
.. i18n: To work correctly, bzr version must be at least 1.3. Check it with the command:
599
To work correctly, bzr version must be at least 1.3. Check it with the command:
603
.. i18n: bzr --version
610
.. i18n: If you have an older version check this url: http://bazaar-vcs.org/Download
611
.. i18n: On debian, in any distribution, the 1.5 version is working, you can get it on this url: http://backports.org/debian/pool/main/b/bzr/bzr_1.5-1~bpo40+1_i386.deb
614
If you have an older version check this url: http://bazaar-vcs.org/Download
615
On debian, in any distribution, the 1.5 version is working, you can get it on this url: http://backports.org/debian/pool/main/b/bzr/bzr_1.5-1~bpo40+1_i386.deb
617
.. i18n: If you experience problems with Bazaar, please read the :ref:`bazaar-faq-link` before asking any questions.
620
If you experience problems with Bazaar, please read the :ref:`bazaar-faq-link` before asking any questions.
629
.. i18n: The combination of Bazaar branch hosting and Launchpad's teams infrastructure gives you a very powerful capability to collaborate on code. Essentially, you can push a branch into a shared space and anyone on that team can then commit to the branch.
632
The combination of Bazaar branch hosting and Launchpad's teams infrastructure gives you a very powerful capability to collaborate on code. Essentially, you can push a branch into a shared space and anyone on that team can then commit to the branch.
634
.. i18n: This means that you can use Bazaar in the same way that you would use something like SVN, i.e. centrally hosting a branch that many people commit to. You have the added benefit, though, that anyone outside the team can always create their own personal branch of your team branch and, if they choose, upload it back to Launchpad.
637
This means that you can use Bazaar in the same way that you would use something like SVN, i.e. centrally hosting a branch that many people commit to. You have the added benefit, though, that anyone outside the team can always create their own personal branch of your team branch and, if they choose, upload it back to Launchpad.
639
.. i18n: This is the official and proposed way to contribute on OpenERP and OpenObject.
642
This is the official and proposed way to contribute on OpenERP and OpenObject.
644
.. i18n: How to commit
645
.. i18n: -------------
651
.. i18n: If you want to contribute on OpenERP or OpenObject, here is the proposed method:
654
If you want to contribute on OpenERP or OpenObject, here is the proposed method:
656
.. i18n: * You create a branch on launchpad on the project that interests you. It's
657
.. i18n: important that you create your branch on launchpad and not on your local
658
.. i18n: system so that we can easily merge, share code between projects and
659
.. i18n: centralize future developments.
660
.. i18n: * You develop your own features or bugfixes
661
.. i18n: in your own branch on launchpad. Don't forget to set the status of your
662
.. i18n: branch (new, experimental, development, mature, ...) so that contributors
663
.. i18n: know what they can and cannot use.
664
.. i18n: * Once your code is good enough, propose your branch for merging
665
.. i18n: * Your work will be evaluated by a member of the committers team.
667
.. i18n: - If they accept your branch for integration in the official version, they
668
.. i18n: will submit to the quality team that will review and merge in the official
670
.. i18n: - If the committer team refuses your branch, they will explain why
671
.. i18n: so that you can review the code to better fit the guidelines (problem for
672
.. i18n: future migrations, ...)
675
* You create a branch on launchpad on the project that interests you. It's
676
important that you create your branch on launchpad and not on your local
677
system so that we can easily merge, share code between projects and
678
centralize future developments.
679
* You develop your own features or bugfixes
680
in your own branch on launchpad. Don't forget to set the status of your
681
branch (new, experimental, development, mature, ...) so that contributors
682
know what they can and cannot use.
683
* Once your code is good enough, propose your branch for merging
684
* Your work will be evaluated by a member of the committers team.
686
- If they accept your branch for integration in the official version, they
687
will submit to the quality team that will review and merge in the official
689
- If the committer team refuses your branch, they will explain why
690
so that you can review the code to better fit the guidelines (problem for
691
future migrations, ...)
693
.. i18n: The extra-addons branch, that stores all extra modules, is directly accessible
694
.. i18n: to all committers. If you are a committer, you can work directly on this branch
695
.. i18n: and commit your own work. This branch does not require a validation of the
696
.. i18n: quality team. You should put there your special modules for your own customers.
699
The extra-addons branch, that stores all extra modules, is directly accessible
700
to all committers. If you are a committer, you can work directly on this branch
701
and commit your own work. This branch does not require a validation of the
702
quality team. You should put there your special modules for your own customers.
704
.. i18n: If you want to propose or develop new modules, we suggest creating your
705
.. i18n: own branch in the `openobject-addons project <https://launchpad.net/openobject-addons>`_
706
.. i18n: and develop within your branch. You can fill in a bug to request that
707
.. i18n: your modules are integrated in one of the two branches:
710
If you want to propose or develop new modules, we suggest creating your
711
own branch in the `openobject-addons project <https://launchpad.net/openobject-addons>`_
712
and develop within your branch. You can fill in a bug to request that
713
your modules are integrated in one of the two branches:
715
.. i18n: * extra-addons : if your module touches a few companies
716
.. i18n: * addons : if your module will be useful for most of the companies
719
* extra-addons : if your module touches a few companies
720
* addons : if your module will be useful for most of the companies
722
.. i18n: We invite all our partners and contributors to work in that way so that we can
723
.. i18n: easily integrate and share the work done between the different projects.
726
We invite all our partners and contributors to work in that way so that we can
727
easily integrate and share the work done between the different projects.
729
.. i18n: After having done that, your branch is public on Launchpad, in the `OpenObject
730
.. i18n: project <https://code.launchpad.net/openobject>`_, and committers can work on
731
.. i18n: it, review it and propose for integration in the official branch. The last line
732
.. i18n: allows you to rebind your branch to the one which is on launchpad, after having
733
.. i18n: done this, your commit will be applied on launchpad directly (unless you use ``--local``)::
735
.. i18n: bzr pull # Get modifications on your branch from others
737
.. i18n: bzr ci # commit your changes on your public branch
740
After having done that, your branch is public on Launchpad, in the `OpenObject
741
project <https://code.launchpad.net/openobject>`_, and committers can work on
742
it, review it and propose for integration in the official branch. The last line
743
allows you to rebind your branch to the one which is on launchpad, after having
744
done this, your commit will be applied on launchpad directly (unless you use ``--local``)::
746
bzr pull # Get modifications on your branch from others
748
bzr ci # commit your changes on your public branch
750
.. i18n: If your changes fix a public bug on launchpad, you can use this to mark the bug as fixed by your branch::
752
.. i18n: bzr ci --fixes=lp:453123 # Where 453123 is a bug ID
755
If your changes fix a public bug on launchpad, you can use this to mark the bug as fixed by your branch::
757
bzr ci --fixes=lp:453123 # Where 453123 is a bug ID
759
.. i18n: Once your branch is mature, mark it as mature in the web interface of launchpad
760
.. i18n: and request for merging in the official release. Your branch will be reviewed
761
.. i18n: by a committer and then the quality team to be merged in the official release.
764
Once your branch is mature, mark it as mature in the web interface of launchpad
765
and request for merging in the official release. Your branch will be reviewed
766
by a committer and then the quality team to be merged in the official release.
768
.. i18n: Answer and bug tracking and management
769
.. i18n: --------------------------------------
772
Answer and bug tracking and management
773
--------------------------------------
775
.. i18n: We use launchpad on the openobject project to track all bugs and features
776
.. i18n: request related to openerp and openobject. the bug tracker is available here:
779
We use launchpad on the openobject project to track all bugs and features
780
request related to openerp and openobject. the bug tracker is available here:
782
.. i18n: * Bug Tracker : https://bugs.launchpad.net/openobject
783
.. i18n: * Ideas Tracker : https://blueprints.launchpad.net/openobject
784
.. i18n: * FAQ Manager : https://answers.launchpad.net/openobject
787
* Bug Tracker : https://bugs.launchpad.net/openobject
788
* Ideas Tracker : https://blueprints.launchpad.net/openobject
789
* FAQ Manager : https://answers.launchpad.net/openobject
791
.. i18n: Every contributor can report bug and propose bugfixes for the bugs.
792
.. i18n: The status of the bug is set according to the correction.
795
Every contributor can report bug and propose bugfixes for the bugs.
796
The status of the bug is set according to the correction.
798
.. i18n: When a particular branch fixes the bug, a committer (member of the `Commiter
799
.. i18n: Team <https://launchpad.net/~openerp-commiter>`_) can set the status to "Fix
800
.. i18n: Committed". Only committers have the right to change the status to "Fix
801
.. i18n: Committed.", after they validated the proposed patch or branch that fixes the
805
When a particular branch fixes the bug, a committer (member of the `Commiter
806
Team <https://launchpad.net/~openerp-commiter>`_) can set the status to "Fix
807
Committed". Only committers have the right to change the status to "Fix
808
Committed.", after they validated the proposed patch or branch that fixes the
811
.. i18n: The `Quality Team <https://launchpad.net/~openerp>`_ have a look every day to
812
.. i18n: bugs in the status "Fix Committed". They check the quality of the code and merge
813
.. i18n: in the official branch if it's OK. To limit the work of the quality team, it's
814
.. i18n: important that only committers can set the bug in the status "Fix Committed".
815
.. i18n: Once quality team finish merging, they change the status to "Fix Released".
818
The `Quality Team <https://launchpad.net/~openerp>`_ have a look every day to
819
bugs in the status "Fix Committed". They check the quality of the code and merge
820
in the official branch if it's OK. To limit the work of the quality team, it's
821
important that only committers can set the bug in the status "Fix Committed".
822
Once quality team finish merging, they change the status to "Fix Released".
831
.. i18n: Translations are managed by
832
.. i18n: the `Launchpad Web interface <https://translations.launchpad.net/openobject>`_. Here, you'll
833
.. i18n: find the list of translatable projects.
836
Translations are managed by
837
the `Launchpad Web interface <https://translations.launchpad.net/openobject>`_. Here, you'll
838
find the list of translatable projects.
840
.. i18n: Please read the `FAQ <https://answers.launchpad.net/rosetta/+faqs>`_ before asking questions.
843
Please read the `FAQ <https://answers.launchpad.net/rosetta/+faqs>`_ before asking questions.
852
.. i18n: Blueprint is a lightweight way to manage releases of your software and to track the progress of features and ideas, from initial concept to implementation. Using Blueprint, you can encourage contributions from right across your project's community, while targeting the best ideas to future releases.
855
Blueprint is a lightweight way to manage releases of your software and to track the progress of features and ideas, from initial concept to implementation. Using Blueprint, you can encourage contributions from right across your project's community, while targeting the best ideas to future releases.
857
.. i18n: Launchpad Blueprint helps you to plan future release with two tools:
860
Launchpad Blueprint helps you to plan future release with two tools:
862
.. i18n: * milestones: points in time, such as a future release or development sprint
863
.. i18n: * series goals: a statement of intention to work on the blueprint for a particular series.
866
* milestones: points in time, such as a future release or development sprint
867
* series goals: a statement of intention to work on the blueprint for a particular series.
869
.. i18n: Although only drivers can target blueprints to milestones and set them as series goals, anyone can propose a blueprint as a series goal. As a driver or owner, you can review proposed goals by following the Set goals link on your project's Blueprint overview page.
872
Although only drivers can target blueprints to milestones and set them as series goals, anyone can propose a blueprint as a series goal. As a driver or owner, you can review proposed goals by following the Set goals link on your project's Blueprint overview page.
874
.. i18n: By following the Subscribe yourself link on a blueprint page, you can ask Launchpad to send you email notification of any changes to the blueprint. In most cases, you'll receive notification only of changes made to the blueprint itself in Launchpad and not to any further information, such as in an external wiki.
877
By following the Subscribe yourself link on a blueprint page, you can ask Launchpad to send you email notification of any changes to the blueprint. In most cases, you'll receive notification only of changes made to the blueprint itself in Launchpad and not to any further information, such as in an external wiki.
879
.. i18n: However, if the wiki software supports email change notifications, Launchpad can even notify you of changes to the wiki page.
882
However, if the wiki software supports email change notifications, Launchpad can even notify you of changes to the wiki page.
884
.. i18n: If you're a blueprint owner and want Launchpad to know about updates to the related wiki page, ask the wiki admin how to send email notifications. Notifications should go to notifications@specs.launchpad.net.
887
If you're a blueprint owner and want Launchpad to know about updates to the related wiki page, ask the wiki admin how to send email notifications. Notifications should go to notifications@specs.launchpad.net.
889
.. i18n: The Blueprints for OpenERP are listed here:
891
.. i18n: * https://blueprints.launchpad.net/openerp
892
.. i18n: * https://blueprints.launchpad.net/~openerp-commiter
895
The Blueprints for OpenERP are listed here:
897
* https://blueprints.launchpad.net/openerp
898
* https://blueprints.launchpad.net/~openerp-commiter
added
removed
i18n/zh_CN/source/developer/99_community_book.rst
