4 >The CVS Repository</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
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"
76 NAME="CVS">2. The CVS Repository</H1
78 > If you intend to help us with programming, documentation or packaging
79 you will need write access to our holy grail, the CVS repository.
80 Please read this chapter completely before accessing via CVS.
87 NAME="CVSACCESS">2.1. Access to CVS</H2
89 > The project's CVS repository is hosted on
91 HREF="http://sourceforge.net/"
95 Please refer to the chapters 6 and 7 in
97 HREF="http://sourceforge.net/docman/?group_id=1"
101 > for the technical access details for your
102 operating system. For historical reasons, the CVS server is
105 >cvs.ijbswa.sourceforge.net</TT
110 >, and the source tree module is called
122 NAME="CVSCOMMIT">2.2. CVS Commit Guideline</H2
124 > The source tree is the heart of every software project. Every effort must
125 be made to ensure that it is readable, compilable and consistent at all
126 times. We therefore ask anyone with CVS access to strictly adhere to the
127 following guidelines:
139 >) be tempted to commit
140 that small change without testing it thoroughly first. When we're
141 close to a public release, ask a fellow developer to review your
147 > Your commit message should give a concise overview of <SPAN
154 > (no big details) and <SPAN
158 >why you changed it</I
161 Just check previous messages for good examples.
166 > Don't use the same message on multiple files, unless it equally applies to
172 > If your changes span multiple files, and the code won't recompile unless
173 all changes are committed (e.g. when changing the signature of a function),
174 then commit all files one after another, without long delays in between.
175 If necessary, prepare the commit messages in advance.
180 > Before changing things on CVS, make sure that your changes are in line
181 with the team's general consensus on what should be done (see below).
186 > Don't commit into the stable branch, unless immediately before a new
188 HREF="newrelease.html#VERSIONNUMBERS"
191 for details.) Collect your changes on the <A
192 HREF="http://sourceforge.net/tracker/?atid=311118&group_id=11118&func=browse"
208 NAME="CVSWHENASK">2.3. Discussing Changes First</H2
210 > We don't have a too formal policy on this, just use common sense. Hints: If it is..
217 > ..a bug-fix / clean-up / cosmetic thing: shoot
222 > ..a new feature that can be turned off: shoot
227 > ..a clear improvement w/o side effects on other parts of the code: shoot
232 > ..a matter of taste: <A
233 HREF="mailto:developers@privoxy.org"
241 > ..a major redesign of some part of the code: <A
242 HREF="mailto:developers@privoxy.org"
253 > Note that near a major public release, we get a bit more cautious - if
254 unsure, it doesn't hurt to ask first. There is always the possibility
255 to submit a patch to the <A
256 HREF="http://sourceforge.net/tracker/?atid=311118&group_id=11118&func=browse"
269 SUMMARY="Footer navigation table"
280 HREF="introduction.html"
298 HREF="documentation.html"
318 >Documentation Guidelines</TD