Author: upayavira Date: Tue Dec 14 14:07:59 2004 New Revision: 111887 URL: http://svn.apache.org/viewcvs?view=rev&rev=111887 Log: Update references to CVS-->SVN in site module. 2.1.X doc refs to come... Modified: cocoon/site/src/documentation/content/xdocs/community/committer.xml cocoon/site/src/documentation/content/xdocs/community/contrib.xml cocoon/site/src/documentation/content/xdocs/community/mail-lists.xml cocoon/site/src/documentation/content/xdocs/community/members.xml cocoon/site/src/documentation/content/xdocs/devinfo/releasing.xml cocoon/site/src/documentation/content/xdocs/guidelines.xml
Modified: cocoon/site/src/documentation/content/xdocs/community/committer.xml Url: http://svn.apache.org/viewcvs/cocoon/site/src/documentation/content/xdocs/community/committer.xml?view=diff&rev=111887&p1=cocoon/site/src/documentation/content/xdocs/community/committer.xml&r1=111886&p2=cocoon/site/src/documentation/content/xdocs/community/committer.xml&r2=111887 ============================================================================== --- cocoon/site/src/documentation/content/xdocs/community/committer.xml (original) +++ cocoon/site/src/documentation/content/xdocs/community/committer.xml Tue Dec 14 14:07:59 2004 @@ -9,7 +9,7 @@ <section id="overview"> <title>Overview</title> <p> - These are some tips to help committers to keep our CVS clean. + These are some tips to help committers to keep our Subversion (SVN) repository clean. See also <link href="http://www.apache.org/dev/committers.html";>Committers FAQ</link> and @@ -31,17 +31,17 @@ <section id="whitespace"> <title>Consistent whitespace</title> <p> - Whitespace can cause big problems with CVS. If it is inconsistent, + Whitespace can cause big problems with SVN. If it is inconsistent, then diffs are very hard to follow - actual changes become lost in the noise of whitespace changes. Some developers use editors that attempt to automatically format the whitespace. The trouble is - that if CVS files are inconsistent, some of those editors just + that if SVN files are inconsistent, some of those editors just make it worse. </p> <p> The solution is that some committers who have a proper editor - should occasionally correct the whitespace across all CVS files, + should occasionally correct the whitespace across all SVN files, applying the following rules. </p> @@ -75,7 +75,7 @@ <p> If you are on a UNIX system, when you receive a patch from a contributor on Windows then do a 'dos2unix'. If you are on a - Windows system, then ensure that you have a proper CVS client + Windows system, then ensure that you have a proper SVN client (it is supposed to convert to UNIX line-endings when you commit). </p> @@ -90,7 +90,7 @@ find . -type f | xargs grep -l '^M' | xargs file | \ grep -i -w text | cut -f1 -d: -To add the ^M use "Ctrl-v Ctrl-m" at the command-line. +To add the ^M use " Ctrl-v Ctrl-m" at the command-line. Note that copy-and-paste will not work. The -w can be omitted, but might then match some extra filenames. ]]></source> Modified: cocoon/site/src/documentation/content/xdocs/community/contrib.xml Url: http://svn.apache.org/viewcvs/cocoon/site/src/documentation/content/xdocs/community/contrib.xml?view=diff&rev=111887&p1=cocoon/site/src/documentation/content/xdocs/community/contrib.xml&r1=111886&p2=cocoon/site/src/documentation/content/xdocs/community/contrib.xml&r2=111887 ============================================================================== --- cocoon/site/src/documentation/content/xdocs/community/contrib.xml (original) +++ cocoon/site/src/documentation/content/xdocs/community/contrib.xml Tue Dec 14 14:07:59 2004 @@ -35,8 +35,9 @@ </p> <p>You can get your local working copy of the - <link href="http://svn.apache.org/viewcvs.cgi/cocoon/branches/BRANCH_2_1_X";>release branch</link> (which you find in the cocoon-2.1 module in - the svn.apache.org code repository). + <link href="http://svn.apache.org/viewcvs.cgi/cocoon/branches/BRANCH_2_1_X/";>current release branch</link>, + or the <link href="http://svn.apache.org/viewcvs.cgi/cocoon/trunk/";>latest development branch</link> + from Subversion (SVN). Review the <link href="http://cocoon.apache.org/2.1/todo.html";>todo</link> list, choose a task (or perhaps you have noticed something that needs patching). Make the changes, do the testing, generate a patch, if you need then discuss it on @@ -166,15 +167,16 @@ conditions</strong> - like most open source projects, we do not have the resources nor the inclination to obtain signed statements from all contributors!</p> - + <!-- WE DON'T HAVE A CONTRIB DIRECTORY. DO WE NEED THIS NOW? UV <p><strong>Note:</strong> Since the <code>contrib/</code> directory of Cocoon CVS contains third-party. completely optional extensions, one of the above requirements is relaxed. Code in the contrib directory does not have to have its copyright assigned to the ASF - but it must still be released under the Apache license.</p> + --> </s2> </s1> - <anchor id="cvshowto"/> + <anchor id="svnhowto"/> <s1 title="Subversion Usage Precis"> <p>An overview of how to use Subversion to participate in Cocoon development. Do not be afraid - you cannot accidently destroy the actual code repository, Modified: cocoon/site/src/documentation/content/xdocs/community/mail-lists.xml Url: http://svn.apache.org/viewcvs/cocoon/site/src/documentation/content/xdocs/community/mail-lists.xml?view=diff&rev=111887&p1=cocoon/site/src/documentation/content/xdocs/community/mail-lists.xml&r1=111886&p2=cocoon/site/src/documentation/content/xdocs/community/mail-lists.xml&r2=111887 ============================================================================== --- cocoon/site/src/documentation/content/xdocs/community/mail-lists.xml (original) +++ cocoon/site/src/documentation/content/xdocs/community/mail-lists.xml Tue Dec 14 14:07:59 2004 @@ -189,12 +189,13 @@ </p> <p>This <strong>read-only</strong> list sends out notification messages detailing - any change made to the CVS repository where all the source code and libraries + any change made to the Subversion (SVN) repository where all the source code and libraries are stored for development purposes. The average user probably doesn't need to - subscribe to this list.</p> + subscribe to this list. (It is named CVS due to the fact that Cocoon previously used + CVS as its repository.)</p> <note>You should never post to this list at all. Only the - CVS server should post to it.</note> + SVN server should post to it.</note> </s1> Modified: cocoon/site/src/documentation/content/xdocs/community/members.xml Url: http://svn.apache.org/viewcvs/cocoon/site/src/documentation/content/xdocs/community/members.xml?view=diff&rev=111887&p1=cocoon/site/src/documentation/content/xdocs/community/members.xml&r1=111886&p2=cocoon/site/src/documentation/content/xdocs/community/members.xml&r2=111887 ============================================================================== --- cocoon/site/src/documentation/content/xdocs/community/members.xml (original) +++ cocoon/site/src/documentation/content/xdocs/community/members.xml Tue Dec 14 14:07:59 2004 @@ -86,6 +86,7 @@ <li>Jeff Turner (jefft.at.apache.org)</li> <li>Sylvain Wallez (sylvain.at.apache.org)</li> <li>Carsten Ziegeler (cziegeler.at.apache.org)</li> + <li>Upayavira (upayavira.at.apache.org)</li> </ul> </section> Modified: cocoon/site/src/documentation/content/xdocs/devinfo/releasing.xml Url: http://svn.apache.org/viewcvs/cocoon/site/src/documentation/content/xdocs/devinfo/releasing.xml?view=diff&rev=111887&p1=cocoon/site/src/documentation/content/xdocs/devinfo/releasing.xml&r1=111886&p2=cocoon/site/src/documentation/content/xdocs/devinfo/releasing.xml&r2=111887 ============================================================================== --- cocoon/site/src/documentation/content/xdocs/devinfo/releasing.xml (original) +++ cocoon/site/src/documentation/content/xdocs/devinfo/releasing.xml Tue Dec 14 14:07:59 2004 @@ -85,13 +85,13 @@ noone will check in during the release process. If someone checks in during the building, testing and tagging, the release process has to be started at the beginning again. Otherwise the release version is - not the one tagged in CVS. + not the one tagged in Subversion. </p> </section> <section> <title>Get the Version</title> <p> - Check-out a fresh copy from the cvs on a unix platform (this is important, + Check-out a fresh copy from Subversion on a unix platform (this is important, do not use windows!) </p> </section> @@ -147,7 +147,7 @@ <section> <title>Continuing the Release Process</title> <p> - Now check-in the changed version from the first step and tag the release in cvs. + Now check-in the changed version from the first step and tag the release in Subversion. Currently three files should have been changed in the last steps: </p> <ul> Modified: cocoon/site/src/documentation/content/xdocs/guidelines.xml Url: http://svn.apache.org/viewcvs/cocoon/site/src/documentation/content/xdocs/guidelines.xml?view=diff&rev=111887&p1=cocoon/site/src/documentation/content/xdocs/guidelines.xml&r1=111886&p2=cocoon/site/src/documentation/content/xdocs/guidelines.xml&r2=111887 ============================================================================== --- cocoon/site/src/documentation/content/xdocs/guidelines.xml (original) +++ cocoon/site/src/documentation/content/xdocs/guidelines.xml Tue Dec 14 14:07:59 2004 @@ -166,7 +166,7 @@ <section> <title>CVS Commit Lists</title> - <p>The cvs list is where all CVS code commit messages are + <p>The cvs list is where all Subversion (SVN) code commit messages are automatically sent. All committers are required to subscribe to this list so that they can stay aware of changes to the repository.</p> @@ -527,9 +527,9 @@ <title>Source Repositories</title> <p>The Project's codebase is maintained in shared information - repositories using CVS on the cvs.apache.org machine. Only Committers + repositories using SVN on the svn.apache.org machine. Only Committers have write access to these repositories. Everyone has read access via - anonymous CVS.</p> + anonymous SVN.</p> <p>All Java Language source code in the repository must be written in conformance to the "Code Conventions for the Java Programming @@ -628,11 +628,11 @@ <p>or</p> - <source>cvs diff -u Main.java >> patchfile.txt</source> + <source>svn diff Main.java >> patchfile.txt</source> <p>or (Win32):</p> - <p>You can use WinCVS for a nice GUI or you can install Cygwin which + <p>You can use TortoiseSVN for a nice GUI or you can install Cygwin which will enable you to use the bash shell and also installs a lot of other utilities (such as diff and patch) that will turn your PC into a virtual Unix machine.</p>
