~bzr-pqm/bzr/bzr.dev

Expanded developer doc index (Eric Siegerman)

added added

removed removed

-----------------

There is plenty of code to write. Testers are always welcome for experimental

changes. In general, pick a BLUE node from performance.png which has nothing

changes. In general, from the `Performance Tasks`_ graph, pick a BLUE node that has nothing

pointing at it that is also BLUE, and start working on that.

Adhoc performance work can also be done. One useful tool is the 'evil' debug

Ad-hoc performance work can also be done. One useful tool is the 'evil' debug

flag. For instance running ``bzr -Devil commit -m "test"`` will log a backtrace

to the bzr log file for every method call which triggers a slow or non-scalable

part of the bzr library. So checking that a given command with ``-Devil`` has

If you were at the London performance sprint, please help finish documenting

the core command analysis work. The core commands that have not been analysed

are listed in performance.dot as the BLUE nodes. For quick reference:

are listed in `Performance Tasks`_ as the BLUE nodes. For quick reference:

* status

* log

---------

The usual resources for contributing to bzr - the mailing list, wiki, bug

tracker and IRC channels are documented in the HACKING_ document. Additionally

tracker and IRC channels are documented in the `Bazaar Developer Guide`_. Additionally

there are members of the project focusing on performance at the moment who are

willing to mentor contributors on performance issues. Just send a mail to the

list asking for mentoring on the step of the performance plan you want to help

with.

.. _HACKING: ../en/developer-guide/HACKING.html

.. _`Bazaar Developer Guide`: ../en/developer-guide/HACKING.html

.. _`Performance Tasks`: performance.png