2
.. i18n: Working with Launchpad
3
.. i18n: ======================
9
.. i18n: Registration and Configuration
10
.. i18n: ------------------------------
13
Registration and Configuration
14
------------------------------
16
.. i18n: Before you can commit on launchpad, you need to create a login.
19
Before you can commit on launchpad, you need to create a login.
21
.. i18n: Go to: https://launchpad.net --> log in / register on top right.
24
Go to: https://launchpad.net --> log in / register on top right.
26
.. 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.
29
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.
31
.. i18n: This login is only needed if you intend to commit on bazaar on openerp-commiter or on your own branch.
34
This login is only needed if you intend to commit on bazaar on openerp-commiter or on your own branch.
36
.. i18n: You can refer to this link :
37
.. i18n: https://help.launchpad.net/YourAccount/NewAccount
40
You can refer to this link :
41
https://help.launchpad.net/YourAccount/NewAccount
43
.. i18n: Any contributor who is interested to become a commiter must show his interest
44
.. i18n: on working for openerp project and his ability to do it in a proper way as the
45
.. i18n: selection for this group is based on meritocracy. It can be by proposing bug
46
.. i18n: fixes, features requested on our :ref:`bug tracker <bug-tracker-link>` system.
47
.. i18n: You can even suggest additional modules and/or functionalities on our :ref:`bug
48
.. i18n: tracker <bug-tracker-link>` system.
51
Any contributor who is interested to become a commiter must show his interest
52
on working for openerp project and his ability to do it in a proper way as the
53
selection for this group is based on meritocracy. It can be by proposing bug
54
fixes, features requested on our :ref:`bug tracker <bug-tracker-link>` system.
55
You can even suggest additional modules and/or functionalities on our :ref:`bug
56
tracker <bug-tracker-link>` system.
58
.. i18n: You can contribute or join OpenERP team, : https://help.launchpad.net/Teams/Joining
61
You can contribute or join OpenERP team, : https://help.launchpad.net/Teams/Joining
63
.. i18n: Contributors are people who wants to help the project getting better, add
64
.. i18n: functionnality and improve stability. Everyone can contribute on the project
65
.. i18n: with his own knowledge by reporting bugs, purposing smart improvment and
66
.. i18n: posting patch.
69
Contributors are people who wants to help the project getting better, add
70
functionnality and improve stability. Everyone can contribute on the project
71
with his own knowledge by reporting bugs, purposing smart improvment and
74
.. i18n: The community team is available on launchpad: https://launchpad.net/~openerp-community
77
The community team is available on launchpad: https://launchpad.net/~openerp-community
79
.. i18n: Member of the quality and commiter team are automatically members of the community.
82
Member of the quality and commiter team are automatically members of the community.
84
.. i18n: Installing Bazaar
85
.. i18n: +++++++++++++++++
92
.. i18n: single: Bazaar; installation
93
.. i18n: single: Installation; Bazaar
98
single: Bazaar; installation
99
single: Installation; Bazaar
102
.. i18n: Get Bazaar version control to pull the source from Launchpad.
105
Get Bazaar version control to pull the source from Launchpad.
107
.. i18n: To install bazaar on any ubuntu distribution, you can edit /etc/apt/sources.list by
110
To install bazaar on any ubuntu distribution, you can edit /etc/apt/sources.list by
114
.. i18n: sudo gedit /etc/apt/sources.list
119
sudo gedit /etc/apt/sources.list
121
.. i18n: and put these lines in it:
124
and put these lines in it:
128
.. i18n: (for ubuntu intrepid 8.10)
129
.. i18n: deb http://ppa.launchpad.net/bzr/ubuntu intrepid main
130
.. i18n: deb-src http://ppa.launchpad.net/bzr/ubuntu intrepid main
132
.. i18n: or (for ubuntu jaunty 9.04)
133
.. i18n: deb http://ppa.launchpad.net/bzr/ubuntu jaunty main
134
.. i18n: deb-src http://ppa.launchpad.net/bzr/ubuntu jaunty main
136
.. i18n: or (for ubuntu karmic 9.10)
137
.. i18n: deb http://ppa.launchpad.net/bzr/ubuntu karmic main
138
.. i18n: deb-src http://ppa.launchpad.net/bzr/ubuntu karmic main
140
.. i18n: Here, interpid, jaunty and karmic are version names of ubuntu. So, replace it with accourding to your ubuntu version.
145
(for ubuntu intrepid 8.10)
146
deb http://ppa.launchpad.net/bzr/ubuntu intrepid main
147
deb-src http://ppa.launchpad.net/bzr/ubuntu intrepid main
149
or (for ubuntu jaunty 9.04)
150
deb http://ppa.launchpad.net/bzr/ubuntu jaunty main
151
deb-src http://ppa.launchpad.net/bzr/ubuntu jaunty main
153
or (for ubuntu karmic 9.10)
154
deb http://ppa.launchpad.net/bzr/ubuntu karmic main
155
deb-src http://ppa.launchpad.net/bzr/ubuntu karmic main
157
Here, interpid, jaunty and karmic are version names of ubuntu. So, replace it with accourding to your ubuntu version.
159
.. i18n: Then, do the following
162
Then, do the following
166
.. i18n: sudo apt-get install bzr
171
sudo apt-get install bzr
173
.. i18n: To work correctly, bzr version must be at least 1.3. Check it with the command:
176
To work correctly, bzr version must be at least 1.3. Check it with the command:
180
.. i18n: bzr --version
187
.. i18n: If you don't have at least 1.3 version, you can check this url: http://bazaar-vcs.org/Download
188
.. 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
191
If you don't have at least 1.3 version, you can check this url: http://bazaar-vcs.org/Download
192
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
194
.. i18n: If you experience problems with Bazaar, please read the :ref:`bazaar-faq-link` before asking any questions.
197
If you experience problems with Bazaar, please read the :ref:`bazaar-faq-link` before asking any questions.
199
.. i18n: Working with Branch
200
.. i18n: -------------------
206
.. 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.
209
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.
211
.. 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.
214
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.
216
.. i18n: This is the official and proposed way to contribute on OpenERP and OpenObject.
219
This is the official and proposed way to contribute on OpenERP and OpenObject.
221
.. i18n: Quick Summary
222
.. i18n: +++++++++++++
228
.. i18n: To download the latest sources and create your own local branches of OpenERP, do this::
230
.. i18n: bzr branch lp:openerp
232
.. i18n: ./bzr_set.py
235
To download the latest sources and create your own local branches of OpenERP, do this::
237
bzr branch lp:openerp
241
.. i18n: 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.::
243
.. i18n: EDIT addons/account/account.py
245
.. i18n: bzr ci -m "Testing Modifications"
248
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.::
250
EDIT addons/account/account.py
252
bzr ci -m "Testing Modifications"
254
.. i18n: Once your code is good enough and follow the :ref:`coding-guidelines-link`, you
255
.. i18n: can push your branch in launchpad. You may have to create an account on
256
.. i18n: launchpad first, register your public key, and subscribe to the `openerp-community <https://launchpad.net/~openerp-community>`_ team. Then, you
257
.. i18n: can push your branch. Suppose you want to push your addons::
260
.. i18n: bzr push lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME
261
.. i18n: bzr bind lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME
264
Once your code is good enough and follow the :ref:`coding-guidelines-link`, you
265
can push your branch in launchpad. You may have to create an account on
266
launchpad first, register your public key, and subscribe to the `openerp-community <https://launchpad.net/~openerp-community>`_ team. Then, you
267
can push your branch. Suppose you want to push your addons::
270
bzr push lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME
271
bzr bind lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME
273
.. i18n: After having done that, your branch is public on Launchpad, in the `OpenObject
274
.. i18n: project <https://code.launchpad.net/openobject>`_, and commiters can work on
275
.. i18n: it, review it and propose for integration in the official branch. The last line
276
.. i18n: allows you to rebind your branch to the one which is on launchpad, after having
277
.. i18n: done this, your commit will be applied on launchpad directly (unless you use ``--local``)::
279
.. i18n: bzr pull # Get modifications on your branch from others
281
.. i18n: bzr ci # commit your changes on your public branch
284
After having done that, your branch is public on Launchpad, in the `OpenObject
285
project <https://code.launchpad.net/openobject>`_, and commiters can work on
286
it, review it and propose for integration in the official branch. The last line
287
allows you to rebind your branch to the one which is on launchpad, after having
288
done this, your commit will be applied on launchpad directly (unless you use ``--local``)::
290
bzr pull # Get modifications on your branch from others
292
bzr ci # commit your changes on your public branch
294
.. i18n: If your changes fixe a public bug on launchpad, you can use this to mark the bug as fixed by your branch::
296
.. i18n: bzr ci --fixes=lp:453123 # Where 453123 is a bug ID
299
If your changes fixe a public bug on launchpad, you can use this to mark the bug as fixed by your branch::
301
bzr ci --fixes=lp:453123 # Where 453123 is a bug ID
303
.. i18n: Once your branch is mature, mark it as mature in the web interface of launchpad
304
.. i18n: and request for merging in the official release. Your branch will be reviewed
305
.. i18n: by a commiter and then the quality team to be merged in the official release.
308
Once your branch is mature, mark it as mature in the web interface of launchpad
309
and request for merging in the official release. Your branch will be reviewed
310
by a commiter and then the quality team to be merged in the official release.
312
.. i18n: [Read more about :ref:`OpenERP Team <openerp-team>`]
315
[Read more about :ref:`OpenERP Team <openerp-team>`]
317
.. i18n: Pushing a new branch
318
.. i18n: ++++++++++++++++++++
324
.. i18n: If you want to contribute on OpenERP or OpenObject, here is the proposed method:
327
If you want to contribute on OpenERP or OpenObject, here is the proposed method:
329
.. i18n: * You create a branch on launchpad on the project that interest you. It's
330
.. i18n: important that you create your branch on launchpad and not on your local
331
.. i18n: system so that we can easily merge, share code between projects and
332
.. i18n: centralize futur developments.
333
.. i18n: * You develop your own features or bugfixes
334
.. i18n: in your own branch on launchpad. Don't forget to set the status of your
335
.. i18n: branch (new, experimental, development, mature, ...) so that contributors
336
.. i18n: knows what they can use or not.
337
.. i18n: * Once your code is good enough, you propose your branch for merging
338
.. i18n: * Your work will be evaluated by one responsible of the commiters team.
340
.. i18n: - If they accept your branch for integration in the official version, they
341
.. i18n: will submit to the quality team that will review and merge in the official
343
.. i18n: - If the commiter team refuses your branch, they will explain why
344
.. i18n: so that you can review your code to better fits guidelines (problem for
345
.. i18n: futur migrations, ...)
348
* You create a branch on launchpad on the project that interest you. It's
349
important that you create your branch on launchpad and not on your local
350
system so that we can easily merge, share code between projects and
351
centralize futur developments.
352
* You develop your own features or bugfixes
353
in your own branch on launchpad. Don't forget to set the status of your
354
branch (new, experimental, development, mature, ...) so that contributors
355
knows what they can use or not.
356
* Once your code is good enough, you propose your branch for merging
357
* Your work will be evaluated by one responsible of the commiters team.
359
- If they accept your branch for integration in the official version, they
360
will submit to the quality team that will review and merge in the official
362
- If the commiter team refuses your branch, they will explain why
363
so that you can review your code to better fits guidelines (problem for
364
futur migrations, ...)
366
.. i18n: The extra-addons branch, that stores all extra modules, is directly accessible
367
.. i18n: to all commiters. If you are a commiter, you can work directly on this branch
368
.. i18n: and commit your own work. This branch do not require a validation of the
369
.. i18n: quality team. You should put there your special modules for your own customers.
372
The extra-addons branch, that stores all extra modules, is directly accessible
373
to all commiters. If you are a commiter, you can work directly on this branch
374
and commit your own work. This branch do not require a validation of the
375
quality team. You should put there your special modules for your own customers.
377
.. i18n: If you want to propose or develop new modules, we suggest you to create your
378
.. i18n: own branch in the `openobject-addons project <https://launchpad.net/openobject-addons>`_
379
.. i18n: and develop within your branch. You can fill in a bug to request that
380
.. i18n: your modules are integrated in one of the two branches:
383
If you want to propose or develop new modules, we suggest you to create your
384
own branch in the `openobject-addons project <https://launchpad.net/openobject-addons>`_
385
and develop within your branch. You can fill in a bug to request that
386
your modules are integrated in one of the two branches:
388
.. i18n: * extra-addons : if your module touches a few companies
389
.. i18n: * addons : if your module will be usefull for most of the companies
392
* extra-addons : if your module touches a few companies
393
* addons : if your module will be usefull for most of the companies
395
.. i18n: We invite all our partners and contributors to work in that way so that we can
396
.. i18n: easily integrate and share the work done between the different projects.
399
We invite all our partners and contributors to work in that way so that we can
400
easily integrate and share the work done between the different projects.
402
.. i18n: After having done that, your branch is public on Launchpad, in the `OpenObject
403
.. i18n: project <https://code.launchpad.net/openobject>`_, and commiters can work on
404
.. i18n: it, review it and propose for integration in the official branch. The last line
405
.. i18n: allows you to rebind your branch to the one which is on launchpad, after having
406
.. i18n: done this, your commit will be applied on launchpad directly (unless you use ``--local``)::
408
.. i18n: bzr pull # Get modifications on your branch from others
410
.. i18n: bzr ci # commit your changes on your public branch
413
After having done that, your branch is public on Launchpad, in the `OpenObject
414
project <https://code.launchpad.net/openobject>`_, and commiters can work on
415
it, review it and propose for integration in the official branch. The last line
416
allows you to rebind your branch to the one which is on launchpad, after having
417
done this, your commit will be applied on launchpad directly (unless you use ``--local``)::
419
bzr pull # Get modifications on your branch from others
421
bzr ci # commit your changes on your public branch
423
.. i18n: If your changes fix a public bug on launchpad, you can use this to mark the bug as fixed by your branch::
425
.. i18n: bzr ci --fixes=lp:453123 # Where 453123 is a bug ID
428
If your changes fix a public bug on launchpad, you can use this to mark the bug as fixed by your branch::
430
bzr ci --fixes=lp:453123 # Where 453123 is a bug ID
432
.. i18n: Once your branch is mature, mark it as mature in the web interface of launchpad
433
.. i18n: and request for merging in the official release. Your branch will be reviewed
434
.. i18n: by a commiter and then the quality team to be merged in the official release.
437
Once your branch is mature, mark it as mature in the web interface of launchpad
438
and request for merging in the official release. Your branch will be reviewed
439
by a commiter and then the quality team to be merged in the official release.
441
.. i18n: How to commit Your Work
442
.. i18n: +++++++++++++++++++++++
445
How to commit Your Work
446
+++++++++++++++++++++++
448
.. i18n: If you want to contribute on OpenERP or OpenObject, here is the proposed method:
451
If you want to contribute on OpenERP or OpenObject, here is the proposed method:
453
.. i18n: * You create a branch on launchpad on the project that interest you. It's
454
.. i18n: important that you create your branch on launchpad and not on your local
455
.. i18n: system so that we can easily merge, share code between projects and
456
.. i18n: centralize futur developments.
457
.. i18n: * You develop your own features or bugfixes
458
.. i18n: in your own branch on launchpad. Don't forget to set the status of your
459
.. i18n: branch (new, experimental, development, mature, ...) so that contributors
460
.. i18n: knows what they can use or not.
461
.. i18n: * Once your code is good enough, you propose your branch for merging
462
.. i18n: * Your work will be evaluated by one responsible of the commiters team.
464
.. i18n: - If they accept your branch for integration in the official version, they
465
.. i18n: will submit to the quality team that will review and merge in the official
467
.. i18n: - If the commiter team refuses your branch, they will explain why
468
.. i18n: so that you can review your code to better fits guidelines (problem for
469
.. i18n: futur migrations, ...)
472
* You create a branch on launchpad on the project that interest you. It's
473
important that you create your branch on launchpad and not on your local
474
system so that we can easily merge, share code between projects and
475
centralize futur developments.
476
* You develop your own features or bugfixes
477
in your own branch on launchpad. Don't forget to set the status of your
478
branch (new, experimental, development, mature, ...) so that contributors
479
knows what they can use or not.
480
* Once your code is good enough, you propose your branch for merging
481
* Your work will be evaluated by one responsible of the commiters team.
483
- If they accept your branch for integration in the official version, they
484
will submit to the quality team that will review and merge in the official
486
- If the commiter team refuses your branch, they will explain why
487
so that you can review your code to better fits guidelines (problem for
488
futur migrations, ...)
490
.. i18n: The `extra-addons branch <https://code.launchpad.net/~openerp-commiter/openobject-addons/trunk-extra-addons>`_,
491
.. i18n: that stores all extra modules, is directly accessible to all commiters. If you
492
.. i18n: are a commiter, you can work directly on this branch and commit your own work.
493
.. i18n: This branch do not require a validation of the quality team. You should put
494
.. i18n: there your special modules for your own customers.
497
The `extra-addons branch <https://code.launchpad.net/~openerp-commiter/openobject-addons/trunk-extra-addons>`_,
498
that stores all extra modules, is directly accessible to all commiters. If you
499
are a commiter, you can work directly on this branch and commit your own work.
500
This branch do not require a validation of the quality team. You should put
501
there your special modules for your own customers.
503
.. i18n: If you want to propose or develop new modules, we suggest you to create your
504
.. i18n: own branch in the `openobject-addons project <https://launchpad.net/openobject-addons>`_
505
.. i18n: and develop within your branch. You can fill in a bug to request that
506
.. i18n: your modules are integrated in one of the two branches:
509
If you want to propose or develop new modules, we suggest you to create your
510
own branch in the `openobject-addons project <https://launchpad.net/openobject-addons>`_
511
and develop within your branch. You can fill in a bug to request that
512
your modules are integrated in one of the two branches:
514
.. i18n: * `extra-addons branch <https://code.launchpad.net/~openerp-commiter/openobject-addons/trunk-extra-addons>`_ : if your module touches a few companies
515
.. i18n: * `addons <https://code.launchpad.net/~openerp/openobject-addons/trunk>`_ : if your module will be usefull for most of the companies
518
* `extra-addons branch <https://code.launchpad.net/~openerp-commiter/openobject-addons/trunk-extra-addons>`_ : if your module touches a few companies
519
* `addons <https://code.launchpad.net/~openerp/openobject-addons/trunk>`_ : if your module will be usefull for most of the companies
521
.. i18n: We invite all our partners and contributors to work in that way so that we can
522
.. i18n: easily integrate and share the work done between the different projects.
525
We invite all our partners and contributors to work in that way so that we can
526
easily integrate and share the work done between the different projects.
528
.. i18n: Answer Tracker and Bugs Management
529
.. i18n: ----------------------------------
532
Answer Tracker and Bugs Management
533
----------------------------------
535
.. i18n: We use launchpad on the openobject project to track all bugs and features
536
.. i18n: request related to openerp and openobject. the bug tracker is available here:
539
We use launchpad on the openobject project to track all bugs and features
540
request related to openerp and openobject. the bug tracker is available here:
542
.. i18n: * Bug Tracker : https://bugs.launchpad.net/openobject
543
.. i18n: * Ideas Tracker : https://blueprints.launchpad.net/openobject
544
.. i18n: * FAQ Manager : https://answers.launchpad.net/openobject
547
* Bug Tracker : https://bugs.launchpad.net/openobject
548
* Ideas Tracker : https://blueprints.launchpad.net/openobject
549
* FAQ Manager : https://answers.launchpad.net/openobject
551
.. i18n: Every contributor can report bug and propose bugfixes for the bugs.
552
.. i18n: The status of the bug is set according to the correction.
555
Every contributor can report bug and propose bugfixes for the bugs.
556
The status of the bug is set according to the correction.
558
.. i18n: When a particular branch fixes the bug, a commiter (member of the `Commiter
559
.. i18n: Team <https://launchpad.net/~openerp-commiter>`_) can set the status to "Fix
560
.. i18n: Commited". Only commiters have the right to change the status to "Fix
561
.. i18n: Committed.", after they validated the proposed patch or branch that fixes the
565
When a particular branch fixes the bug, a commiter (member of the `Commiter
566
Team <https://launchpad.net/~openerp-commiter>`_) can set the status to "Fix
567
Commited". Only commiters have the right to change the status to "Fix
568
Committed.", after they validated the proposed patch or branch that fixes the
571
.. i18n: The `Quality Team <https://launchpad.net/~openerp>`_ have a look every day to
572
.. i18n: bugs in the status "Fix Commited". They check the quality of the code and merge
573
.. i18n: in the official branch if it's ok. To limit the work of the quality team, it's
574
.. i18n: important that only commiters can set the bug in the status "Fix Commited".
575
.. i18n: Once quality team finish merging, they change the status to "Fix Released".
578
The `Quality Team <https://launchpad.net/~openerp>`_ have a look every day to
579
bugs in the status "Fix Commited". They check the quality of the code and merge
580
in the official branch if it's ok. To limit the work of the quality team, it's
581
important that only commiters can set the bug in the status "Fix Commited".
582
Once quality team finish merging, they change the status to "Fix Released".
591
.. i18n: Translations are managed by
592
.. i18n: the `Launchpad Web interface <https://translations.launchpad.net/openobject>`_. Here, you'll
593
.. i18n: find the list of translatable projects.
596
Translations are managed by
597
the `Launchpad Web interface <https://translations.launchpad.net/openobject>`_. Here, you'll
598
find the list of translatable projects.
600
.. i18n: Please read the `FAQ <https://answers.launchpad.net/rosetta/+faqs>`_ before asking questions.
603
Please read the `FAQ <https://answers.launchpad.net/rosetta/+faqs>`_ before asking questions.
612
.. 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.
615
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.
617
.. i18n: Launchpad Blueprint helps you to plan future release with two tools:
620
Launchpad Blueprint helps you to plan future release with two tools:
622
.. i18n: * milestones: points in time, such as a future release or development sprint
623
.. i18n: * series goals: a statement of intention to work on the blueprint for a particular series.
626
* milestones: points in time, such as a future release or development sprint
627
* series goals: a statement of intention to work on the blueprint for a particular series.
629
.. 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.
632
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.
634
.. 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.
637
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.
639
.. i18n: However, if the wiki software supports email change notifications, Launchpad can even notify you of changes to the wiki page.
642
However, if the wiki software supports email change notifications, Launchpad can even notify you of changes to the wiki page.
644
.. 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.
647
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.
649
.. i18n: The Buleprints for OpenERP are listed here:
651
.. i18n: * https://blueprints.launchpad.net/openerp
652
.. i18n: * https://blueprints.launchpad.net/~openerp-commiter
655
The Buleprints for OpenERP are listed here:
657
* https://blueprints.launchpad.net/openerp
658
* https://blueprints.launchpad.net/~openerp-commiter
added
removed
i18n/ru/source/developer/1_1_Introduction/2_launchpad.rst
