/brz/remove-bazaar

To get this branch, use:
bzr branch http://gegoxaren.bato24.eu/bzr/brz/remove-bazaar

« back to all changes in this revision

Viewing changes to doc/developers/HACKING.txt

  • Committer: Jelmer Vernooij
  • Date: 2018-06-14 17:59:16 UTC
  • mto: This revision was merged to the branch mainline in revision 7065.
  • Revision ID: jelmer@jelmer.uk-20180614175916-a2e2xh5k533guq1x
Move breezy.plugins.git to breezy.git.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/HACKING.txt
12
12
document, send a merge request or new text to the mailing list.
13
13
 
14
14
The latest developer documentation can be found online at
15
 
https://www.breezy-vcs.org/developers/.
 
15
http://doc.bazaar.canonical.com/developers/.
16
16
 
17
17
Getting Started
18
18
###############
52
52
 
53
53
There is a very active community around Breezy. Mostly we meet on IRC
54
54
(#bzr on irc.freenode.net) and on the mailing list. To join the Breezy
55
 
community, see https://www.breezy-vcs.org/pages/support.html.
 
55
community, see http://wiki.bazaar.canonical.com/BzrSupport.
56
56
 
57
57
If you are planning to make a change, it's a very good idea to mention it
58
58
on the IRC channel and/or on the mailing list. There are many advantages
87
87
copy of bzr.dev?`_.)
88
88
::
89
89
 
90
 
 $ brz init-shared-repo ~/bzr
 
90
 $ brz init-repo ~/bzr
91
91
 $ cd ~/bzr
92
92
 $ brz branch lp:brz bzr.dev
93
93
 
125
125
"Propose for merging into another branch".  Select "lp:bzr" to hand
126
126
your changes off to the Breezy developers for review and merging.
127
127
 
128
 
Alternatively, after pushing you can use the ``propose`` command to
 
128
Alternatively, after pushing you can use the ``lp-propose`` command to 
129
129
create the merge proposal.
130
130
 
131
131
Using a meaningful name for your branch will help you and the reviewer(s)
205
205
 
206
206
* Patch Queue Manager - https://launchpad.net/pqm/
207
207
 
208
 
For further information, see <https://www.breezy-vcs.org/developers/>.
 
208
For further information, see <http://wiki.bazaar.canonical.com/BzrDevelopment>.
 
209
 
 
210
 
209
211
 
210
212
 
211
213
Preparing a Sandbox for Making Changes to Breezy
292
294
 
293
295
 
294
296
Automatically-generated API reference information is available at
295
 
<https://www.breezy-vcs.org/developers/api/>.
 
297
<http://people.canonical.com/~mwh/bzrlibapi/>.
296
298
 
297
299
See also the `Breezy Architectural Overview
298
 
<https://www.breezy-vcs.org/developers/overview.html>`_.
 
300
<http://doc.bazaar.canonical.com/developers/overview.html>`_.
299
301
 
300
302
 
301
303
Core Topics
531
533
 
532
534
* reviewing changes
533
535
* planning releases
534
 
* managing releases (see `Releasing Breezy <https://www.breezy-vcs.org/developers/releasing.html>`_)
 
536
* managing releases (see `Releasing Breezy <http://doc.bazaar.canonical.com/developers/releasing.html>`_)
535
537
 
536
538
.. note::
537
539
  Removing barriers to community participation is a key reason for adopting