73
61
Bazaar Development in a Nutshell
74
62
================================
76
.. was from http://wiki.bazaar.canonical.com/BzrGivingBack
78
One of the fun things about working on a version control system like Bazaar is
79
that the users have a high level of proficiency in contributing back into
80
the tool. Consider the following very brief introduction to contributing back
81
to Bazaar. More detailed instructions are in the following sections.
86
First, get a local copy of the development mainline (See `Why make a local
92
$ bzr branch lp:bzr bzr.dev
94
Now make your own branch::
96
$ bzr branch bzr.dev 123456-my-bugfix
98
This will give you a branch called "123456-my-bugfix" that you can work on
99
and commit in. Here, you can study the code, make a fix or a new feature.
100
Feel free to commit early and often (after all, it's your branch!).
102
Documentation improvements are an easy place to get started giving back to the
103
Bazaar project. The documentation is in the `doc/` subdirectory of the Bazaar
106
When you are done, make sure that you commit your last set of changes as well!
107
Once you are happy with your changes, ask for them to be merged, as described
110
Making a Merge Proposal
111
-----------------------
113
The Bazaar developers use Launchpad to further enable a truly distributed
114
style of development. Anyone can propose a branch for merging into the Bazaar
115
trunk. To start this process, you need to push your branch to Launchpad. To
116
do this, you will need a Launchpad account and user name, e.g.
117
`your_lp_username`. You can push your branch to Launchpad directly from
120
$ bzr push lp:~<your_lp_username>/bzr/meaningful_name_here
122
After you have pushed your branch, you will need to propose it for merging to
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 "lp:bzr" to hand
126
your changes off to the Bazaar developers for review and merging.
128
Alternatively, after pushing you can use the ``lp-propose`` command to
129
create the merge proposal.
131
Using a meaningful name for your branch will help you and the reviewer(s)
132
better track the submission. Use a very succint description of your submission
133
and prefix it with bug number if needed (lp:~mbp/bzr/484558-merge-directory
134
for example). Alternatively, you can suffix with the bug number
135
(lp:~jameinel/bzr/export-file-511987).
141
Please put a "cover letter" on your merge request explaining:
143
* the reason **why** you're making this change
145
* **how** this change achieves this purpose
147
* anything else you may have fixed in passing
149
* anything significant that you thought of doing, such as a more
150
extensive fix or a different approach, but didn't or couldn't do now
152
A good cover letter makes reviewers' lives easier because they can decide
153
from the letter whether they agree with the purpose and approach, and then
154
assess whether the patch actually does what the cover letter says.
155
Explaining any "drive-by fixes" or roads not taken may also avoid queries
156
from the reviewer. All in all this should give faster and better reviews.
157
Sometimes writing the cover letter helps the submitter realize something
158
else they need to do. The size of the cover letter should be proportional
159
to the size and complexity of the patch.
162
Why make a local copy of bzr.dev?
163
---------------------------------
165
Making a local mirror of bzr.dev is not strictly necessary, but it means
167
- You can use that copy of bzr.dev as your main bzr executable, and keep it
168
up-to-date using ``bzr pull``.
169
- Certain operations are faster, and can be done when offline. For example:
172
- ``bzr diff -r ancestor:...``
175
- When it's time to create your next branch, it's more convenient. When you
176
have further contributions to make, you should do them in their own branch::
179
$ bzr branch bzr.dev additional_fixes
180
$ cd additional_fixes # hack, hack, hack
64
Looking for a 10 minute introduction to submitting a change?
65
See http://bazaar-vcs.org/BzrGivingBack.
67
TODO: Merge that Wiki page into this document.
184
70
Understanding the Development Process
185
71
=====================================
187
The development team follows many practices including:
73
The development team follows many best-practices including:
189
75
* a public roadmap and planning process in which anyone can participate
202
88
* Launchpad - https://launchpad.net/
204
* Bazaar - http://bazaar.canonical.com/
90
* Bazaar - http://bazaar-vcs.org/
92
* Bundle Buggy - http://bundlebuggy.aaronbentley.com/
206
94
* Patch Queue Manager - https://launchpad.net/pqm/
208
For further information, see <http://wiki.bazaar.canonical.com/BzrDevelopment>.
96
For further information, see http://bazaar-vcs.org/BzrDevelopment.
99
A Closer Look at the Merge & Review Process
100
===========================================
102
If you'd like to propose a change, please post to the
103
bazaar@lists.canonical.com list with a bundle, patch, or link to a
104
branch. Put '[PATCH]' or '[MERGE]' in the subject so Bundle Buggy
105
can pick it out, and explain the change in the email message text.
106
Remember to update the NEWS file as part of your change if it makes any
107
changes visible to users or plugin developers. Please include a diff
108
against mainline if you're giving a link to a branch.
110
You can generate a bundle like this::
112
bzr bundle > mybundle.patch
114
A .patch extension is recommended instead of .bundle as many mail clients
115
will send the latter as a binary file. If a bundle would be too long or your
116
mailer mangles whitespace (e.g. implicitly converts Unix newlines to DOS
117
newlines), use the merge-directive command instead like this::
119
bzr merge-directive http://bazaar-vcs.org http://example.org/my_branch > my_directive.patch
121
See the help for details on the arguments to merge-directive.
123
Please do **NOT** put [PATCH] or [MERGE] in the subject line if you don't
124
want it to be merged. If you want comments from developers rather than
125
to be merged, you can put '[RFC]' in the subject line.
127
Anyone is welcome to review code. There are broadly three gates for
130
* Doesn't reduce test coverage: if it adds new methods or commands,
131
there should be tests for them. There is a good test framework
132
and plenty of examples to crib from, but if you are having trouble
133
working out how to test something feel free to post a draft patch
136
* Doesn't reduce design clarity, such as by entangling objects
137
we're trying to separate. This is mostly something the more
138
experienced reviewers need to help check.
140
* Improves bugs, features, speed, or code simplicity.
142
Code that goes in should pass all three. The core developers take care
143
to keep the code quality high and understandable while recognising that
144
perfect is sometimes the enemy of good. (It is easy for reviews to make
145
people notice other things which should be fixed but those things should
146
not hold up the original fix being accepted. New things can easily be
147
recorded in the Bug Tracker instead.)
149
Anyone can "vote" on the mailing list. Core developers can also vote using
150
Bundle Buggy. Here are the voting codes and their explanations.
152
:approve: Reviewer wants this submission merged.
153
:tweak: Reviewer wants this submission merged with small changes. (No
155
:abstain: Reviewer does not intend to vote on this patch.
156
:resubmit: Please make changes and resubmit for review.
157
:reject: Reviewer doesn't want this kind of change merged.
158
:comment: Not really a vote. Reviewer just wants to comment, for now.
160
If a change gets two approvals from core reviewers, and no rejections,
161
then it's OK to come in. Any of the core developers can bring it into the
162
bzr.dev trunk and backport it to maintenance branches if required. The
163
Release Manager will merge the change into the branch for a pending
164
release, if any. As a guideline, core developers usually merge their own
165
changes and volunteer to merge other contributions if they were the second
166
reviewer to agree to a change.
168
To track the progress of proposed changes, use Bundle Buggy. See
169
http://bundlebuggy.aaronbentley.com/help for a link to all the
170
outstanding merge requests together with an explanation of the columns.
171
Bundle Buggy will also mail you a link to track just your change.
213
174
Preparing a Sandbox for Making Changes to Bazaar
214
175
================================================
216
177
Bazaar supports many ways of organising your work. See
217
http://wiki.bazaar.canonical.com/SharedRepositoryLayouts for a summary of the
178
http://bazaar-vcs.org/SharedRepositoryLayouts for a summary of the
218
179
popular alternatives.
220
181
Of course, the best choice for you will depend on numerous factors:
242
203
Navigating the Code Base
243
204
========================
245
.. Was at <http://wiki.bazaar.canonical.com/NewDeveloperIntroduction>
247
Some of the key files in this directory are:
250
The command you run to start Bazaar itself. This script is pretty
251
short and just does some checks then jumps into bzrlib.
254
This file covers a brief introduction to Bazaar and lists some of its
258
Installs Bazaar system-wide or to your home directory. To perform
259
development work on Bazaar it is not required to run this file - you
260
can simply run the bzr command from the top level directory of your
261
development copy. Note: That if you run setup.py this will create a
262
'build' directory in your development branch. There's nothing wrong
263
with this but don't be confused by it. The build process puts a copy
264
of the main code base into this build directory, along with some other
265
files. You don't need to go in here for anything discussed in this
269
Possibly the most exciting folder of all, bzrlib holds the main code
270
base. This is where you will go to edit python files and contribute to
274
Holds documentation on a whole range of things on Bazaar from the
275
origination of ideas within the project to information on Bazaar
276
features and use cases. Within this directory there is a subdirectory
277
for each translation into a human language. All the documentation
278
is in the ReStructuredText markup language.
281
Documentation specifically targeted at Bazaar and plugin developers.
282
(Including this document.)
284
doc/en/release-notes/
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
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).
296
Automatically-generated API reference information is available at
297
<http://people.canonical.com/~mwh/bzrlibapi/>.
299
See also the `Bazaar Architectural Overview
300
<http://doc.bazaar.canonical.com/developers/overview.html>`_.
206
TODO: List and describe in one line the purpose of each directory
207
inside an installation of bzr.
209
TODO: Refer to a central location holding an up to date copy of the API
210
documentation generated by epydoc, e.g. something like
211
http://starship.python.net/crew/mwh/bzrlibapi/bzrlib.html.
217
The Importance of Testing
218
=========================
220
Reliability is a critical success factor for any Version Control System.
221
We want Bazaar to be highly reliable across multiple platforms while
222
evolving over time to meet the needs of its community.
224
In a nutshell, this is want we expect and encourage:
226
* New functionality should have test cases. Preferably write the
227
test before writing the code.
229
In general, you can test at either the command-line level or the
230
internal API level. See Writing tests below for more detail.
232
* Try to practice Test-Driven Development: before fixing a bug, write a
233
test case so that it does not regress. Similarly for adding a new
234
feature: write a test case for a small version of the new feature before
235
starting on the code itself. Check the test fails on the old code, then
236
add the feature or fix and check it passes.
238
By doing these things, the Bazaar team gets increased confidence that
239
changes do what they claim to do, whether provided by the core team or
240
by community members. Equally importantly, we can be surer that changes
241
down the track do not break new features or bug fixes that you are
244
As of May 2007, Bazaar ships with a test suite containing over 6000 tests
245
and growing. We are proud of it and want to remain so. As community
246
members, we all benefit from it. Would you trust version control on
247
your project to a product *without* a test suite like Bazaar has?
250
Running the Test Suite
251
======================
253
Currently, bzr selftest is used to invoke tests.
254
You can provide a pattern argument to run a subset. For example,
255
to run just the blackbox tests, run::
257
./bzr selftest -v blackbox
259
To skip a particular test (or set of tests), use the --exclude option
260
(shorthand -x) like so::
262
./bzr selftest -v -x blackbox
264
To ensure that all tests are being run and succeeding, you can use the
265
--strict option which will fail if there are any missing features or known
268
./bzr selftest --strict
270
To list tests without running them, use the --list-only option like so::
272
./bzr selftest --list-only
274
This option can be combined with other selftest options (like -x) and
275
filter patterns to understand their effect.
281
In general tests should be placed in a file named test_FOO.py where
282
FOO is the logical thing under test. That file should be placed in the
283
tests subdirectory under the package being tested.
285
For example, tests for merge3 in bzrlib belong in bzrlib/tests/test_merge3.py.
286
See bzrlib/tests/test_sampler.py for a template test script.
288
Tests can be written for the UI or for individual areas of the library.
289
Choose whichever is appropriate: if adding a new command, or a new command
290
option, then you should be writing a UI test. If you are both adding UI
291
functionality and library functionality, you will want to write tests for
292
both the UI and the core behaviours. We call UI tests 'blackbox' tests
293
and they are found in ``bzrlib/tests/blackbox/*.py``.
295
When writing blackbox tests please honour the following conventions:
297
1. Place the tests for the command 'name' in
298
bzrlib/tests/blackbox/test_name.py. This makes it easy for developers
299
to locate the test script for a faulty command.
301
2. Use the 'self.run_bzr("name")' utility function to invoke the command
302
rather than running bzr in a subprocess or invoking the
303
cmd_object.run() method directly. This is a lot faster than
304
subprocesses and generates the same logging output as running it in a
305
subprocess (which invoking the method directly does not).
307
3. Only test the one command in a single test script. Use the bzrlib
308
library when setting up tests and when evaluating the side-effects of
309
the command. We do this so that the library api has continual pressure
310
on it to be as functional as the command line in a simple manner, and
311
to isolate knock-on effects throughout the blackbox test suite when a
312
command changes its name or signature. Ideally only the tests for a
313
given command are affected when a given command is changed.
315
4. If you have a test which does actually require running bzr in a
316
subprocess you can use ``run_bzr_subprocess``. By default the spawned
317
process will not load plugins unless ``--allow-plugins`` is supplied.
323
We make selective use of doctests__. In general they should provide
324
*examples* within the API documentation which can incidentally be tested. We
325
don't try to test every important case using doctests -- regular Python
326
tests are generally a better solution.
328
Most of these are in ``bzrlib/doc/api``. More additions are welcome.
330
__ http://docs.python.org/lib/module-doctest.html
333
Skipping tests and test requirements
334
------------------------------------
336
In our enhancements to unittest we allow for some addition results beyond
337
just success or failure.
339
If a test can't be run, it can say that it's skipped. This is typically
340
used in parameterized tests - for example if a transport doesn't support
341
setting permissions, we'll skip the tests that relating to that. ::
344
return self.branch_format.initialize(repo.bzrdir)
345
except errors.UninitializableFormat:
346
raise tests.TestSkipped('Uninitializable branch format')
348
Raising TestSkipped is a good idea when you want to make it clear that the
349
test was not run, rather than just returning which makes it look as if it
352
Several different cases are distinguished:
355
Generic skip; the only type that was present up to bzr 0.18.
358
The test doesn't apply to the parameters with which it was run.
359
This is typically used when the test is being applied to all
360
implementations of an interface, but some aspects of the interface
361
are optional and not present in particular concrete
362
implementations. (Some tests that should raise this currently
363
either silently return or raise TestSkipped.) Another option is
364
to use more precise parameterization to avoid generating the test
368
**(Not implemented yet)**
369
The test can't be run because of an inherent limitation of the
370
environment, such as not having symlinks or not supporting
374
The test can't be run because a dependency (typically a Python
375
library) is not available in the test environment. These
376
are in general things that the person running the test could fix
377
by installing the library. It's OK if some of these occur when
378
an end user runs the tests or if we're specifically testing in a
379
limited environment, but a full test should never see them.
382
The test exists but is known to fail, for example because the
383
code to fix it hasn't been run yet. Raising this allows
384
you to distinguish these failures from the ones that are not
385
expected to fail. This could be conditionally raised if something
386
is broken on some platforms but not on others.
388
We plan to support three modes for running the test suite to control the
389
interpretation of these results. Strict mode is for use in situations
390
like merges to the mainline and releases where we want to make sure that
391
everything that can be tested has been tested. Lax mode is for use by
392
developers who want to temporarily tolerate some known failures. The
393
default behaviour is obtained by ``bzr selftest`` with no options, and
394
also (if possible) by running under another unittest harness.
396
======================= ======= ======= ========
397
result strict default lax
398
======================= ======= ======= ========
399
TestSkipped pass pass pass
400
TestNotApplicable pass pass pass
401
TestPlatformLimit pass pass pass
402
TestDependencyMissing fail pass pass
403
KnownFailure fail pass pass
404
======================= ======= ======= ========
407
Test feature dependencies
408
-------------------------
410
Rather than manually checking the environment in each test, a test class
411
can declare its dependence on some test features. The feature objects are
412
checked only once for each run of the whole test suite.
414
For historical reasons, as of May 2007 many cases that should depend on
415
features currently raise TestSkipped.)
419
class TestStrace(TestCaseWithTransport):
421
_test_needs_features = [StraceFeature]
423
This means all tests in this class need the feature. The feature itself
424
should provide a ``_probe`` method which is called once to determine if
427
These should generally be equivalent to either TestDependencyMissing or
428
sometimes TestPlatformLimit.
434
Known failures are when a test exists but we know it currently doesn't
435
work, allowing the test suite to still pass. These should be used with
436
care, we don't want a proliferation of quietly broken tests. It might be
437
appropriate to use them if you've committed a test for a bug but not the
438
fix for it, or if something works on Unix but not on Windows.
441
Testing exceptions and errors
442
-----------------------------
444
It's important to test handling of errors and exceptions. Because this
445
code is often not hit in ad-hoc testing it can often have hidden bugs --
446
it's particularly common to get NameError because the exception code
447
references a variable that has since been renamed.
449
.. TODO: Something about how to provoke errors in the right way?
451
In general we want to test errors at two levels:
453
1. A test in ``test_errors.py`` checking that when the exception object is
454
constructed with known parameters it produces an expected string form.
455
This guards against mistakes in writing the format string, or in the
456
``str`` representations of its parameters. There should be one for
457
each exception class.
459
2. Tests that when an api is called in a particular situation, it raises
460
an error of the expected class. You should typically use
461
``assertRaises``, which in the Bazaar test suite returns the exception
462
object to allow you to examine its parameters.
464
In some cases blackbox tests will also want to check error reporting. But
465
it can be difficult to provoke every error through the commandline
466
interface, so those tests are only done as needed -- eg in response to a
467
particular bug or if the error is reported in an unusual way(?) Blackbox
468
tests should mostly be testing how the command-line interface works, so
469
should only test errors if there is something particular to the cli in how
470
they're displayed or handled.
476
The Python ``warnings`` module is used to indicate a non-fatal code
477
problem. Code that's expected to raise a warning can be tested through
480
The test suite can be run with ``-Werror`` to check no unexpected errors
483
However, warnings should be used with discretion. It's not an appropriate
484
way to give messages to the user, because the warning is normally shown
485
only once per source line that causes the problem. You should also think
486
about whether the warning is serious enought that it should be visible to
487
users who may not be able to fix it.
490
Interface implementation testing and test scenarios
491
---------------------------------------------------
493
There are several cases in Bazaar of multiple implementations of a common
494
conceptual interface. ("Conceptual" because
495
it's not necessary for all the implementations to share a base class,
496
though they often do.) Examples include transports and the working tree,
497
branch and repository classes.
499
In these cases we want to make sure that every implementation correctly
500
fulfils the interface requirements. For example, every Transport should
501
support the ``has()`` and ``get()`` and ``clone()`` methods. We have a
502
sub-suite of tests in ``test_transport_implementations``. (Most
503
per-implementation tests are in submodules of ``bzrlib.tests``, but not
504
the transport tests at the moment.)
506
These tests are repeated for each registered Transport, by generating a
507
new TestCase instance for the cross product of test methods and transport
508
implementations. As each test runs, it has ``transport_class`` and
509
``transport_server`` set to the class it should test. Most tests don't
510
access these directly, but rather use ``self.get_transport`` which returns
511
a transport of the appropriate type.
513
The goal is to run per-implementation only tests that relate to that
514
particular interface. Sometimes we discover a bug elsewhere that happens
515
with only one particular transport. Once it's isolated, we can consider
516
whether a test should be added for that particular implementation,
517
or for all implementations of the interface.
519
The multiplication of tests for different implementations is normally
520
accomplished by overriding the ``test_suite`` function used to load
521
tests from a module. This function typically loads all the tests,
522
then applies a TestProviderAdapter to them, which generates a longer
523
suite containing all the test variations.
529
Some utilities are provided for generating variations of tests. This can
530
be used for per-implementation tests, or other cases where the same test
531
code needs to run several times on different scenarios.
533
The general approach is to define a class that provides test methods,
534
which depend on attributes of the test object being pre-set with the
535
values to which the test should be applied. The test suite should then
536
also provide a list of scenarios in which to run the tests.
538
Typically ``multiply_tests_from_modules`` should be called from the test
539
module's ``test_suite`` function.
542
Essential Domain Classes
543
########################
545
Introducing the Object Model
546
============================
548
The core domain objects within the bazaar model are:
558
Transports are explained below. See http://bazaar-vcs.org/Classes/
559
for an introduction to the other key classes.
564
The ``Transport`` layer handles access to local or remote directories.
565
Each Transport object acts like a logical connection to a particular
566
directory, and it allows various operations on files within it. You can
567
*clone* a transport to get a new Transport connected to a subdirectory or
570
Transports are not used for access to the working tree. At present
571
working trees are always local and they are accessed through the regular
572
Python file io mechanisms.
577
Transports work in URLs. Take note that URLs are by definition only
578
ASCII - the decision of how to encode a Unicode string into a URL must be
579
taken at a higher level, typically in the Store. (Note that Stores also
580
escape filenames which cannot be safely stored on all filesystems, but
581
this is a different level.)
583
The main reason for this is that it's not possible to safely roundtrip a
584
URL into Unicode and then back into the same URL. The URL standard
585
gives a way to represent non-ASCII bytes in ASCII (as %-escapes), but
586
doesn't say how those bytes represent non-ASCII characters. (They're not
587
guaranteed to be UTF-8 -- that is common but doesn't happen everywhere.)
589
For example if the user enters the url ``http://example/%e0`` there's no
590
way to tell whether that character represents "latin small letter a with
591
grave" in iso-8859-1, or "latin small letter r with acute" in iso-8859-2
592
or malformed UTF-8. So we can't convert their URL to Unicode reliably.
594
Equally problematic if we're given a url-like string containing non-ascii
595
characters (such as the accented a) we can't be sure how to convert that
596
to the correct URL, because we don't know what encoding the server expects
597
for those characters. (Although this is not totally reliable we might still
598
accept these and assume they should be put into UTF-8.)
600
A similar edge case is that the url ``http://foo/sweet%2Fsour`` contains
601
one directory component whose name is "sweet/sour". The escaped slash is
602
not a directory separator. If we try to convert URLs to regular Unicode
603
paths this information will be lost.
605
This implies that Transports must natively deal with URLs; for simplicity
606
they *only* deal with URLs and conversion of other strings to URLs is done
607
elsewhere. Information they return, such as from ``list_dir``, is also in
608
the form of URL components.
358
659
the expected deprecation message, and also returns the real result from
359
660
the method, so that tests can keep running.
361
Deprecation warnings will be suppressed for final releases, but not for
362
development versions or release candidates, or when running ``bzr
363
selftest``. This gives developers information about whether their code is
364
using deprecated functions, but avoids confusing users about things they
662
Coding Style Guidelines
663
=======================
668
``hasattr`` should not be used because it swallows exceptions including
669
``KeyboardInterrupt``. Instead, say something like ::
671
if getattr(thing, 'name', None) is None
677
Please write PEP-8__ compliant code.
679
__ http://www.python.org/peps/pep-0008.html
681
One often-missed requirement is that the first line of docstrings
682
should be a self-contained one-sentence summary.
684
We use 4 space indents for blocks, and never use tab characters. (In vim,
687
Lines should be no more than 79 characters if at all possible.
688
Lines that continue a long statement may be indented in either of
691
within the parenthesis or other character that opens the block, e.g.::
697
or indented by four spaces::
703
The first is considered clearer by some people; however it can be a bit
704
harder to maintain (e.g. when the method name changes), and it does not
705
work well if the relevant parenthesis is already far to the right. Avoid
708
self.legbone.kneebone.shinbone.toebone.shake_it(one,
714
self.legbone.kneebone.shinbone.toebone.shake_it(one,
720
self.legbone.kneebone.shinbone.toebone.shake_it(
723
For long lists, we like to add a trailing comma and put the closing
724
character on the following line. This makes it easier to add new items in
727
from bzrlib.goo import (
733
There should be spaces between function paramaters, but not between the
734
keyword name and the value::
736
call(1, 3, cheese=quark)
740
;(defface my-invalid-face
741
; '((t (:background "Red" :underline t)))
742
; "Face used to highlight invalid constructs or other uglyties"
745
(defun my-python-mode-hook ()
746
;; setup preferred indentation style.
747
(setq fill-column 79)
748
(setq indent-tabs-mode nil) ; no tabs, never, I will not repeat
749
; (font-lock-add-keywords 'python-mode
750
; '(("^\\s *\t" . 'my-invalid-face) ; Leading tabs
751
; ("[ \t]+$" . 'my-invalid-face) ; Trailing spaces
752
; ("^[ \t]+$" . 'my-invalid-face)); Spaces only
756
(add-hook 'python-mode-hook 'my-python-mode-hook)
758
The lines beginning with ';' are comments. They can be activated
759
if one want to have a strong notice of some tab/space usage
766
* Imports should be done at the top-level of the file, unless there is
767
a strong reason to have them lazily loaded when a particular
768
function runs. Import statements have a cost, so try to make sure
769
they don't run inside hot functions.
771
* Module names should always be given fully-qualified,
772
i.e. ``bzrlib.hashcache`` not just ``hashcache``.
778
Functions, methods or members that are "private" to bzrlib are given
779
a leading underscore prefix. Names without a leading underscore are
780
public not just across modules but to programmers using bzrlib as an
781
API. As a consequence, a leading underscore is appropriate for names
782
exposed across modules but that are not to be exposed to bzrlib API
785
We prefer class names to be concatenated capital words (``TestCase``)
786
and variables, methods and functions to be lowercase words joined by
787
underscores (``revision_id``, ``get_revision``).
789
For the purposes of naming some names are treated as single compound
790
words: "filename", "revno".
792
Consider naming classes as nouns and functions/methods as verbs.
794
Try to avoid using abbreviations in names, because there can be
795
inconsistency if other people use the full name.
801
``revision_id`` not ``rev_id`` or ``revid``
803
Functions that transform one thing to another should be named ``x_to_y``
804
(not ``x2y`` as occurs in some old code.)
810
Python destructors (``__del__``) work differently to those of other
811
languages. In particular, bear in mind that destructors may be called
812
immediately when the object apparently becomes unreferenced, or at some
813
later time, or possibly never at all. Therefore we have restrictions on
814
what can be done inside them.
816
0. Never use a __del__ method without asking Martin/Robert first.
818
1. Never rely on a ``__del__`` method running. If there is code that
819
must run, do it from a ``finally`` block instead.
821
2. Never ``import`` from inside a ``__del__`` method, or you may crash the
824
3. In some places we raise a warning from the destructor if the object
825
has not been cleaned up or closed. This is considered OK: the warning
826
may not catch every case but it's still useful sometimes.
832
In some places we have variables which point to callables that construct
833
new instances. That is to say, they can be used a lot like class objects,
834
but they shouldn't be *named* like classes:
836
> I think that things named FooBar should create instances of FooBar when
837
> called. Its plain confusing for them to do otherwise. When we have
838
> something that is going to be used as a class - that is, checked for via
839
> isinstance or other such idioms, them I would call it foo_class, so that
840
> it is clear that a callable is not sufficient. If it is only used as a
841
> factory, then yes, foo_factory is what I would use.
847
Several places in Bazaar use (or will use) a registry, which is a
848
mapping from names to objects or classes. The registry allows for
849
loading in registered code only when it's needed, and keeping
850
associated information such as a help string or description.
856
To make startup time faster, we use the ``bzrlib.lazy_import`` module to
857
delay importing modules until they are actually used. ``lazy_import`` uses
858
the same syntax as regular python imports. So to import a few modules in a
861
from bzrlib.lazy_import import lazy_import
862
lazy_import(globals(), """
871
revision as _mod_revision,
873
import bzrlib.transport
877
At this point, all of these exist as a ``ImportReplacer`` object, ready to
878
be imported once a member is accessed. Also, when importing a module into
879
the local namespace, which is likely to clash with variable names, it is
880
recommended to prefix it as ``_mod_<module>``. This makes it clearer that
881
the variable is a module, and these object should be hidden anyway, since
882
they shouldn't be imported into other namespaces.
885
Modules versus Members
886
~~~~~~~~~~~~~~~~~~~~~~
888
While it is possible for ``lazy_import()`` to import members of a module
889
when using the ``from module import member`` syntax, it is recommended to
890
only use that syntax to load sub modules ``from module import submodule``.
891
This is because variables and classes can frequently be used without
892
needing a sub-member for example::
894
lazy_import(globals(), """
895
from module import MyClass
899
return isinstance(x, MyClass)
901
This will incorrectly fail, because ``MyClass`` is a ``ImportReplacer``
902
object, rather than the real class.
905
Passing to Other Variables
906
~~~~~~~~~~~~~~~~~~~~~~~~~~
908
It also is incorrect to assign ``ImportReplacer`` objects to other variables.
909
Because the replacer only knows about the original name, it is unable to
910
replace other variables. The ``ImportReplacer`` class will raise an
911
``IllegalUseOfScopeReplacer`` exception if it can figure out that this
912
happened. But it requires accessing a member more than once from the new
913
variable, so some bugs are not detected right away.
919
The null revision is the ancestor of all revisions. Its revno is 0, its
920
revision-id is ``null:``, and its tree is the empty tree. When referring
921
to the null revision, please use ``bzrlib.revision.NULL_REVISION``. Old
922
code sometimes uses ``None`` for the null revision, but this practice is
929
Processing Command Lines
930
------------------------
932
bzrlib has a standard framework for parsing command lines and calling
933
processing routines associated with various commands. See builtins.py
934
for numerous examples.
937
Standard Parameter Types
938
------------------------
940
There are some common requirements in the library: some parameters need to be
941
unicode safe, some need byte strings, and so on. At the moment we have
942
only codified one specific pattern: Parameters that need to be unicode
943
should be checked via ``bzrlib.osutils.safe_unicode``. This will coerce the
944
input into unicode in a consistent fashion, allowing trivial strings to be
945
used for programmer convenience, but not performing unpredictably in the
946
presence of different locales.
952
(The strategy described here is what we want to get to, but it's not
953
consistently followed in the code at the moment.)
955
bzrlib is intended to be a generically reusable library. It shouldn't
956
write messages to stdout or stderr, because some programs that use it
957
might want to display that information through a GUI or some other
960
We can distinguish two types of output from the library:
962
1. Structured data representing the progress or result of an
963
operation. For example, for a commit command this will be a list
964
of the modified files and the finally committed revision number
967
These should be exposed either through the return code or by calls
968
to a callback parameter.
970
A special case of this is progress indicators for long-lived
971
operations, where the caller should pass a ProgressBar object.
973
2. Unstructured log/debug messages, mostly for the benefit of the
974
developers or users trying to debug problems. This should always
975
be sent through ``bzrlib.trace`` and Python ``logging``, so that
976
it can be redirected by the client.
978
The distinction between the two is a bit subjective, but in general if
979
there is any chance that a library would want to see something as
980
structured data, we should make it so.
982
The policy about how output is presented in the text-mode client
983
should be only in the command-line tool.
990
Bazaar has online help for various topics through ``bzr help COMMAND`` or
991
equivalently ``bzr command -h``. We also have help on command options,
992
and on other help topics. (See ``help_topics.py``.)
994
As for python docstrings, the first paragraph should be a single-sentence
995
synopsis of the command.
997
The help for options should be one or more proper sentences, starting with
998
a capital letter and finishing with a full stop (period).
1000
All help messages and documentation should have two spaces between
1007
In general tests should be placed in a file named test_FOO.py where
1008
FOO is the logical thing under test. That file should be placed in the
1009
tests subdirectory under the package being tested.
1011
For example, tests for merge3 in bzrlib belong in bzrlib/tests/test_merge3.py.
1012
See bzrlib/tests/test_sampler.py for a template test script.
1014
Tests can be written for the UI or for individual areas of the library.
1015
Choose whichever is appropriate: if adding a new command, or a new command
1016
option, then you should be writing a UI test. If you are both adding UI
1017
functionality and library functionality, you will want to write tests for
1018
both the UI and the core behaviours. We call UI tests 'blackbox' tests
1019
and they are found in ``bzrlib/tests/blackbox/*.py``.
1021
When writing blackbox tests please honour the following conventions:
1023
1. Place the tests for the command 'name' in
1024
bzrlib/tests/blackbox/test_name.py. This makes it easy for developers
1025
to locate the test script for a faulty command.
1027
2. Use the 'self.run_bzr("name")' utility function to invoke the command
1028
rather than running bzr in a subprocess or invoking the
1029
cmd_object.run() method directly. This is a lot faster than
1030
subprocesses and generates the same logging output as running it in a
1031
subprocess (which invoking the method directly does not).
1033
3. Only test the one command in a single test script. Use the bzrlib
1034
library when setting up tests and when evaluating the side-effects of
1035
the command. We do this so that the library api has continual pressure
1036
on it to be as functional as the command line in a simple manner, and
1037
to isolate knock-on effects throughout the blackbox test suite when a
1038
command changes its name or signature. Ideally only the tests for a
1039
given command are affected when a given command is changed.
1041
4. If you have a test which does actually require running bzr in a
1042
subprocess you can use ``run_bzr_subprocess``. By default the spawned
1043
process will not load plugins unless ``--allow-plugins`` is supplied.
1049
We have a rich collection of tools to support writing tests. Please use
1050
them in preference to ad-hoc solutions as they provide portability and
1051
performance benefits.
1056
The ``TreeBuilder`` interface allows the construction of arbitrary trees
1057
with a declarative interface. A sample session might look like::
1059
tree = self.make_branch_and_tree('path')
1060
builder = TreeBuilder()
1061
builder.start_tree(tree)
1062
builder.build(['foo', "bar/", "bar/file"])
1063
tree.commit('commit the tree')
1064
builder.finish_tree()
1066
Please see bzrlib.treebuilder for more details.
1071
The ``BranchBuilder`` interface allows the creation of test branches in a
1072
quick and easy manner. A sample session::
1074
builder = BranchBuilder(self.get_transport().clone('relpath'))
1075
builder.build_commit()
1076
builder.build_commit()
1077
builder.build_commit()
1078
branch = builder.get_branch()
1080
Please see bzrlib.branchbuilder for more details.
1085
We make selective use of doctests__. In general they should provide
1086
*examples* within the API documentation which can incidentally be tested. We
1087
don't try to test every important case using doctests -- regular Python
1088
tests are generally a better solution.
1090
Most of these are in ``bzrlib/doc/api``. More additions are welcome.
1092
__ http://docs.python.org/lib/module-doctest.html
1097
Currently, bzr selftest is used to invoke tests.
1098
You can provide a pattern argument to run a subset. For example,
1099
to run just the blackbox tests, run::
1101
./bzr selftest -v blackbox
1103
To skip a particular test (or set of tests), use the --exclude option
1104
(shorthand -x) like so::
1106
./bzr selftest -v -x blackbox
1108
To list tests without running them, use the --list-only option like so::
1110
./bzr selftest --list-only
1112
This option can be combined with other selftest options (like -x) and
1113
filter patterns to understand their effect.
1116
Handling Errors and Exceptions
1117
==============================
1119
Commands should return non-zero when they encounter circumstances that
1120
the user should really pay attention to - which includes trivial shell
1123
Recommended values are:
1126
1. Conflicts in merge-like operations, or changes are present in
1127
diff-like operations.
1128
2. Unrepresentable diff changes (i.e. binary files that we cannot show
1130
3. An error or exception has occurred.
1131
4. An internal error occurred (one that shows a traceback.)
1133
Errors are handled through Python exceptions. Exceptions should be defined
1134
inside bzrlib.errors, so that we can see the whole tree at a glance.
1136
We broadly classify errors as either being either internal or not,
1137
depending on whether ``internal_error`` is set or not. If we think it's our
1138
fault, we show a backtrace, an invitation to report the bug, and possibly
1139
other details. This is the default for errors that aren't specifically
1140
recognized as being caused by a user error. Otherwise we show a briefer
1141
message, unless -Derror was given.
1143
Many errors originate as "environmental errors" which are raised by Python
1144
or builtin libraries -- for example IOError. These are treated as being
1145
our fault, unless they're caught in a particular tight scope where we know
1146
that they indicate a user errors. For example if the repository format
1147
is not found, the user probably gave the wrong path or URL. But if one of
1148
the files inside the repository is not found, then it's our fault --
1149
either there's a bug in bzr, or something complicated has gone wrong in
1150
the environment that means one internal file was deleted.
1152
Many errors are defined in ``bzrlib/errors.py`` but it's OK for new errors
1153
to be added near the place where they are used.
1155
Exceptions are formatted for the user by conversion to a string
1156
(eventually calling their ``__str__`` method.) As a convenience the
1157
``._fmt`` member can be used as a template which will be mapped to the
1158
error's instance dict.
1160
New exception classes should be defined when callers might want to catch
1161
that exception specifically, or when it needs a substantially different
1164
Exception strings should start with a capital letter and should not have a
1165
final fullstop. If long, they may contain newlines to break the text.
1171
When you change bzrlib, please update the relevant documentation for the
1172
change you made: Changes to commands should update their help, and
1173
possibly end user tutorials; changes to the core library should be
1174
reflected in API documentation.
1179
If you make a user-visible change, please add a note to the NEWS file.
1180
The description should be written to make sense to someone who's just
1181
a user of bzr, not a developer: new functions or classes shouldn't be
1182
mentioned, but new commands, changes in behaviour or fixed nontrivial
1183
bugs should be listed. See the existing entries for an idea of what
1186
Within each release, entries in the news file should have the most
1187
user-visible changes first. So the order should be approximately:
1189
* changes to existing behaviour - the highest priority because the
1190
user's existing knowledge is incorrect
1191
* new features - should be brought to their attention
1192
* bug fixes - may be of interest if the bug was affecting them, and
1193
should include the bug number if any
1194
* major documentation changes
1195
* changes to internal interfaces
1197
People who made significant contributions to each change are listed in
1198
parenthesis. This can include reporting bugs (particularly with good
1199
details or reproduction recipes), submitting patches, etc.
1204
The docstring of a command is used by ``bzr help`` to generate help output
1205
for the command. The list 'takes_options' attribute on a command is used by
1206
``bzr help`` to document the options for the command - the command
1207
docstring does not need to document them. Finally, the '_see_also'
1208
attribute on a command can be used to reference other related help topics.
1213
Functions, methods, classes and modules should have docstrings
1214
describing how they are used.
1216
The first line of the docstring should be a self-contained sentence.
1218
For the special case of Command classes, this acts as the user-visible
1219
documentation shown by the help command.
1221
The docstrings should be formatted as reStructuredText_ (like this
1222
document), suitable for processing using the epydoc_ tool into HTML
1225
.. _reStructuredText: http://docutils.sourceforge.net/rst.html
1226
.. _epydoc: http://epydoc.sourceforge.net/
368
1229
General Guidelines
632
1498
how to set it up and configure it.
1504
Setting Up Your Workspace for Reviews
1505
-------------------------------------
1507
TODO: Incorporate John Arbash Meinel's detailed email to Ian C on the
1508
numerous ways of setting up integration branches.
1511
The Review Checklist
1512
--------------------
1514
See `A Closer Look at the Merge & Review Process`_
1515
for information on the gates used to decide whether code can be merged
1516
or not and details on how review results are recorded and communicated.
1519
The Importance of Timely Reviews
1520
--------------------------------
1522
Good reviews do take time. They also regularly require a solid
1523
understanding of the overall code base. In practice, this means a small
1524
number of people often have a large review burden - with knowledge comes
1525
responsibility. No one like their merge requests sitting in a queue going
1526
nowhere, so reviewing sooner rather than later is strongly encouraged.
1535
Of the many workflows supported by Bazaar, the one adopted for Bazaar
1536
development itself is known as "Decentralized with automatic gatekeeper".
1537
To repeat the explanation of this given on
1538
http://bazaar-vcs.org/Workflows:
1541
In this workflow, each developer has their own branch or
1542
branches, plus read-only access to the mainline. A software gatekeeper
1543
(e.g. PQM) has commit rights to the main branch. When a developer wants
1544
their work merged, they request the gatekeeper to merge it. The gatekeeper
1545
does a merge, a compile, and runs the test suite. If the code passes, it
1546
is merged into the mainline.
1548
In a nutshell, here's the overall submission process:
1550
#. get your work ready (including review except for trivial changes)
1551
#. push to a public location
1552
#. ask PQM to merge from that location
1555
At present, PQM always takes the changes to merge from a branch
1556
at a URL that can be read by it. For Bazaar, that means a public,
1557
typically http, URL.
1559
As a result, the following things are needed to use PQM for submissions:
1561
#. A publicly available web server
1562
#. Your OpenPGP key registered with PQM (contact RobertCollins for this)
1563
#. The PQM plugin installed and configured (not strictly required but
1564
highly recommended).
1567
Selecting a Public Branch Location
1568
----------------------------------
1570
If you don't have your own web server running, branches can always be
1571
pushed to Launchpad. Here's the process for doing that:
1573
Depending on your location throughout the world and the size of your
1574
repository though, it is often quicker to use an alternative public
1575
location to Launchpad, particularly if you can set up your own repo and
1576
push into that. By using an existing repo, push only needs to send the
1577
changes, instead of the complete repository every time. Note that it is
1578
easy to register branches in other locations with Launchpad so no benefits
1579
are lost by going this way.
1582
For Canonical staff, http://people.ubuntu.com/~<user>/ is one
1583
suggestion for public http branches. Contact your manager for information
1584
on accessing this system if required.
1586
It should also be noted that best practice in this area is subject to
1587
change as things evolve. For example, once the Bazaar smart server on
1588
Launchpad supports server-side branching, the performance situation will
1589
be very different to what it is now (Jun 2007).
1592
Configuring the PQM Plug-In
1593
---------------------------
1595
While not strictly required, the PQM plugin automates a few things and
1596
reduces the chance of error. Before looking at the plugin, it helps to
1597
understand a little more how PQM operates. Basically, PQM requires an
1598
email indicating what you want it to do. The email typically looks like
1601
star-merge source-branch target-branch
1605
star-merge http://bzr.arbash-meinel.com/branches/bzr/jam-integration http://bazaar-vcs.org/bzr/bzr.dev
1607
Note that the command needs to be on one line. The subject of the email
1608
will be used for the commit message. The email also needs to be ``gpg``
1609
signed with a key that PQM accepts.
1611
The advantages of using the PQM plugin are:
1613
#. You can use the config policies to make it easy to set up public
1614
branches, so you don't have to ever type the full paths you want to merge
1617
#. It checks to make sure the public branch last revision matches the
1618
local last revision so you are submitting what you think you are.
1620
#. It uses the same public_branch and smtp sending settings as bzr-email,
1621
so if you have one set up, you have the other mostly set up.
1623
#. Thunderbird refuses to not wrap lines, and request lines are usually
1624
pretty long (you have 2 long URLs in there).
1626
Here are sample configuration settings for the PQM plugin. Here are the
1627
lines in bazaar.conf::
1630
email = Joe Smith <joe.smith@internode.on.net>
1631
smtp_server=mail.internode.on.net:25
1633
And here are the lines in ``locations.conf`` (or ``branch.conf`` for
1634
dirstate-tags branches)::
1636
[/home/joe/bzr/my-integration]
1637
push_location = sftp://joe-smith@bazaar.launchpad.net/%7Ejoe-smith/bzr/my-integration/
1638
push_location:policy = norecurse
1639
public_branch = http://bazaar.launchpad.net/~joe-smith/bzr/my-integration/
1640
public_branch:policy = appendpath
1641
pqm_email = Bazaar PQM <pqm@bazaar-vcs.org>
1642
pqm_branch = http://bazaar-vcs.org/bzr/bzr.dev
1644
Note that the push settings will be added by the first ``push`` on
1645
a branch. Indeed the preferred way to generate the lines above is to use
1646
``push`` with an argument, then copy-and-paste the other lines into
1653
Here is one possible recipe once the above environment is set up:
1655
#. pull bzr.dev => my-integration
1656
#. merge patch => my-integration
1657
#. fix up any final merge conflicts (NEWS being the big killer here).
1663
The ``push`` step is not required if ``my-integration`` is a checkout of
1666
Because of defaults, you can type a single message into commit and
1667
pqm-commit will reuse that.
1670
Tracking Change Acceptance
1671
--------------------------
1673
The web interface to PQM is https://pqm.bazaar-vcs.org/. After submitting
1674
a change, you can visit this URL to confirm it was received and placed in
1677
When PQM completes processing a change, an email is sent to you with the
1681
Reviewing Blueprints
1682
====================
1684
Blueprint Tracking Using Launchpad
1685
----------------------------------
1687
New features typically require a fair amount of discussion, design and
1688
debate. For Bazaar, that information is often captured in a so-called
1689
"blueprint" on our Wiki. Overall tracking of blueprints and their status
1690
is done using Launchpad's relevant tracker,
1691
https://blueprints.launchpad.net/bzr/. Once a blueprint for ready for
1692
review, please announce it on the mailing list.
1694
Alternatively, send an email begining with [RFC] with the proposal to the
1695
list. In some cases, you may wish to attach proposed code or a proposed
1696
developer document if that best communicates the idea. Debate can then
1697
proceed using the normal merge review processes.
1700
Recording Blueprint Review Feedback
1701
-----------------------------------
1703
Unlike its Bug Tracker, Launchpad's Blueprint Tracker doesn't currently
1704
(Jun 2007) support a chronological list of comment responses. Review
1705
feedback can either be recorded on the Wiki hosting the blueprints or by
1706
using Launchpad's whiteboard feature.
636
1709
Planning Releases
637
1710
=================
1715
As the two senior developers, Martin Pool and Robert Collins coordinate
1716
the overall Bazaar product development roadmap. Core developers provide
1717
input and review into this, particularly during sprints. It's totally
1718
expected that community members ought to be working on things that
1719
interest them the most. The roadmap is valuable though because it provides
1720
context for understanding where the product is going as a whole and why.
1723
Using Releases and Milestones in Launchpad
1724
------------------------------------------
1726
TODO ... (Exact policies still under discussion)
added
removed
doc/developers/HACKING.txt
