User: starksm
Date: 01/07/13 14:21:35
Modified: . CVSAdmin.jsp
Log:
Document the requirement to run the jbosstest suite
Revision Changes Path
1.6 +22 -1 newsite/CVSAdmin.jsp
Index: CVSAdmin.jsp
===================================================================
RCS file: /cvsroot/jboss/newsite/CVSAdmin.jsp,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- CVSAdmin.jsp 2001/06/21 19:23:33 1.5
+++ CVSAdmin.jsp 2001/07/13 21:21:34 1.6
@@ -202,6 +202,7 @@
you need to check out that branch and make the changes. So for example,
if you need to add a patch the the 2.2 branch of the example cvs structure
above, you need to first check out the 2.2 branch using the Branch_2_2 tag.
+<ol>
<li>Checkout the module using the branch tag you want to work on. To
checkout the 2.2 branch of the jboss module do:
<pre>cvs co -r Branch_2_2 jboss</pre>
@@ -225,7 +226,13 @@
<li>Make your chages to the source in the jboss working directory created
by the previous check out.
+</li>
+<li><b>(Required)</b> Run the jbosstest unit test suite. If there are any errors do
+NOT commit your change. Repeated failures to validate a change made to a branch
+will result in loss of CVS write privaledges.
+</li>
+
<li>Commit your changes. Do this by executing the following command in the
directory you made the changes in, or any common parent directory:
<pre>cvs commit -m "Your commit msg"</pre>
@@ -233,6 +240,7 @@
don't you will be prompted for the commit msg. Note that this will apply the
same commit msg to all files you have changed. If you want specific commit
msgs for each file then you can perform a seperate commit on each file.
+</li>
<li>(Required) Tag the branch with the next beta binary release tag by incrementing
the build number of the latest tag. To determine what build number to use, look
@@ -261,13 +269,17 @@
you have made you need to use Rel_2_2_2_1. Do this using:
<pre>cvs tag Rel_2_2_2_1</pre>
from the top of the jboss working directory.
+</li>
<li>(Required) Merge the changes to the main trunk if they are missing. You
need to validate that the changes you have made to the release branch are
not already in the main trunk and merge the changes if they are.
+</li>
<li>(Required, if merge was done) Check out the latest trunk code:
<pre>cvs co jboss</pre>
+</li>
+
<li>(Required, if merge was done) Tag the main trunk with the next alpha
build tag. Assuming the this is Rel_2_3_1_5, you would do:
<pre>cvs tag Rel_2_3_1_5</pre>
@@ -280,6 +292,8 @@
jboss release branch, perform the following steps. These steps are
for an example of making a change in the jbosscx module for incorporation
into the jboss 2.4 release branch.
+</li>
+</ol>
<ol>
<li>Checkout the module using the branch tag you want to work on(if
@@ -290,6 +304,7 @@
<li>Make your chages to the source in the jbosscx working directory created
by the previous check out.
</li>
+
<li>Commit your changes. Do this by executing the following command in the
directory you made the changes in, or any common parent directory:
<pre>cvs commit -m "Your commit msg"</pre>
@@ -309,6 +324,12 @@
</li>
<li>Copy the module jars into the approriate jboss/src subdirectory locations.
</li>
+
+<li><b>(Required)</b> Run the jbosstest unit test suite. If there are any errors do
+NOT commit your change. Repeated failures to validate a change made to a branch
+will result in loss of CVS write privaledges.
+</li>
+
<li>Commit the jar changes in the jboss module by running the following
from within the jboss/src directory:
<pre>cvs commit -m "Your commit msg"</pre>
@@ -317,7 +338,7 @@
within the jboss root working directory tag the release:
<pre>cvs tag Rel_2_4_0_1</pre>
</li>
+
</ol>
<jsp:include page="navigation.jsp" flush="true" />
-
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
