4 >The CVS Repository</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.60"><LINK
9 TITLE="Privoxy Developer Manual"
10 HREF="index.html"><LINK
13 HREF="introduction.html"><LINK
15 TITLE="Documentation Guidelines"
16 HREF="documentation.html"><LINK
19 HREF="../p_doc.css"></HEAD
38 >Privoxy Developer Manual</TH
46 HREF="introduction.html"
59 HREF="documentation.html"
73 >2. The CVS Repository</A
76 > If you intend to help us with programming, documentation or packaging
77 you will need write access to our holy grail, the CVS repository.
78 Please read this chapter completely before accessing via CVS.
86 >2.1. Access to CVS</A
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
123 >2.2. CVS Commit Guideline</A
126 > The source tree is the heart of every software project. Every effort must
127 be made to ensure that it is readable, compilable and consistent at all
128 times. We therefore ask anyone with CVS access to strictly adhere to the
129 following guidelines:
138 >) be tempted to commit
139 that small change without testing it thoroughly first. When we're
140 close to a public release, ask a fellow developer to review your
146 > Your commit message should give a concise overview of <I
150 > (no big details) and <I
152 >why you changed it</I
154 Just check previous messages for good examples.
159 > Don't use the same message on multiple files, unless it equally applies to
165 > If your changes span multiple files, and the code won't recompile unless
166 all changes are committed (e.g. when changing the signature of a function),
167 then commit all files one after another, without long delays in between.
168 If necessary, prepare the commit messages in advance.
173 > Before changing things on CVS, make sure that your changes are in line
174 with the team's general consensus on what should be done (see below).
179 > Don't commit into the stable branch, unless immediately before a new
181 HREF="newrelease.html#VERSIONNUMBERS"
184 for details.) Collect your changes on the <A
185 HREF="http://sourceforge.net/tracker/?atid=311118&group_id=11118&func=browse"
202 >2.3. Discussing Changes First</A
205 > We don't have a too formal policy on this, just use common sense. Hints: If it is..
212 > ..a bug-fix / clean-up / cosmetic thing: shoot
217 > ..a new feature that can be turned off: shoot
222 > ..a clear improvement w/o side effects on other parts of the code: shoot
227 > ..a matter of taste: <A
228 HREF="mailto:developers@privoxy.org"
236 > ..a major redesign of some part of the code: <A
237 HREF="mailto:developers@privoxy.org"
248 > Note that near a major public release, we get a bit more cautious - if
249 unsure, it doesn't hurt to ask first. There is always the possibility
250 to submit a patch to the <A
251 HREF="http://sourceforge.net/tracker/?atid=311118&group_id=11118&func=browse"
274 HREF="introduction.html"
290 HREF="documentation.html"
309 >Documentation Guidelines</TD