1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5 >The CVS Repository</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10 TITLE="Privoxy Developer Manual"
11 HREF="index.html"><LINK
14 HREF="introduction.html"><LINK
16 TITLE="Documentation Guidelines"
17 HREF="documentation.html"><LINK
20 HREF="../p_doc.css"></HEAD
31 SUMMARY="Header navigation table"
40 >Privoxy Developer Manual</TH
48 HREF="introduction.html"
62 HREF="documentation.html"
77 >2. The CVS Repository</A
80 > If you become part of the active development team, you will eventually
81 need write access to our holy grail, the CVS repository. One of the
82 team members will need to set this up for you. Please read
83 this chapter completely before accessing via CVS.
91 >2.1. Access to CVS</A
94 > The project's CVS repository is hosted on
96 HREF="http://sourceforge.net/"
100 Please refer to the chapters 6 and 7 in
102 HREF="http://sourceforge.net/docman/?group_id=1"
106 > for the technical access details for your
107 operating system. For historical reasons, the CVS server is
110 >ijbswa.cvs.sourceforge.net</TT
115 >, and the source tree module is called
131 > Within the CVS repository, there are modules and branches. As
132 mentioned, the sources are in the <TT
139 >. Other modules are present for platform specific
140 issues. There is a webview of the CVS hierarchy at <A
141 HREF="http://ijbswa.cvs.sourceforge.net/ijbswa/"
143 >http://ijbswa.cvs.sourceforge.net/ijbswa/</A
145 which might help with visualizing how these pieces fit together.
148 > Branches are used to fork a sub-development path from the main trunk.
152 > module where the sources are, there
153 is always at least one <SPAN
156 > from the main trunk
157 devoted to a stable release series. The main trunk is where active
158 development takes place for the next stable series (e.g. 3.2.x).
159 So just prior to each stable series (e.g. 3.0.x), a branch is created
160 just for stable series releases (e.g. 3.0.0 -> 3.0.1 -> 3.0.2, etc).
161 Once the initial stable release of any stable branch has taken place,
166 >only used for bugfixes</I
169 had prior testing before being committed to CVS. (See <A
170 HREF="newrelease.html#VERSIONNUMBERS"
172 > below for details on
176 > At one time there were two distinct branches: stable and unstable. The
177 more drastic changes were to be in the unstable branch. These branches
178 have now been merged to minimize time and effort of maintaining two
188 >2.3. CVS Commit Guidelines</A
191 > The source tree is the heart of every software project. Every effort must
192 be made to ensure that it is readable, compilable and consistent at all
193 times. There are differing guidelines for the stable branch and the
194 main development trunk, and we ask anyone with CVS access to strictly
195 adhere to the following guidelines:
198 > Basic Guidelines, for all branches:
206 > Please don't commit even
207 a small change without testing it thoroughly first. When we're
208 close to a public release, ask a fellow developer to review your
214 > Your commit message should give a concise overview of <SPAN
221 > (no big details) and <SPAN
225 >why you changed it</I
228 Just check previous messages for good examples.
233 > Don't use the same message on multiple files, unless it equally applies to
239 > If your changes span multiple files, and the code won't recompile unless
240 all changes are committed (e.g. when changing the signature of a function),
241 then commit all files one after another, without long delays in between.
242 If necessary, prepare the commit messages in advance.
247 > Before changing things on CVS, make sure that your changes are in line
248 with the team's general consensus on what should be done.
253 > Note that near a major public release, we get more cautious.
254 There is always the possibility to submit a patch to the <A
255 HREF="http://sourceforge.net/tracker/?atid=311118&group_id=11118&func=browse"
272 SUMMARY="Footer navigation table"
283 HREF="introduction.html"
301 HREF="documentation.html"
321 >Documentation Guidelines</TD