7
Breezy is a tool for helping people collaborate. It tracks the changes
7
Bazaar is a tool for helping people collaborate. It tracks the changes
8
8
that you and other people make to a group of files - such as software
9
9
source code - to give you snapshots of each stage of their evolution.
10
Using that information, Breezy can effortlessly merge your work with
10
Using that information, Bazaar can effortlessly merge your work with
13
Tools like Breezy are called version control systems (VCS) and have
14
long been popular with software developers. Breezy's ease of use,
13
Tools like Bazaar are called version control systems (VCS) and have
14
long been popular with software developers. Bazaar's ease of use,
15
15
flexibility and simple setup make it ideal not only for software
16
16
developers but also for other groups who work together on files and
17
17
documents, such as technical writers, web designers and translators.
19
This guide takes you through installing Breezy and how to use it,
19
This guide takes you through installing Bazaar and how to use it,
20
20
whether on your own or with a team of other people. If you're already
21
21
familiar with distributed version control and want to dive straight in,
22
22
you may wish to skim this section and jump straight to
31
31
1. file versioning tools, e.g. SCCS, RCS
32
32
2. tree versioning tools - central style, e.g. CVS
33
33
3. tree versioning tools - central style, take two, e.g. Subversion
34
4. tree versioning tools - distributed style, e.g. Breezy.
34
4. tree versioning tools - distributed style, e.g. Bazaar.
36
The design and implementation of Breezy builds on the lessons learned
37
from all the previous generations of tools. In particular, Breezy
36
The design and implementation of Bazaar builds on the lessons learned
37
from all the previous generations of tools. In particular, Bazaar
38
38
cleanly supports both the central and the distributed version
39
39
control models so you can change models as it makes sense, without
40
40
needing to change tools.
59
59
it has a negative influence on quality in others.
61
61
Distributed VCS tools let users and teams have multiple repositories
62
rather than just a single central one. In Breezy's case, the history is
62
rather than just a single central one. In Bazaar's case, the history is
63
63
normally kept in the same place as the code that is being version controlled.
64
64
This allows the user to commit their changes whenever it makes sense, even
65
65
when offline. Network access is only required when publishing changes or
92
92
centralized VCS tools, see http://wiki.bazaar.canonical.com/BzrWhy.
95
Key features of Breezy
95
Key features of Bazaar
96
96
----------------------
98
While Breezy is not the only distributed VCS tool around, it does have some
98
While Bazaar is not the only distributed VCS tool around, it does have some
99
99
notable features that make it an excellent choice for many teams and
100
100
communities. A summary of these and comparisons with other VCS tools
101
can be found on the Breezy Wiki, http://wiki.bazaar.canonical.com.
101
can be found on the Bazaar Wiki, http://wiki.bazaar.canonical.com.
103
103
Of the many features, one in particular is worth highlighting:
104
Breezy is completely free software written in Python. As a result,
104
Bazaar is completely free software written in Python. As a result,
105
105
it is easy to contribute improvements. If you wish to get involved,
106
106
please see http://wiki.bazaar.canonical.com/BzrSupport.
112
This manual provides an easy to read introduction to Breezy and how to use
112
This manual provides an easy to read introduction to Bazaar and how to use
113
113
it effectively. It is recommended that all users read at least the rest of
114
114
this chapter as it:
116
116
* explains the core concepts users need to know
117
* introduces some popular ways of using Breezy to collaborate.
117
* introduces some popular ways of using Bazaar to collaborate.
119
Chapters 2-6 provide a closer look at how to use Breezy to complete
119
Chapters 2-6 provide a closer look at how to use Bazaar to complete
120
120
various tasks. It is recommended that most users read these in first-to-last
121
order shortly after starting to use Breezy. Chapter 7 and beyond provide
122
additional information that helps you make the most of Breezy once the core
121
order shortly after starting to use Bazaar. Chapter 7 and beyond provide
122
additional information that helps you make the most of Bazaar once the core
123
123
functionality is understood. This material can be read when required and in
126
126
If you are already familiar with other version control tools,
127
127
you may wish to get started quickly by reading the following documents:
129
* `Breezy in five minutes`_ - a mini-tutorial
131
* `Breezy Quick Start Card`_ - a one page summary of commonly used commands.
133
In addition, the online help and `Breezy User Reference`_ provide all the
129
* `Bazaar in five minutes`_ - a mini-tutorial
131
* `Bazaar Quick Start Card`_ - a one page summary of commonly used commands.
133
In addition, the online help and `Bazaar User Reference`_ provide all the
134
134
details on the commands and options available.
136
.. _Breezy in five minutes: ../mini-tutorial/index.html
137
.. _Breezy Quick Start Card: ../quick-reference/index.html
138
.. _Breezy User Reference: ../user-reference/index.html
136
.. _Bazaar in five minutes: ../mini-tutorial/index.html
137
.. _Bazaar Quick Start Card: ../quick-reference/index.html
138
.. _Bazaar User Reference: ../user-reference/index.html
140
140
We hope you find this manual useful. If you have suggestions on how it
141
or the rest of Breezy's documentation can be improved, please contact
141
or the rest of Bazaar's documentation can be improved, please contact
142
142
us on the mailing list, bazaar@lists.canonical.com.