<p><strong>windows-cron</strong> - a small package that makes cron possible on Windows systems</p>
<p><strong>docs</strong> - various extra user-contributed documentation</p>
</blockquote>
- <p>Most people are working on the existing features in the <strong>moodle</strong> module, but many are also contributing new ideas in the <strong>contrib</strong> modules. Once code reaches a certain level of maturity in the <strong>contrib</strong> area, it migrates over into the main <strong>moodle</strong> tree. </p>
+ <p>Most people are working on the existing features in the <strong>moodle</strong> module, but many are also contributing new ideas in the <strong>contrib</strong> modules. Once code reaches a certain level of maturity in the <strong>contrib</strong> area, it can be migrated over into the main <strong>moodle</strong> tree. </p>
<p> </p>
</blockquote>
<h2><a name="3" id="3"></a>3. Basic CVS Commands </h2>
- <h3><a name="3.1" id="3.1"></a>3.1 CVS on Unix </h3>
<blockquote>
- <p>Sourceforge CVS uses ssh as a transport layer for security, so you will have to set a CVS_RSH environment variable in your Unix shell. It's best to put these commands in your .bashrc or .cshrc so you don't have to type it all the time<strong>:</strong></p>
+ <h3><a name="3.1" id="3.1"></a>3.1 CVS on Unix </h3>
<blockquote>
- <pre><strong>setenv CVS_RSH ssh</strong> (for csh, tcsh etc)</pre>
- <pre><strong>export CVS_RSH=ssh</strong> (for sh, bash etc)</pre>
- </blockquote>
- <p>Next, you can check out the latest development version of Moodle using this (all one line): </p>
- <blockquote>
- <pre><strong>cvs -z3 -d:ext:<span class="style1">myusername</span>@cvs.sourceforge.net:/cvsroot/moodle co moodle</strong></pre>
- </blockquote>
- <p>The command is similar for other CVS modules:</p>
- <blockquote>
- <pre><strong>cvs -z3 -d:ext:<span class="style1">myusername</span>@cvs.sourceforge.net:/cvsroot/moodle co contrib</strong></pre>
- </blockquote>
- <p>Don't try to do run this first CVS command over an existing moodle installation: start fresh with a new directory.</p>
- <p>Note that you will be prompted for <strong><font color="#990000">mypassword</font></strong> for each command unless you set up <a target="_top" href="http://sourceforge.net/account/editsshkeys.php">authorized keys</a>.</p>
- <p>Now, you should have a new 'moodle' directory. You can rename it and move it around if you like. Go into it: </p>
- <blockquote>
- <pre><strong>cd moodle </strong></pre>
- </blockquote>
- <p>All the latest Moodle files should be in there. You can now change files in your copy. To compare your files and directories against the main CVS copy on the server use cvs diff, e.g.: </p>
- <blockquote>
- <pre><strong>cvs diff -c config-dist.php
+ <p>Sourceforge CVS uses ssh as a transport layer for security, so you will have to set a CVS_RSH environment variable in your Unix shell. It's best to put these commands in your .bashrc or .cshrc so you don't have to type it all the time<strong>:</strong></p>
+ <blockquote>
+ <pre><strong>setenv CVS_RSH ssh</strong> (for csh, tcsh etc)</pre>
+ <pre><strong>export CVS_RSH=ssh</strong> (for sh, bash etc)</pre>
+ </blockquote>
+ <p>Next, you can check out the latest development version of Moodle using this (all one line): </p>
+ <blockquote>
+ <pre><strong>cvs -z3 -d:ext:<span class="style1">myusername</span>@cvs.sourceforge.net:/cvsroot/moodle co moodle</strong></pre>
+ </blockquote>
+ <p>The command is similar for other CVS modules:</p>
+ <blockquote>
+ <pre><strong>cvs -z3 -d:ext:<span class="style1">myusername</span>@cvs.sourceforge.net:/cvsroot/moodle co contrib</strong></pre>
+ </blockquote>
+ <p>Don't try to do run this first CVS command over an existing moodle installation: start fresh with a new directory.</p>
+ <p>Note that you will be prompted for <strong><font color="#990000">mypassword</font></strong> for each command unless you set up <a target="_top" href="http://sourceforge.net/account/editsshkeys.php">authorized keys</a>.</p>
+ <p>Now, you should have a new 'moodle' directory. You can rename it and move it around if you like. Go into it: </p>
+ <blockquote>
+ <pre><strong>cd moodle </strong></pre>
+ </blockquote>
+ <p>All the latest Moodle files should be in there. You can now change files in your copy. To compare your files and directories against the main CVS copy on the server use cvs diff, e.g.: </p>
+ <blockquote>
+ <pre><strong>cvs diff -c config-dist.php
cvs diff -c lang</strong></pre>
- </blockquote>
- <p>To fetch the latest updates from the server use: </p>
- <blockquote>
- <pre><strong>cvs update -dP</strong> </pre>
- </blockquote>
- <p>To copy your new files back to the server you would do something like: </p>
- <blockquote>
- <pre><strong>cd lang/ca
+ </blockquote>
+
<p>To fetch the latest updates from the server use: </p>
+
<pre><strong>cvs update -dP</strong> </pre>
+ </blockquote>
+
<p>To copy your new files back to the server you would do something like: </p>
+
<pre><strong>cd lang/ca
cvs commit</strong> </pre>
+ </blockquote>
+ <p>You will be prompted to add some comments (depends on your default text editor) ... add a meaningful comment and close the editor ... the files will be sent to Sourceforge and stored. Done! </p>
+ <p>To save more time you can put default arguments into a file called .cvsrc in your home directory. For example, mine contains: </p>
+ <blockquote>
+ <pre><strong>diff -c
+update -dP</strong> </pre>
+ </blockquote>
+ <p>Try 'cvs help' for more details ... </p>
+ <p> </p>
</blockquote>
- <p>You will be prompted to add some comments (depends on your default text editor) ... add a meaningful comment and close the editor ... the files will be sent to Sourceforge and stored. Done! </p>
- <p>To save more time you can put default arguments into a file called .cvsrc in your home directory. For example, mine contains: </p>
+ <h3><a name="3.2" id="3.2"></a>3.2 CVS on Windows </h3>
<blockquote>
- <pre><strong>diff -c
-update -dP</strong> </pre>
+ <p>First, you need to download a completely fresh copy of Moodle using your developer account.</p>
</blockquote>
- <p>Try 'cvs help' for more details ... </p>
- <p> </p>
- </blockquote>
- <h3><a name="3.2" id="3.2"></a>3.2 CVS on Windows </h3>
- <blockquote>
- <p>First, you need to download a completely fresh copy of Moodle using your developer account.</p>
<ol>
<ol>
- <li> Get TortoiseCVS from <a target="_top" href="http://www.tortoisecvs.org/">tortoisecvs.org</a> and install it, then reboot.</li>
- <li>Find or create a new folder somewhere where you want Moodle to be downloaded to.</li>
- <li>Right-mouse-click that folder and choose "<strong>CVS Checkout</strong>" from the menu. You should see a dialog box.</li>
- <li>Copy this text into the CVSROOT field (using your own username!):
- <pre> :ext:<font color="#990000">myusername</font>@cvs.sourceforge.net:/cvsroot/moodle</pre>
- </li>
- <li>Under the "Module" field, type "<strong>moodle</strong>" to get the latest development version of Moodle, "<strong>contrib</strong>" to get the contributions directory, or "<strong>mysql</strong>" to get the MySQL Admin module.</li>
- <li>Press the button: "<strong>OK</strong>" and everything should be downloaded.<br>
- </li>
+ <ol>
+ <li> Get TortoiseCVS from <a target="_top" href="http://www.tortoisecvs.org/">tortoisecvs.org</a> and install it, then reboot.</li>
+ <li>Find or create a new folder somewhere where you want Moodle to be downloaded to.</li>
+ <li>Right-mouse-click that folder and choose "<strong>CVS Checkout</strong>" from the menu. You should see a dialog box.</li>
+ <li>Copy this text into the CVSROOT field (using your own username!):
+ <pre> :ext:<font color="#990000">myusername</font>@cvs.sourceforge.net:/cvsroot/moodle</pre>
+ </li>
+ <li>Under the "Module" field, type "<strong>moodle</strong>" to get the latest development version of Moodle, "<strong>contrib</strong>" to get the contributions directory, or "<strong>mysql</strong>" to get the MySQL Admin module.</li>
+ <li>Press the button: "<strong>OK</strong>" and everything should be downloaded.<br>
+ </li>
+ </ol>
</ol>
</ol>
- <p>A dialog box should show all the files being downloaded, and after a while you should have a complete copy of Moodle. After this first checkout, you can fetch the latest updated files from the CVS server:</p>
+ <blockquote>
+ <p>A dialog box should show all the files being downloaded, and after a while you should have a complete copy of Moodle. After this first checkout, you can fetch the latest updated files from the CVS server:</p>
+ </blockquote>
<ol>
<ol>
- <li> Right-mouse-click on your Moodle folder (or any file) and select "<strong>CVS Update</strong>". </li>
- <li>Sit back and watch the logs scroll by. Take note of conflicts that may occur if your local code has changes that conflict with the incoming versions - you will need to edit these files and resolve the conflicts manually. <br>
- </li>
+ <ol>
+ <li> Right-mouse-click on your Moodle folder (or any file) and select "<strong>CVS Update</strong>". </li>
+ <li>Sit back and watch the logs scroll by. Take note of conflicts that may occur if your local code has changes that conflict with the incoming versions - you will need to edit these files and resolve the conflicts manually. <br>
+ </li>
+ </ol>
</ol>
</ol>
- <p>After modifying files (you will notice their icons change from green to red!), you can commit them back to the CVS server like this:</p>
+ <blockquote>
+ <p>After modifying files (you will notice their icons change from green to red!), you can commit them back to the CVS server like this:</p>
+ </blockquote>
<ol>
<ol>
- <li> Right-mouse-click on your Moodle folder (or any file) and select "<strong>CVS Commit...</strong>".</li>
- <li>In the dialog box, type a clear description of the changes you are committing.</li>
- <li>Click "OK". Your changes will be sent to the server.<br>
- </li>
+ <ol>
+ <li> Right-mouse-click on your Moodle folder (or any file) and select "<strong>CVS Commit...</strong>".</li>
+ <li>In the dialog box, type a clear description of the changes you are committing.</li>
+ <li>Click "OK". Your changes will be sent to the server.<br>
+ </li>
+ </ol>
</ol>
</ol>
</blockquote>
<blockquote>
<pre><strong>cvs status -v index.php</strong></pre>
</blockquote>
- <br />
+ <p>Tags and branches should ALWAYS be applied to the <strong>entire module</strong> (all of Moodle). Don't tag individual files or directories. <br />
+ </p>
<h3><a name="4.1" id="4.1"></a>4.1 Trunk development</h3>
- <p>The Trunk of CVS is the main development version of Moodle. In CVS it is also known as the <span class="style4">HEAD</span>, or default branch.</p>
- <p>Moodle developers try to keep this stable as possible, but as it usually contains new code it probably has bugs and small instabilities.</p>
- <p>Every now and then we decide the product has enough features to make a release. At this time, the trunk is tagged with a MOODLE_XX_BETA tag (in case we ever want to roll back to that point) and a new branch is formed for the release, called <span class="style1">MOODLE_XX_STABLE</span>. </p>
- <p>A Beta package is also released at this point - it's for testers who don't use CVS but want to test the latest features and report bugs.</p>
- <p> </p>
- <h3><a name="4.2" id="4.2"></a>4.2 Stable branches for each release</h3>
- <p>As soon as the stable branch <span class="style3">MOODLE_XX_STABLE</span> is created, development efforts will fork into two streams for a while. Some people may continue working on new features in the trunk for the next release, but most developers should be concentrating on using the current <span class="style1"><strong>STABLE</strong></span> branch and fixing bugs that are found in it. </p>
- <p>You can switch your local copy of Moodle to the STABLE version using the following command in Unix from the root directory:</p>
<blockquote>
- <pre><strong>cvs update -dP -r <span class="style1">MOODLE_XX_STABLE</span></strong></pre>
+ <p>The Trunk of CVS is the main development version of Moodle. In CVS it is also known as the <span class="style4">HEAD</span>, or default branch.</p>
+ <p>Moodle developers try to keep this stable as possible, but as it usually contains new code it probably has bugs and small instabilities.</p>
+ <p>Every now and then we decide the product has enough features to make a release. At this time, the trunk is tagged with a <strong>MOODLE_XX_BETA</strong> tag (in case we ever want to roll back to that point) and a new branch is formed for the release, called <span class="style1">MOODLE_XX_STABLE</span>. </p>
+ <p>A Beta package is also released at this point - it's for testers who don't use CVS but want to test the latest features and report bugs.</p>
</blockquote>
- <p>After that, all the commands described above will apply to that stable version. To return to the trunk version just issue:</p>
+ <p> </p>
+ <h3><a name="4.2" id="4.2"></a>4.2 Stable branches for each release</h3>
<blockquote>
- <pre><strong>cvs update -dPA</strong></pre>
- </blockquote>
- <p>On Windows clients you should have a menu from which you can choose the branch. </p>
- <p>Once the new STABLE branch really stabilises, a release can be declared. Packages are created for distribution and the branch will be tagged (by Martin) with a tag named: <strong>MOODLE_XXX</strong></p>
- <p>Periodically, bug fixes in the STABLE branch should be merged into the trunk so that they become available in future versions of Moodle. A floating tag called MOODLE_XX_MERGED will be maintained to keep track of the last merge. The procedure for such a merge is as follows:</p>
- <ol>
+ <p>As soon as the stable branch <span class="style3">MOODLE_XX_STABLE</span> is created, development efforts will fork into two streams for a while. Some people may continue working on new features in the trunk for the next release, but most developers should be concentrating on using the current <span class="style1"><strong>STABLE</strong></span> branch and fixing bugs that are found in it. </p>
+ <p>You can switch your local copy of Moodle to the STABLE version using the following command in Unix from the root directory:</p>
+ <blockquote>
+ <pre><strong>cvs update -dP -r <span class="style1">MOODLE_XX_STABLE</span></strong></pre>
+ </blockquote>
+ <p>After that, all the commands described above will apply to that stable version. To return to the trunk version just issue:</p>
+ <blockquote>
+ <pre><strong>cvs update -dPA</strong></pre>
+ </blockquote>
+ <p>On Windows clients you should have a menu from which you can choose the branch. </p>
+ <p>Once the new STABLE branch really stabilises, a release can be declared. Packages are created for distribution and the branch will be tagged (by Martin) with a tag named: <strong>MOODLE_XXX</strong></p>
+ <p>Periodically, bug fixes in the STABLE branch should be merged into the trunk so that they become available in future versions of Moodle. A floating tag called MOODLE_XX_MERGED will be maintained to keep track of the last merge. The procedure for such a merge is as follows:</p>
<ol>
- <li><strong> cvs update -dPA</strong></li>
- <li><strong>cvs update -j MOODLE_13_MERGED -j MOODLE_13_STABLE</strong></li>
- <li><strong>cvs commit </strong></li>
- <li><strong> cvs update -dPr MOODLE_13_STABLE</strong></li>
- <li><strong>cvs tag -RF MOODLE_13_MERGED</strong></li>
+ <ol>
+ <li>Get out the very latest trunk version.<br>
+ <br>
+ <strong>cvs update -dPA</strong><br>
+ </li>
+ <li>Merge everything on the branch since the last merge, into your trunk version <strong><br>
+ <br>
+ cvs update -j MOODLE_13_MERGED -j MOODLE_13_STABLE<br>
+ </strong></li>
+ <li>Check the merged copy back into CVS trunk version <span class="style1"><strong><br>
+ <br>
+ </strong></span><strong>cvs commit </strong><span class="style1"><strong><br>
+ </strong></span></li>
+ <li>Go back to the branch version <br>
+ <br>
+ <strong>cvs update -dPr MOODLE_13_STABLE<br>
+ </strong></li>
+ <li>Update the floating merge tag so that this process can be repeated next time <br>
+ <p><strong>cvs tag -RF MOODLE_13_MERGED</strong></p>
+ </li>
+ </ol>
</ol>
- </ol>
- <p><br>
- Finally, the values for <em>$version</em> in all the Moodle version.php files within the stable branch should not be updated at all if possible (except the last digit if necessary). The reason is that someone updating from a very stable version to the next very stable version could miss database upgrades that happened on the trunk. </p>
+ <p><br>
+ Finally, the values for <em>$version</em> in all the Moodle version.php files within the stable branch should not be updated at all if possible (except the last digit if necessary). The reason is that someone updating from a very stable version to the next very stable version could miss database upgrades that happened on the trunk. </p>
+ </blockquote>
<p> </p>
<h3><a name="4.3" id="4.3"></a>4.3 Feature branches for large changes </h3>
- <p>Occasionally, there may be a very large feature that needs to be checked in so several people can work on it, but it is too unstable to be included in the main development trunk.</p>
- <p>In these cases a short-term branch can be created to work on the feature, and then merged back into the main trunk as soon as possible. An example called <span class="style1"><strong>MOODLE_14_WIDGET</strong></span> branch can be seen in the above diagram.</p>
- <p>If you need to do this for your new WIDGET feature, follow these steps:</p>
+ <blockquote>
+ <p>Occasionally, there may be a very large feature that needs to be checked in so several people can work on it, but it is too unstable to be included in the main development trunk.</p>
+ <p>In these cases a short-term branch can be created to work on the feature, and then merged back into the main trunk as soon as possible. An example called <span class="style1"><strong>MOODLE_14_WIDGET</strong></span> branch can be seen in the above diagram.</p>
+ <p>If you need to do this for your new WIDGET feature, follow these steps:</p>
+ </blockquote>
<ol>
<ol>
- <li>Discuss with other developers to make sure it's necessary.</li>
- <li>Make a tag on the <strong>trunk</strong> called <strong>MOODLE_XX_WIDGET_PRE</strong></li>
- <li>Create your branch called <span class="style1"><strong>MOODLE_XX_WIDGET</strong></span></li>
- <li>Work in that branch until the feature is reasonably stable.</li>
- <li>Merge the whole branch into the trunk and abandon the branch.</li>
+ <ol>
+ <li>Discuss with other developers to make sure it's necessary!</li>
+ <li>Make a new tag on the <strong>trunk</strong> (for all of moodle) called <strong>MOODLE_XX_WIDGET_PRE<br>
+ <br>
+ cvs tag -R MOODLE_XX_WIDGET_PRE
+ <br>
+ </strong></li>
+ <li>Create your branch called <span class="style1"><strong>MOODLE_XX_WIDGET<br>
+ <br>
+ </strong></span><strong>cvs tag -Rb <span class="style1">MOODLE_XX_WIDGET</span></strong><span class="style1"><strong> <br>
+ </strong></span></li>
+ <li>Work in that branch until the feature is reasonably stable. Commit as necessary.<br>
+ <br>
+ <strong>cvs commit
+ <br>
+ </strong></li>
+ <li>When ready, merge the whole branch into the trunk, commit it to the trunk and then abandon the branch.<br>
+ <p><strong>cvs update -dPA</strong></p>
+ <p><strong>cvs update -j <span class="style1">MOODLE_XX_WIDGET</span></strong></p>
+ <p><strong>cvs commit </strong></p>
+ </li>
+ </ol>
</ol>
</ol>
- <p> </p>
+ <blockquote>
+ <p> </p>
+ </blockquote>
</blockquote>
- <p align="center">Good luck!</p>
+ <p align="center">Good luck, be careful and have fun!</p>
<p> </p>
</blockquote>
<p align="CENTER"><font size="1"><a href="." target="_top">Moodle Documentation</a></font></p>
projects / moodle.git / commitdiff