<html>
<head>
- <meta name="generator" content=
- "HTML Tidy for Linux/x86 (vers 7 December 2008), see www.w3.org">
-
<title>The CVS Repository</title>
<meta name="GENERATOR" content=
"Modular DocBook HTML Stylesheet Version 1.79">
"documentation.html">
<link rel="STYLESHEET" type="text/css" href="../p_doc.css">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
- <style type="text/css">
-body {
- background-color: #EEEEEE;
- color: #000000;
- }
- :link { color: #0000FF }
- :visited { color: #840084 }
- :active { color: #0000FF }
- span.c2 {font-style: italic}
- hr.c1 {text-align: left}
- </style>
</head>
-<body class="SECT1">
+<body class="SECT1" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink=
+"#840084" alink="#0000FF">
<div class="NAVHEADER">
<table summary="Header navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
"documentation.html" accesskey="N">Next</a></td>
</tr>
</table>
- <hr class="c1" width="100%">
+ <hr align="left" width="100%">
</div>
<div class="SECT1">
"_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 EMPHASIS c2">only used for bugfixes</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>
<li>
<p>Your commit message should give a concise overview of
- <span class="emphasis EMPHASIS c2">what you changed</span> (no big
- details) and <span class="emphasis EMPHASIS c2">why you changed
- it</span> Just check previous messages for good examples.</p>
+ <span class="emphasis"><i class="EMPHASIS">what you
+ changed</i></span> (no big details) and <span class=
+ "emphasis"><i class="EMPHASIS">why you changed it</i></span> Just
+ check previous messages for good examples.</p>
</li>
<li>
</div>
<div class="NAVFOOTER">
- <hr class="c1" width="100%">
+ <hr align="left" width="100%">
<table summary="Footer navigation table" width="100%" border="0"
cellpadding="0" cellspacing="0">
projects / privoxy.git / blobdiff