db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@apache.org
Subject svn commit: r405511 - in /db/derby/site/trunk: build/site/DerbyBugGuidelines.html build/site/binaries/FilingDerbyIssuesInJira.pdf src/documentation/content/xdocs/DerbyBugGuidelines.html src/documentation/content/xdocs/binaries/FilingDerbyIssuesInJira.pdf
Date Tue, 09 May 2006 19:19:14 GMT
Author: jta
Date: Tue May  9 12:19:11 2006
New Revision: 405511

URL: http://svn.apache.org/viewcvs?rev=405511&view=rev
Log:
DERBY-1171: Added the FilingDerbyIssuesInJira.pdf file with a link to it
from DerbyBugGuidelines.html. PDF contributed by billrobertson42@yahoo.com.

Added:
    db/derby/site/trunk/build/site/binaries/FilingDerbyIssuesInJira.pdf   (with props)
    db/derby/site/trunk/src/documentation/content/xdocs/binaries/FilingDerbyIssuesInJira.pdf
  (with props)
Modified:
    db/derby/site/trunk/build/site/DerbyBugGuidelines.html
    db/derby/site/trunk/src/documentation/content/xdocs/DerbyBugGuidelines.html

Modified: db/derby/site/trunk/build/site/DerbyBugGuidelines.html
URL: http://svn.apache.org/viewcvs/db/derby/site/trunk/build/site/DerbyBugGuidelines.html?rev=405511&r1=405510&r2=405511&view=diff
==============================================================================
--- db/derby/site/trunk/build/site/DerbyBugGuidelines.html (original)
+++ db/derby/site/trunk/build/site/DerbyBugGuidelines.html Tue May  9 12:19:11 2006
@@ -134,10 +134,10 @@
 <a name="N10035"></a><a name="Introduction"></a>
 <h2 class="boxed">Introduction</h2>
 <div class="section">
-<p>This document is suggested reading for anyone who wants to enter a bug against Derby.
It explains how to go about filing a bug and what information you should provide to make the
bug entry useful to a developer attempting to fix it. For information on filing other issues
in Jira (enhancements, improvements etc.) and for a detailed description of some of the less
understood concepts and data fields in Jira, please read the document titled <a href="binaries/FilingDerbyIssuesInJira.doc">Filing
Apache Derby Issues in Jira</a>.</p>
+<p>This document is suggested reading for anyone who wants to enter a bug against Derby.
It explains how to go about filing a bug and what information you should provide to make the
bug entry useful to a developer attempting to fix it. For information on filing other issues
in Jira (enhancements, improvements etc.) and for a detailed description of some of the less
understood concepts and data fields in Jira, please read the document titled <em>Apache
Derby Issues in Jira</em> [<a href="binaries/FilingDerbyIssuesInJira.doc">doc</a>,
<a href="binaries/FilingDerbyIssuesInJira.pdf">PDF</a>].</p>
 <p>Derby issues are maintained at <a class="external" href="http://issues.apache.org/jira/browse/DERBY">http://issues.apache.org/jira/browse/DERBY</a>.
Suggested actions to take before/while filing a bug are listed in the sections below.</p>
 </div>
-<a name="N10045"></a><a name="Login+to+Jira%2FRequest+a+Jira+userid"></a>
+<a name="N1004C"></a><a name="Login+to+Jira%2FRequest+a+Jira+userid"></a>
 <h2 class="boxed">Login to Jira/Request a Jira userid</h2>
 <div class="section">
 <p>You may access Jira at</p>
@@ -146,12 +146,12 @@
 </p>
 <p>If you do not have a userid, create one. A "Signup" link has been provided on the
login page. There are 2 levels of access to Derby issues in Jira, "user" access and "developer"
access. A "user" may open a bug but will not be able to edit/update/assign it. This requires
"developer" privileges. If you think you will need to edit/update a bug entry, please send
an email to <a class="external" href="mailto:derby-dev@db.apache.org">derby-dev@db.apache.org</a>
requesting that you be added in to the "derby-developers" group in Jira.</p>
 </div>
-<a name="N10055"></a><a name="Search+Jira+for+an+existing+bug+report"></a>
+<a name="N1005C"></a><a name="Search+Jira+for+an+existing+bug+report"></a>
 <h2 class="boxed">Search Jira for an existing bug report</h2>
 <div class="section">
 <p>Before filing a new bug, it is recommended that you first search Jira to verify
that it has not yet been reported. Jira offers various fields (and combinations thereof) that
you can search on. You will probably benefit the most by searching on keywords that are relevant
to the bug you are intending to report. For more details on how to search, see the document
titled <a href="binaries/FilingDerbyIssuesInJira.doc">Filing Apache Derby Issues in
Jira</a>.</p>
 </div>
-<a name="N1005F"></a><a name="Post+your+bug+to+the+mailing+lists"></a>
+<a name="N10066"></a><a name="Post+your+bug+to+the+mailing+lists"></a>
 <h2 class="boxed">Post your bug to the mailing lists</h2>
 <div class="section">
 <p>If the bug you are intending to report is not already logged in Jira, it may be
a good idea to post a query to the <a class="external" href="mailto:derby-user@db.apache.org">derby-user@db.apache.org</a>
mail list asking the following:</p>
@@ -161,7 +161,7 @@
 <p>- if relevant, why you think the bug is a "blocker" (highest priority)</p>
 <p>Note: Posting to the mail lists should not be seen as an alternative to filing the
bug in Jira. This step may be viewed as optional, however you should at least search Jira
for an existing bug report.</p>
 </div>
-<a name="N10073"></a><a name="File+your+bug"></a>
+<a name="N1007A"></a><a name="File+your+bug"></a>
 <h2 class="boxed">File your bug</h2>
 <div class="section">
 <p>When you post a new bug to the mail lists, please pay attention to the following
details that make it a "useful" post. These simple guidelines help avoid poorly filed/described
bugs:</p>
@@ -172,13 +172,13 @@
 <p>- Include any relevant output from the derby.log file. If this information is too
confusing for you to understand and the file isn't too big, you may want to attach it to your
bug entry</p>
 <p>Provide error information such as SQLSTATE and nested exceptions reported by Derby.
Usually, Derby would generate chained exceptions (nested), so you should write applications
that traverse the chains with the getNextException() method call in your exception reporting
code. If you are not using a JDBC application, you should report the series of nested exceptions
(if generated) displayed on your error console.</p>
 </div>
-<a name="N10085"></a><a name="%22Close%22+your+bug+once+it+is+%22Resolved%22"></a>
+<a name="N1008C"></a><a name="%22Close%22+your+bug+once+it+is+%22Resolved%22"></a>
 <h2 class="boxed">"Close" your bug once it is "Resolved"</h2>
 <div class="section">
 <p>As the submitter of a bug, it is your responsibility to verify a bug fix and "Close"
the issue. Once fixed, a developer marks the bug as "Resolved" with a resolution of "Fixed".
You need to then go back and "Close" the issue, provided you agree the bug has been fixed.
If the resolution of the bug is something other than "Fixed" and you disagree, or the fix
submitted did not really resolve the issue, you need to "Reopen" the issue. Please add relevant
comments in Jira when doing these operations. See the document titled <a href="binaries/FilingDerbyIssuesInJira.doc">Filing
Apache Derby Issues in Jira</a> for additional details.</p>
 <p>Note that once you file your bug, Jira will generate a notification email to the
derby-dev@db.apache.org mail list.</p>
 </div>
-<a name="N10091"></a><a name="For+more+information"></a>
+<a name="N10098"></a><a name="For+more+information"></a>
 <h2 class="boxed">For more information</h2>
 <div class="section">
 <p>You may want to read the document titled <a href="binaries/FilingDerbyIssuesInJira.doc">Filing
Apache Derby Issues in Jira</a> for additional details on the following concepts:</p>
@@ -200,7 +200,7 @@
 </li>
 </ul>
 <p>
-<em>Last updated: Nov 9, 2004</em>
+<em>Last updated: May 9, 2006</em>
 </p>
 </div>
 </div>

Added: db/derby/site/trunk/build/site/binaries/FilingDerbyIssuesInJira.pdf
URL: http://svn.apache.org/viewcvs/db/derby/site/trunk/build/site/binaries/FilingDerbyIssuesInJira.pdf?rev=405511&view=auto
==============================================================================
Binary file - no diff available.

Propchange: db/derby/site/trunk/build/site/binaries/FilingDerbyIssuesInJira.pdf
------------------------------------------------------------------------------
    svn:mime-type = application/pdf

Modified: db/derby/site/trunk/src/documentation/content/xdocs/DerbyBugGuidelines.html
URL: http://svn.apache.org/viewcvs/db/derby/site/trunk/src/documentation/content/xdocs/DerbyBugGuidelines.html?rev=405511&r1=405510&r2=405511&view=diff
==============================================================================
--- db/derby/site/trunk/src/documentation/content/xdocs/DerbyBugGuidelines.html (original)
+++ db/derby/site/trunk/src/documentation/content/xdocs/DerbyBugGuidelines.html Tue May  9
12:19:11 2006
@@ -19,8 +19,10 @@
 developer attempting to fix it. For information on filing other
 issues in Jira (enhancements, improvements etc.) and for a detailed
 description of some of the less understood concepts and data fields
-in Jira, please read the document titled <A HREF="binaries/FilingDerbyIssuesInJira.doc">Filing
-Apache Derby Issues in Jira</A>.</P>
+in Jira, please read the document titled 
+<em>Apache Derby Issues in Jira</em>
+[<A HREF="binaries/FilingDerbyIssuesInJira.doc">doc</A>,
+<a href="binaries/FilingDerbyIssuesInJira.pdf">PDF</a>].</P>
 
 <P>
 Derby issues are maintained at
@@ -139,6 +141,6 @@
 	<LI><P>What to do to avoid a poorly constructed bug entry</P>
 </UL>
 
-<p><em>Last updated: Nov 9, 2004</em></p>
+<p><em>Last updated: May 9, 2006</em></p>
 </BODY>
 </HTML>=

Added: db/derby/site/trunk/src/documentation/content/xdocs/binaries/FilingDerbyIssuesInJira.pdf
URL: http://svn.apache.org/viewcvs/db/derby/site/trunk/src/documentation/content/xdocs/binaries/FilingDerbyIssuesInJira.pdf?rev=405511&view=auto
==============================================================================
Binary file - no diff available.

Propchange: db/derby/site/trunk/src/documentation/content/xdocs/binaries/FilingDerbyIssuesInJira.pdf
------------------------------------------------------------------------------
    svn:mime-type = application/pdf



Mime
View raw message