husted 2004/02/20 09:03:20
Modified: doc project.xml releases.xml status.xml
doc/proposals release-plan_1_2_0.xml
Log:
Correct hyperlinks.
Revision Changes Path
1.47 +4 -4 jakarta-struts/doc/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/project.xml,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- project.xml 6 Jan 2004 05:49:41 -0000 1.46
+++ project.xml 20 Feb 2004 17:03:19 -0000 1.47
@@ -86,16 +86,16 @@
<menu name="Development">
<item
- name="CVS Repository"
- href="http://cvs.apache.org/viewcvs/jakarta-struts/";
+ name="Roadmap"
+ href="status.html"
/>
<item
name="Release Guidelines"
href="releases.html"
/>
<item
- name="Roadmap"
- href="status.html"
+ name="CVS Repository"
+ href="http://cvs.apache.org/viewcvs/jakarta-struts/";
/>
</menu>
1.7 +6 -6 jakarta-struts/doc/releases.xml
Index: releases.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/releases.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- releases.xml 13 Jan 2004 13:19:48 -0000 1.6
+++ releases.xml 20 Feb 2004 17:03:19 -0000 1.7
@@ -10,13 +10,13 @@
<body>
<section href="status" name="Release Guidelines">
<p>This document describes the Struts
- <a href="#Releases">release process</a>and our
+ <a href="#Releases">release process</a> and our
<a href="#Coding">coding conventions</a>. Both stable and development
releases are
<a href="acquiring.html">available for download</a>.</p>
</section>
<section href="Releases" name="Release Guidelines">
<p>A
- <a href="http://jakarta.apache.org/commons/versioning.html";>point
release</a>should be made before and after any product change that is not a
"fully-compatible change" (see link). This includes moving a dependency from an
internal package to an external product, including products distributed through the
Jakarta Commons. We should place any fully-compatible changes in the hands of the
community before starting on a change that is only "interface" or "external-interface"
compatible.</p>
+ <a href="http://jakarta.apache.org/commons/versioning.html";>point release</a>
should be made before and after any product change that is not a "fully-compatible
change" (see link). This includes moving a dependency from an internal package to an
external product, including products distributed through the Jakarta Commons. We
should place any fully-compatible changes in the hands of the community before
starting on a change that is only "interface" or "external-interface" compatible.</p>
<p>A fully-compatible point release does not always need a "preview" beta or
milestone release. If appropriate, a Release Candidate can be cut, uploaded to the
Release Manager's home directory on cvs.apache.org (~/public_html), and voted to be
released to the general public from there.</p>
<p>Any release should follow the same general process used by the Jakarta
Commons and the Apache HTTP Server project.</p>
<ul>
@@ -52,7 +52,7 @@
<li>There is a "release" target in the buildfile that will zip and tar the
releases. Before uploading the release, extract the sample web applications and deploy
the WARs under each of the "supported" containers. Play test each application under
each container to be sure they operate nominally.</li>
<li>Be sure to copy the [EMAIL PROTECTED] list on any release
announcement.</li>
<li>Remember to update the
- <a href="status.html">Status section of the Roadmap page</a>once a release
is available.</li>
+ <a href="status.html">Status section of the Roadmap page</a> once a release
is available.</li>
<li>By the way, the nightly builds are being created on a machine of Craig
McClanahan's. If there are problems with a nightly build that seem infrastructure
related, Craig is the one to contact.</li>
</ul>
</section>
@@ -90,14 +90,14 @@
<small>//
------------------------------------------------------------------------
78</small></li>
<li>Please do your best to provide high-quality Javadocs for all source
code elements. Package overviews (aka "Developer Guides") are also encouraged.</li>
<li>When working on a bugfix, please first write a
- <a href="http://www.junit.org";>JUnit</a>test that proves the bug exists,
and then use the test to prove the bug is fixed. =:0)</li>
+ <a href="http://www.junit.org";>JUnit</a> test that proves the bug exists,
and then use the test to prove the bug is fixed. =:0)</li>
<li>When working on an enhancement, please feel free to use test-driven
design and write the test first <head-slap/>. For more about TDD, see the
<a href="http://sourceforge.net/projects/mockobjects";>MockObjects
project</a>.</li>
<li>As files are updated from year to year, the copyright on each file
should be extended to include the current year.
<b>You do not need to change the copyright year unless you change the
file.</b>Every source file should include the ASF copyright notice and current Apache
License and copyright.</li>
<li>Provide high-level API compatibility for any changes made within the
same major release series (#.x). Changes which adversely affect compatibility should
be slotted for the next major release series (++#.x).</li>
<li>Our favorite books about programming are
- <a
href="http://www.amazon.com/exec/obidos/ISBN=0201633612/hitchhikeguidetoA/";>Design
Patterns</a>and
+ <a
href="http://www.amazon.com/exec/obidos/ISBN=0201633612/hitchhikeguidetoA/";>Design
Patterns</a> and
<a
href="http://www.amazon.com/exec/obidos/ISBN=0201485672/hitchhikeguidetoA/";>Refactoring</a>.</li>
<li>Our favorite book about open source development is the
<a
href="http://www.amazon.com/exec/obidos/ISBN=1565927249/hitchhikeguidetoA/";>The
Cathedral and the Bazaar</a>.</li>
@@ -111,7 +111,7 @@
</section>
<section>
<p class="right">Next:
- <a href="news/index.html">News and Status</a></p>
+ <a href="http://cvs.apache.org/viewcvs/jakarta-struts/";>CVS Repository</a></p>
</section>
</body>
</document>
1.60 +2 -2 jakarta-struts/doc/status.xml
Index: status.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/status.xml,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -r1.59 -r1.60
--- status.xml 20 Feb 2004 14:47:01 -0000 1.59
+++ status.xml 20 Feb 2004 17:03:19 -0000 1.60
@@ -472,7 +472,7 @@
<li>
- <a href="proposals/release-plan_1_2_0.html">Release Plan 1.2.0</a> --
unratified DRAFT document
+ <a href="proposals/release-plan_1_2_0.html">Release Plan 1.2.0</a>
</li>
<li>
1.9 +2 -2 jakarta-struts/doc/proposals/release-plan_1_2_0.xml
Index: release-plan_1_2_0.xml
===================================================================
RCS file: /home/cvs/jakarta-struts/doc/proposals/release-plan_1_2_0.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- release-plan_1_2_0.xml 20 Feb 2004 14:41:23 -0000 1.8
+++ release-plan_1_2_0.xml 20 Feb 2004 17:03:20 -0000 1.9
@@ -94,7 +94,7 @@
<li>
<strong>Resolve showstoppers.</strong>
Relevant
- <a
href="http://issues.apache.org/bugzilla/buglist.cgi?email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Struts&version=1.1RC2&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&newqueryname=&order=Bug+Number";>
+ <a
href="http://issues.apache.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=Blocker&bug_severity=Critical&bug_severity=Major&bug_severity=Normal&bug_severity=Minor&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Struts&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=bugs.bug_i";>
Bugzilla tickets</a> verified by a Struts Committer to have the
Severity BLOCKER, CRITICAL, or
MAJOR must be "Resolved" with one of these Bugzilla resolutions:
FIXED, INVALID, WONTFIX, WORKSFORME.
</li>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
