forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r359392 - in /forrest/site: broken-links.xml forrest-issues.html forrest-issues.pdf issues.html issues.pdf
Date Wed, 28 Dec 2005 04:39:21 GMT
Author: crossley
Date: Tue Dec 27 20:39:14 2005
New Revision: 359392

URL: http://svn.apache.org/viewcvs?rev=359392&view=rev
Log:
Automatic publish from forrestbot

Modified:
    forrest/site/broken-links.xml
    forrest/site/forrest-issues.html
    forrest/site/forrest-issues.pdf
    forrest/site/issues.html
    forrest/site/issues.pdf

Modified: forrest/site/broken-links.xml
URL: http://svn.apache.org/viewcvs/forrest/site/broken-links.xml?rev=359392&r1=359391&r2=359392&view=diff
==============================================================================
--- forrest/site/broken-links.xml (original)
+++ forrest/site/broken-links.xml Tue Dec 27 20:39:14 2005
@@ -1,2 +1,5 @@
 <broken-links>
+  <link message="/svn/asf/forrest/site-author/./content/xdocs/images.docs_0_60/howto/bugzilla-patch/bugzilla-screen.gif
(No such file or directory)" uri="docs_0_60/howto/bugzilla-patch/my-images/bugzilla-screen.gif">
+    <referrer uri="docs_0_60/howto/bugzilla-patch/howto-bugzilla-patch.html"/>
+  </link>
 </broken-links>

Modified: forrest/site/forrest-issues.html
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.html?rev=359392&r1=359391&r2=359392&view=diff
==============================================================================
--- forrest/site/forrest-issues.html (original)
+++ forrest/site/forrest-issues.html Tue Dec 27 20:39:14 2005
@@ -195,9 +195,6 @@
 <a href="#%5BFOR-762%5D+Default+page+URL+for+breadcrumbs+and+site%3A+links">[FOR-762]
Default page URL for breadcrumbs and site: links</a>
 </li>
 <li>
-<a href="#%5BFOR-707%5D+Document+i18n+features+of+Forrest">[FOR-707] Document i18n
features of Forrest</a>
-</li>
-<li>
 <a href="#%5BFOR-711%5D+Cache+results+from+the+Locationmap">[FOR-711] Cache results
from the Locationmap</a>
 </li>
 <li>
@@ -210,6 +207,9 @@
 <a href="#%5BFOR-388%5D+Use+plugins+in-place+if+src+available">[FOR-388] Use plugins
in-place if src available</a>
 </li>
 <li>
+<a href="#%5BFOR-707%5D+Document+i18n+features+of+Forrest">[FOR-707] Document i18n
features of Forrest</a>
+</li>
+<li>
 <a href="#%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes">[FOR-241]
character entities (e.g. ampersand) are expanded again for href or src attributes</a>
 </li>
 <li>
@@ -338,27 +338,7 @@
 &lt;br&gt;
 Cocoon does not appear to assume the end node directory is index.* and thus appends no file
automatically as tomcat or the http server does so it must be manually done. </p>
 </div>
-<a name="N1003B"></a><a name="%5BFOR-707%5D+Document+i18n+features+of+Forrest"></a>
-<h2 class="underlined_10">[FOR-707] Document i18n features of Forrest</h2>
-<div class="section">
-<p>
-<a href="http://issues.apache.org/jira/browse/FOR-707">http://issues.apache.org/jira/browse/FOR-707</a>
-</p>
-<p>There is next to no documentation about i18n, just a pretty poor FAQ entry that
points at an issue that has now been closed.
-&lt;br&gt;
-
-&lt;br&gt;
-Cheche wrote a blog entry on his work:
-&lt;br&gt;
-
-&lt;br&gt;
-&lt;a href="http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/"&gt;http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/&lt;/a&gt;
-&lt;br&gt;
-
-&lt;br&gt;
-We could, at the very least use the locationmap to pull this content into our site [OT: I
wonder if this could be a way to generate more documentation?)</p>
-</div>
-<a name="N10049"></a><a name="%5BFOR-711%5D+Cache+results+from+the+Locationmap"></a>
+<a name="N1003B"></a><a name="%5BFOR-711%5D+Cache+results+from+the+Locationmap"></a>
 <h2 class="underlined_10">[FOR-711] Cache results from the Locationmap</h2>
 <div class="section">
 <p>
@@ -374,7 +354,7 @@
 &lt;br&gt;
 If we test all locationmaps and find no result we should record that tere is no result in
this hashmap. This will also be a good place to throw an exception so that Cocoon can better
report such errors (see FOR-701)</p>
 </div>
-<a name="N10057"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
+<a name="N10049"></a><a name="%5BFOR-742%5D+trouble+accessing+unversioned+plugin+for+a+released+version+of+Forrest%2C+e.g.+projectInfo"></a>
 <h2 class="underlined_10">[FOR-742] trouble accessing unversioned plugin for a released
version of Forrest, e.g. projectInfo</h2>
 <div class="section">
 <p>
@@ -388,7 +368,7 @@
 &lt;br&gt;
 &lt;a href="http://marc.theaimsgroup.com/?t=113176328300002"&gt;http://marc.theaimsgroup.com/?t=113176328300002&lt;/a&gt;</p>
 </div>
-<a name="N10065"></a><a name="%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode"></a>
+<a name="N10057"></a><a name="%5BFOR-735%5D+Plugins+are+not+correctly+deployed+in+webapp+mode"></a>
 <h2 class="underlined_10">[FOR-735] Plugins are not correctly deployed in webapp mode</h2>
 <div class="section">
 <p>
@@ -404,7 +384,7 @@
 &lt;br&gt;
 - the pdf links give an error &amp;quot;Resource Not Found&amp;quot;</p>
 </div>
-<a name="N10073"></a><a name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
+<a name="N10065"></a><a name="%5BFOR-388%5D+Use+plugins+in-place+if+src+available"></a>
 <h2 class="underlined_10">[FOR-388] Use plugins in-place if src available</h2>
 <div class="section">
 <p>
@@ -419,6 +399,26 @@
 
 &lt;br&gt;
 </p>
+</div>
+<a name="N10073"></a><a name="%5BFOR-707%5D+Document+i18n+features+of+Forrest"></a>
+<h2 class="underlined_10">[FOR-707] Document i18n features of Forrest</h2>
+<div class="section">
+<p>
+<a href="http://issues.apache.org/jira/browse/FOR-707">http://issues.apache.org/jira/browse/FOR-707</a>
+</p>
+<p>There is next to no documentation about i18n, just a pretty poor FAQ entry that
points at an issue that has now been closed.
+&lt;br&gt;
+
+&lt;br&gt;
+Cheche wrote a blog entry on his work:
+&lt;br&gt;
+
+&lt;br&gt;
+&lt;a href="http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/"&gt;http://casa.che-che.com/blog/2005/05/10/internalization-a-site-using-forrest-07-dev/&lt;/a&gt;
+&lt;br&gt;
+
+&lt;br&gt;
+We could, at the very least use the locationmap to pull this content into our site [OT: I
wonder if this could be a way to generate more documentation?)</p>
 </div>
 <a name="N10081"></a><a name="%5BFOR-241%5D+character+entities+%28e.g.+ampersand%29+are+expanded+again+for+href+or+src+attributes"></a>
 <h2 class="underlined_10">[FOR-241] character entities (e.g. ampersand) are expanded
again for href or src attributes</h2>

Modified: forrest/site/forrest-issues.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/forrest-issues.pdf?rev=359392&r1=359391&r2=359392&view=diff
==============================================================================
Binary files - no diff available.

Modified: forrest/site/issues.html
URL: http://svn.apache.org/viewcvs/forrest/site/issues.html?rev=359392&r1=359391&r2=359392&view=diff
==============================================================================
--- forrest/site/issues.html (original)
+++ forrest/site/issues.html Tue Dec 27 20:39:14 2005
@@ -182,30 +182,195 @@
 	          &nbsp;<input value="-a" class="smallerfont" title="Shrink text" onclick="ndeSetTextSize('decr');
return false;" type="button">
 	          &nbsp;<input value="+a" class="biggerfont" title="Enlarge text" onclick="ndeSetTextSize('incr');
return false;" type="button">
 </div>
-<h1>Apache Forrest issue tracker</h1> 
+<h1>Apache Forrest issue tracker</h1>
+<div id="minitoc-area">
+<ul class="minitoc">
+<li>
+<a href="#intro">Introduction</a>
+</li>
+<li>
+<a href="#guide">Guidelines and hints for reporting issues</a>
+<ul class="minitoc">
+<li>
+<a href="#priority">Special fields: Priority (a.k.a. Severity)</a>
+</li>
+<li>
+<a href="#urgency">Special fields: Urgency</a>
+</li>
+<li>
+<a href="#permissions">Permissions</a>
+</li>
+</ul>
+</li>
+<li>
+<a href="#filters">Some search filters</a>
+</li>
+</ul>
+</div>
+
   
+<a name="N1000D"></a><a name="intro"></a>
+<h2 class="underlined_10">Introduction</h2>
+<div class="section">
 <p>
-    The Apache Forrest uses an issue tracker call Jira.
+    The Apache Forrest uses an issue tracker call Jira. All of the project
+    contributions should go there (not to the mailing list). This enables us to
+    keep track of contributions and to classify and manage the issues.
   </p>
-
-  
 <p>
     
 <a href="http://issues.apache.org/jira/browse/FOR">http://issues.apache.org/jira/browse/FOR</a>
-  
-</p>
-
-  
+    is the main entry point which provides access to enter, view, search, and
+    add additional comments to issues. There are some additional search
+    <a href="#filters">filters</a> provided below.
+  </p>
 <p>
     You need to set up an account there before you can create new issues or
     add comments to existing issues.
+    Anyone can register as a user and report issues.
+    See <a href="#guide">guidelines</a> below.
   </p>
-
-  
 <p>
     Note that the issue tracker is not a discussion or user help forum.
-    Please discuss issues with using Forrest on the user or dev mailing list.
+    Please discuss issues about using Forrest on the user or dev mailing list.
   </p>
+</div>
+
+  
+<a name="N1002C"></a><a name="guide"></a>
+<h2 class="underlined_10">Guidelines and hints for reporting issues</h2>
+<div class="section">
+<ul>
+      
+<li>Follow the prompts below each entry field.</li>
+      
+<li>If you don't know the answer to a particular question, then
+        leave the field blank.</li>
+      
+<li>Add a concise initial Description, then add more Comments later to
+        further describe the issue.</li>
+      
+<li>Other people will follow up and enhance your description and
+        classifications.</li>
+      
+<li>If details about your computing environment are relevant
+        (e.g. Java version or operating system) then add them to a Comment.</li>
+    
+</ul>
+<a name="N10044"></a><a name="priority"></a>
+<h3 class="underlined_5">Special fields: Priority (a.k.a. Severity)</h3>
+<p>
+        The Priority is the severity according to the issue reporter. This will
+        be a guideline to the development team to identify the most urgent
+        issues. It is not a guarantee that a Critical issue will be resolved
+        before a Major issue.
+      </p>
+<p>
+        Follow the Jira help icon to see the definition of the options.
+      </p>
+<a name="N10051"></a><a name="urgency"></a>
+<h3 class="underlined_5">Special fields: Urgency</h3>
+<p>
+        The project team will classify this according to their urgency. The aim is
+        to be able to see at a glance which issues should be attended to, so that
+        developers can operate efficiently and so that the product can be released
+        as soon as possible. Some issues hinder the project, so need to be identified.
+      </p>
+<p>
+        We use the following definition of the options.
+      </p>
+<ul>
+        
+<li>
+          None: The default. Not yet classified.
+        </li>
+        
+<li>
+          Blocker: Prevents other developers from working; or critical issue with functionality;
+          or holds up the implementation of other functionality.
+          Cannot release until it is fixed. Will be fixed ASAP.
+        </li>
+        
+<li>
+          Urgent: Is a key new feature; or affects many users. Will be fixed before the next
+          release.
+        </li>
+        
+<li>
+          Normal: If this issue scratches the itch of any particular developer, then
+          they should help to solve it and provide a patch.
+        </li>
+        
+<li>
+          Low: If this issue bothers you, then fix it because it is not a high priority
+          for the project.
+        </li>
+      
+</ul>
+<a name="N10070"></a><a name="permissions"></a>
+<h3 class="underlined_5">Permissions</h3>
+<ul>
+        
+<li>
+          Anyone: Browse, Find, View.
+        </li>
+        
+<li>
+          jira-users: People who have registered as a user of the ASF Jira.
+          Create, Edit, Comment, Attach, Vote, Watch.
+          The reporter can also Close.
+        </li>
+        
+<li>
+          forrest-developers: People who are Forrest committers.
+          Resolve, Close, Delete issues, Delete coments, Link, Assign, Administer Projects.
+        </li>
+        
+<li>
+          Some committers are global adminstrators: Edit user details, Add users to groups,
Configure.
+        </li>
+      
+</ul>
+</div>
+
+  
+<a name="N10087"></a><a name="filters"></a>
+<h2 class="underlined_10">Some search filters</h2>
+<div class="section">
+<p>
+      Various general searches are available from the
+      <a href="http://issues.apache.org/jira/browse/FOR">front page</a>,
+      e.g. "open issues classified by component", or "Added recently".
+      The following are some special filters.
+    </p>
+<ul>
+      
+<li>
+        
+<a href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310472">FOR-open-with-patch</a>
+        - Committers need to visit this regularly and deal with the patches.
+      </li>
+      
+<li>
+        
+<a href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310473">FOR-urgency-blocker</a>
+        - Issues that the project considers to be Blockers.
+      </li>
+      
+<li>
+        
+<a href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310475">FOR-urgency-urgent</a>
+        - Issues that the project considers to be Urgent.
+      </li>
+      
+<li>
+        
+<a href="http://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12310043">FOR-unscheduled</a>
+        - Issues that have not yet been scheduled to be fixed for a certain version.
+      </li>
+    
+</ul>
+</div>
 
 
 </div>

Modified: forrest/site/issues.pdf
URL: http://svn.apache.org/viewcvs/forrest/site/issues.pdf?rev=359392&r1=359391&r2=359392&view=diff
==============================================================================
Binary files - no diff available.



Mime
View raw message