"_top">http://ijbswa.cvs.sourceforge.net/ijbswa/</a>, which might help
with visualizing how these pieces fit together.</p>
- <p>Branches are used to fork a sub-development path from the main
- trunk. Within the <tt class="LITERAL">current</tt> module where the
- sources are, there is always at least one <span class=
- "QUOTE">"branch"</span> from the main trunk devoted to a stable release
- series. The main trunk is where active development takes place for the
- next stable series (e.g. 3.2.x). So just prior to each stable series
- (e.g. 3.0.x), a branch is created just for stable series releases (e.g.
- 3.0.0 -> 3.0.1 -> 3.0.2, etc). Once the initial stable release of
- any stable branch has taken place, this branch is <span class=
- "emphasis"><i class="EMPHASIS">only used for bugfixes</i></span>, which
- have had prior testing before being committed to CVS. (See <a href=
- "newrelease.html#VERSIONNUMBERS">Version Numbers</a> below for details
- on versioning.)</p>
-
<p>At one time there were two distinct branches: stable and unstable.
The more drastic changes were to be in the unstable branch. These
branches have now been merged to minimize time and effort of
<p>The source tree is the heart of every software project. Every effort
must be made to ensure that it is readable, compilable and consistent
- at all times. There are differing guidelines for the stable branch and
- the main development trunk, and we ask anyone with CVS access to
- strictly adhere to the following guidelines:</p>
+ at all times. We expect anyone with CVS access to strictly adhere to
+ the following guidelines:</p>
<p>Basic Guidelines, for all branches:</p>
projects / privoxy.git / blobdiff