[Japi-cvs] SF.net SVN: japi: [5] trunk/src/doc
Status: Beta
Brought to you by:
christianhujer
Menu
▾
▴
[Japi-cvs] SF.net SVN: japi: [5] trunk/src/doc
|
From: <chr...@us...> - 2006-04-03 01:41:29
|
Revision: 5 Author: christianhujer Date: 2006-04-02 18:41:18 -0700 (Sun, 02 Apr 2006) ViewCVS: http://svn.sourceforge.net/japi/?rev=5&view=rev Log Message: ----------- Added subversion documentation. Modified Paths: -------------- trunk/src/doc/start.xhtml Added Paths: ----------- trunk/src/doc/subversion.xhtml Modified: trunk/src/doc/start.xhtml =================================================================== --- trunk/src/doc/start.xhtml 2006-04-03 00:54:20 UTC (rev 4) +++ trunk/src/doc/start.xhtml 2006-04-03 01:41:18 UTC (rev 5) @@ -37,6 +37,7 @@ <li>Overview of <a href="changes">Changes to previous versions</a></li> <li><a href="releasePlan">Release Plan</a></li> <li><a href="wontFixes">Known flaws that won't be fixed</a></li> + <li><a href="subversion">Accessing JAPI's Subversion Repository</a></li> </ul> <h2>Contact the developers</h2> <ul> Added: trunk/src/doc/subversion.xhtml =================================================================== --- trunk/src/doc/subversion.xhtml (rev 0) +++ trunk/src/doc/subversion.xhtml 2006-04-03 01:41:18 UTC (rev 5) @@ -0,0 +1,62 @@ +<?xml version="1.0" encoding="utf-8"?> +<!-- $Id: releasePlan.xhtml,v 1.6 2006/03/29 22:21:14 christianhujer Exp $ --> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="de"> + <head> + <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8" /> + <meta name="Date" content="$Date: 2006/03/29 22:21:14 $" /> + <title>JAPI Subversion Developer Access</title> + </head> + <body> + <h2>Checking out a normal working copy</h2> + <p> + To checkout a normal working copy of the latest development, checkout the trunk. + This is what's called HEAD or MAIN/LATEST in other version control systems. + </p> + <p><code>svn co https://svn.sourceforge.net/svnroot/japi japi/trunk</code></p> + <h2>Rules</h2> + <p> + Current rules are this: + </p> + <ul> + <li> + All files need a mime type. + For normal source code, use <code>text/plain</code>. + Use <code>svn propset svn:mime-type text/plain <var>filename</var></code> to set the mime type. + </li> + <li> + All files with a text based mime type need a line ending setting. + JAPI convention is to always use <code>LF</code>. + Use <code>svn propset svn:eol-style LF <var>filename</var></code> to set the line ending style. + </li> + </ul> + <h2>Releases</h2> + <p> + Releases are created in the following way: + </p> + <ol> + <li> + A branch with the new release name is created. + Usually the branch will increase the minor revision and use it as its name. + Example: <code>svn copy trunk branch/0.8</code>. + The policy for branches is that they aren't completely frozen, but only changes required for release and bug fixing are allowed. + </li> + <li> + The branch is braught into releasable state. + This usually should be zero effort, yet consider this a separate step. + </li> + <li> + The release is published. + As a part of the release publishing, a tag with the new release name and patch level is created. + Example: <code>svn copy branch/0.8 tag/0.8.0</code>. + The policy for tags is that they are completely frozen, tags must never ever be changed. + </li> + </ol> + <h2>Checking out a released version</h2> + <p> + To checkout a released version, use <code>svn co https://svn.sourceforge.net/svnroot/japi japi/tag/<var>version</var></code> with + <var>version</var> being the release name. + To checkout, for example, version <samp>0.8.0</samp>, use <samp>svn co https://svn.sourceforge.net/svnroot/japi japi/tag/0.8.0</samp>. + </p> + </body> +</html> Property changes on: trunk/src/doc/subversion.xhtml ___________________________________________________________________ Name: svn:mime-type + text/xml Name: svn:eol-style + LF This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
