← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/developers/HACKING.txt

  • Committer: Andrew Bennetts
  • Date: 2011-07-11 02:06:18 UTC
  • mfrom: (6018 +trunk)
  • mto: This revision was merged to the branch mainline in revision 6020.
  • Revision ID: andrew.bennetts@canonical.com-20110711020618-gcjgoeb5azwjrnu6
Merge lp:bzr/2.4.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/HACKING.txt
117
117
`your_lp_username`.  You can push your branch to Launchpad directly from
118
118
Bazaar::
119
119
 
120
 
  $ bzr push lp:~your_lp_username/bzr/meaningful_name_here
 
120
  $ bzr push lp:~<your_lp_username>/bzr/meaningful_name_here
121
121
 
122
122
After you have pushed your branch, you will need to propose it for merging to
123
123
the Bazaar trunk.  Go to
124
 
<https://launchpad.net/your_lp_username/bzr/meaningful_name_here> and choose
125
 
"Propose for merging into another branch".  Select "~bzr/bzr/trunk" to hand
 
124
<https://launchpad.net/~<your_lp_username>/bzr/meaningful_name_here> and choose
 
125
"Propose for merging into another branch".  Select "lp:bzr" to hand
126
126
your changes off to the Bazaar developers for review and merging.
127
127
 
128
128
Alternatively, after pushing you can use the ``lp-propose`` command to 
254
254
    This file covers a brief introduction to Bazaar and lists some of its
255
255
    key features.
256
256
 
257
 
NEWS
258
 
    Summary of changes in each Bazaar release that can affect users or
259
 
    plugin developers.
260
 
 
261
257
setup.py
262
258
    Installs Bazaar system-wide or to your home directory.  To perform
263
259
    development work on Bazaar it is not required to run this file - you
285
281
    Documentation specifically targeted at Bazaar and plugin developers.
286
282
    (Including this document.)
287
283
 
 
284
doc/en/release-notes/
 
285
 
 
286
    Detailed changes in each Bazaar release (there is one file by series:
 
287
    bzr-2.3.txt, bzr-2.4.txt, etc) that can affect users or plugin
 
288
    developers.
 
289
 
 
290
doc/en/whats-new/
 
291
 
 
292
    High-level summaries of changes in each Bazaar release (there is one
 
293
    file by series: whats-new-in-2.3.txt, whats-new-in-2.4.txt, etc).
288
294
 
289
295
 
290
296
Automatically-generated API reference information is available at
576
582
stuff covered above, "core" developers have responsibility for:
577
583
 
578
584
* reviewing changes
579
 
* reviewing blueprints
580
585
* planning releases
581
586
* managing releases (see `Releasing Bazaar <http://doc.bazaar.canonical.com/developers/releasing.html>`_)
582
587