jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fschumac...@apache.org
Subject svn commit: r1671297 - /jmeter/trunk/xdocs/issues.xml
Date Sat, 04 Apr 2015 19:26:28 GMT
Author: fschumacher
Date: Sat Apr  4 19:26:28 2015
New Revision: 1671297

URL: http://svn.apache.org/r1671297
Log:
* More code markup changes
* Spacepolice
* Add a link to the debug sampler component reference

Modified:
    jmeter/trunk/xdocs/issues.xml

Modified: jmeter/trunk/xdocs/issues.xml
URL: http://svn.apache.org/viewvc/jmeter/trunk/xdocs/issues.xml?rev=1671297&r1=1671296&r2=1671297&view=diff
==============================================================================
--- jmeter/trunk/xdocs/issues.xml (original)
+++ jmeter/trunk/xdocs/issues.xml Sat Apr  4 19:26:28 2015
@@ -6,19 +6,19 @@
    The ASF licenses this file to You under the Apache License, Version 2.0
    (the "License"); you may not use this file except in compliance with
    the License.  You may obtain a copy of the License at
- 
+
        http://www.apache.org/licenses/LICENSE-2.0
- 
+
    Unless required by applicable law or agreed to in writing, software
    distributed under the License is distributed on an "AS IS" BASIS,
    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    See the License for the specific language governing permissions and
    limitations under the License.
 -->
-<document>   
-<properties>     
-    <title>Issues</title>   
-</properties> 
+<document>
+<properties>
+    <title>Issues</title>
+</properties>
 <body>
 <section name="Issue tracker">
 <p>
@@ -26,10 +26,10 @@ JMeter uses Bugzilla for issue tracking,
 </p>
 <p>
 Before creating a new issue, please check whether the issue has already been reported by
searching Bugzilla.
-It's also worth checking first on the JMeter user mailing list; others may already have a
solution. 
+It's also worth checking first on the JMeter user mailing list; others may already have a
solution.
 </p>
 </section>
-<section name="Known Bugs"> 
+<section name="Known Bugs">
 <ul>
 <li>
 <a href="http://bz.apache.org/bugzilla/buglist.cgi?query_format=specific&amp;order=relevance+desc&amp;bug_status=__open__&amp;product=JMeter&amp;content=">
@@ -50,15 +50,15 @@ In most cases it is worth starting a dis
 Bugzilla is good for tracking progress and supplying patches, but is unwieldy for longer
discussions.
 </p> 
 <p>
-If you have not already done so, you need to register an account first, using the "New Account"
link at the top of the
+If you have not already done so, you need to register an account first, using the "<code>New
Account</code>" link at the top of the
 main Bugzilla page: <a href="https://bz.apache.org/bugzilla/">https://bz.apache.org/bugzilla/</a>.
 </p>
 <p>
 Make sure you read and understand the information on the account creation page before signing
up.
 </p>
 <p>
-Once logged in, click "File a bug" and select JMeter from the list
-Please set the severity to "enhancement".
+Once logged in, click "<code>File a bug</code>" and select JMeter from the list
+Please set the severity to "<code>enhancement</code>".
 </p>
 <p>
 Please make sure that you describe the enhancement in sufficient detail. If necessary provide
an example use-case.
@@ -69,18 +69,18 @@ If you are providing a code patch, also
 </section>
 <section name="Raising an Issue">
 <p>
-First check that the issue has not already been reported. 
+First check that the issue has not already been reported.
 If reporting a bug, are you sure it really is a bug in JMeter, not just a misunderstanding
of how JMeter works?
 </p>
 <p>
-If you have not already done so, you need to register an account first, using the "New Account"
link at the top of the
+If you have not already done so, you need to register an account first, using the "<code>New
Account</code>" link at the top of the
 main Bugzilla page: <a href="https://bz.apache.org/bugzilla/">https://bz.apache.org/bugzilla/</a>.
 </p>
 <p>
 Make sure you read and understand the information on the account creation page before signing
up.
 </p>
 <p>
-Once logged in, click "File a bug" and select JMeter from the list.
+Once logged in, click "<code>File a bug</code>" and select JMeter from the list.
 </p>
 </section>
 <section name="Required Information for bug reporting">
@@ -90,23 +90,23 @@ Use the checklist below to guide you.
 </p>
 <ul>
 <li>JMeter version</li>
-li>Java version (output from java -version)</li>
+<li>Java version (output from <code>java -version</code>)</li>
 <li>OS version</li>
-<li>jmeter.log file (unlikely to contain sensitive information, but check before uploading)</li>
-<li>JMX file if relevant (redact any sensitive information first), providing a simplified
Test Plan (using DEBUG sampler) will ensure BUG is fixed much more rapidely than without it</li>
+<li><code>jmeter.log</code> file (unlikely to contain sensitive information,
but check before uploading)</li>
+<li>JMX file if relevant (redact any sensitive information first), providing a simplified
Test Plan (using <complink name="Debug Sampler"/>) will ensure BUG is fixed much more
rapidely than without it</li>
 <li>JTL file if relevant (may need to redact sensitive information)</li>
 <li>For a suspected bug, describe what you did, what happened, and how this differs
from what you expected to happen.
-Does it happen every time?. 
+Does it happen every time?
 </li>
-<li>Add yourself in CC List to be notified when JMeter Team requires more information
(in this case bug will be marked as NEEDINFO)</li>
-<li>Select accurately the IMPORTANCE level, ENHANCEMENT means it's not a BUG while
others mean it's a BUG</li>
+<li>Add yourself in <code>CC</code> List to be notified when JMeter Team
requires more information (in this case bug will be marked as <code>NEEDINFO</code>)</li>
+<li>Select accurately the IMPORTANCE level, <code>ENHANCEMENT</code> means
it's not a BUG while others mean it's a BUG</li>
 <li>If you are providing a patch to fix a bug, please ensure it is in unified diff
format.
-If using Eclipse, please set the patch root to "Project", not the default "Workspace" which
is harder to apply.</li>
+If using Eclipse, please set the patch root to "<code>Project</code>", not the
default "<code>Workspace</code>" which is harder to apply.</li>
 <li>New source files can be provided as is; please ensure they have the standard Apache
License header (as per other JMeter files).
-Please do not use @author tags (credit will be given in the changes file).
+Please do not use <code>@author</code> tags (credit will be given in the changes
file).
 </li>
-<li>In the case of patches for new features, please also provide documentation patches
if at all possible. 
-Components are documented in xdocs/usermanual/component_reference.xml.</li>
+<li>In the case of patches for new features, please also provide documentation patches
if at all possible.
+Components are documented in <code>xdocs/usermanual/component_reference.xml</code>.</li>
 </ul>
 <p><b>See also the following <a href="https://bz.apache.org/bugwritinghelp.html">Bug
writing guidelines</a>,
 also the terms and conditions noted on the <a href="https://bz.apache.org/bugzilla/createaccount.cgi">Bugzilla
account creation page.</a></b></p>



Mime
View raw message