svn commit: r15136 - trunk/www/subprojects.html

Author: linus
Date: 2008-07-01 02:29:13-0700
New Revision: 15136

Modified:
   trunk/www/subprojects.html

Log:
Small updates in the text.

Modified: trunk/www/subprojects.html
Url: http://argouml.tigris.org/source/browse/argouml/trunk/www/subprojects.html?view=diff&rev=15136&p1=trunk/www/subprojects.html&p2=trunk/www/subprojects.html&r1=15135&r2=15136
==============================================================================
--- trunk/www/subprojects.html	(original)
+++ trunk/www/subprojects.html	2008-07-01 02:29:13-0700
@@ -56,14 +56,12 @@
 	  other tools needed to build.
       <li>The tagging and branching rules from the ArgoUML main project apply.
       <li>The subprojects will use subversion as the version control system.
-      <li>Xenofarm and maybe other static checks will work over several 
+      <li>The nightly build and other static checks will work over several 
           projects, i.e. all projects included in the releases.
-          There is work to be done here!
       <li>Java Web Start starts will be made to include subproject result.
-          There is work to be done here!
     </ul>
 
-<li>Subprojects will, in most cases, not use their own issuezilla.
+<li>Subprojects will not use their own issuezilla.
     Instead bug reports will be filed in the ArgoUML issuezilla where
     subprojects will get their own subcomponent.
     The reasons for this are
@@ -72,7 +70,7 @@
     to make it easier for our users to file bug reports, and
     to make it possible to move a miss-filed issue from one subproject
     to another (or back and forth between the main project).
-    This requires that persons developing in the subproject are require
+    This requires that persons developing in a subproject
     to hold an Observer role in the main project to be able to work
     with the issues.