← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/developers/HACKING.txt

  • Committer: Ian Clatworthy
  • Date: 2009-09-09 12:57:43 UTC
  • mto: (4634.37.2 prepare-2.0)
  • mto: This revision was merged to the branch mainline in revision 4689.
  • Revision ID: ian.clatworthy@canonical.com-20090909125743-33t6yu7m1yl4oobn
Get plain-style documentation generation working again

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/HACKING.txt
260
260
Automatically-generated API reference information is available at 
261
261
<http://starship.python.net/crew/mwh/bzrlibapi/>.  
262
262
 
263
 
See also the :doc:`Bazaar Architectural Overview  <overview>`.
 
263
See also the `Bazaar Architectural Overview
 
264
<http://doc.bazaar-vcs.org/developers/overview.html>`_.
264
265
 
265
266
 
266
267
The Code Review Process
835
836
Test coverage
836
837
=============
837
838
 
838
 
All code should be exercised by the test suite.  See :doc:`Guide to Testing
839
 
Bazaar <testing>` for detailed information about writing tests.
 
839
All code should be exercised by the test suite.  See the `Bazaar Testing
 
840
Guide <http://doc.bazaar-vcs.org/developers/testing.html>`_ for detailed
 
841
information about writing tests.
840
842
 
841
843
 
842
844
Core Topics
1397
1399
* reviewing changes
1398
1400
* reviewing blueprints
1399
1401
* planning releases
1400
 
* managing releases (see :doc:`Releasing Bazaar <releasing>`)
 
1402
* managing releases (see `Releasing Bazaar <http://doc.bazaar-vcs.org/developers/releasing.html>`_)
1401
1403
 
1402
1404
.. note::
1403
1405
  Removing barriers to community participation is a key reason for adopting