<strong>If you have not already done so, please
<a href="http://www.tigris.org/servlets/Login">log in</a>
before submitting a feature request!</strong>
-<p>
+</p>
<p>
Feature requests should be submitted to
-<a href="http://scons.tigris.org/issues/enter_bug.cgi?subcomponent=scons&issue_type=FEATURE">http://scons.tigris.org/issues/enter_bug.cgi?subcomponent=scons&issue_type=FEATURE</a>
+<a href="http://scons.tigris.org/issues/enter_bug.cgi?subcomponent=scons&issue_type=FEATURE">http://scons.tigris.org/issues/enter_bug.cgi?subcomponent=scons&issue_type=FEATURE</a>.
A more detailed set of <a href="feature-request.html#steps">submission steps</a>
can be found below.
</p>
<strong>If you have not already done so, please
<a href="http://www.tigris.org/servlets/Login">log in</a>
before submitting a patch!</strong>
-<p>
+</p>
<p>
Patches should be submitted to
-<a href="http://scons.tigris.org/issues/enter_bug.cgi?subcomponent=scons&issue_type=PATCH">http://scons.tigris.org/issues/enter_bug.cgi?subcomponent=scons&issue_type=PATCH</a>
+<a href="http://scons.tigris.org/issues/enter_bug.cgi?subcomponent=scons&issue_type=PATCH">http://scons.tigris.org/issues/enter_bug.cgi?subcomponent=scons&issue_type=PATCH</a>.
Please follow the <a href="patch-submission.html#guidelines">submission guidelines</a> below
to make sure your patch contains the necessary information.
A more detailed set of <a href="patch-submission.html#steps">submission steps</a>
<h2 id="guidelines">Guidelines for Patch Submission</h2>
<p>
-Your bug will be much more likely to get diagnosed and fixed
-if you supply all the necessary information to make it easy to do so.
+To try to maintain and improve the quality of SCons releases,
+we have some pretty high standards for the quality of patches
+that make it into the SCons code base.
+This list of guidelines describes how to make it as
+easy as possible for your patch to be accepted for integration.
+We're still interested in your code
+even if you don't follow all of these guidelines,
+but then your patch will more than likely sit in the queue
+until someone else has time to supply all of the
+necessary missing items.
</p>
<ul>
prevent it from being integrated at all.
If you choose not to create a tigris.org account,
at least put some identifying contact information
-in the bug description.
+in the patch description.
</p>
</li>
You can still submit a patch anonymously, without logging in,
but it may be impossible to integrate your patch
if we need more information and have no
-idea who submitted the bug or how to contact you.
+idea who submitted the patch or how to contact you.
If you choose not to create a tigris.org account,
at least put some identifying contact information
in the description.
</head>
<body>
+<p>
+<strong>21 May 2006:</strong>
+The SCons Project tracking of bug reports, patches and feature requests
+ahs been moved from our
+<a href="http://sourceforge.net/projects/scons/">SourceForge project page</a>
+to our <a href="http://scons.tigris.org/servlets/ProjectIssues">Issue Tracker</a>
+here at
+<a href="http://www.tigris.org">tigris.org</a>.
+Many thanks to Greg Noel and Kevin Maples for making this happen.
+</p>
+
<p>
<strong>27 April 2006:</strong>
SCons has been accepted as a Google