jmeter-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1723868 - /jmeter/trunk/xdocs/issues.xml
Date Sat, 09 Jan 2016 18:11:35 GMT
Author: pmouawad
Date: Sat Jan  9 18:11:35 2016
New Revision: 1723868

Improve and clarify issues page


Modified: jmeter/trunk/xdocs/issues.xml
--- jmeter/trunk/xdocs/issues.xml (original)
+++ jmeter/trunk/xdocs/issues.xml Sat Jan  9 18:11:35 2016
@@ -29,11 +29,11 @@ Before creating a new issue, please chec
 It's also worth checking first on the JMeter user mailing list; others may already have a
-<section name="Known Bugs">
+<section name="Known Bugs and enhancements">
 <a href=";order=relevance+desc&amp;bug_status=__open__&amp;product=JMeter&amp;content=">
-Bugzilla - All open bugs</a>
+Bugzilla - All open bugs and enhancements</a>
 <a href=";bug_status=ASSIGNED&amp;bug_status=REOPENED&amp;bug_status=NEEDINFO&amp;bug_severity=Blocker&amp;bug_severity=Critical&amp;bug_severity=Major&amp;bug_severity=Normal&amp;bug_severity=Regression&amp;bug_severity=Minor&amp;bug_severity=Trivial&amp;product=JMeter&amp;cmdtype=doit&amp;order=Bug+Number">
@@ -80,7 +80,11 @@ main Bugzilla page: <a href="https://bz.
 Make sure you read and understand the information on the account creation page before signing
-Once logged in, click "<code>File a bug</code>" and select JMeter from the list.
+Once logged in you have 2 options:
+    <li>At the bottom left of the screen click '<code>File a new bug in the "JMeter"
product</code>' link</li>
+    <li>At the top left of the screen, click "<code>New</code>" link and
select JMeter from the list.</li>
 <section name="Required Information for bug reporting">
@@ -99,6 +103,8 @@ Use the checklist below to guide you.
 Does it happen every time?
 <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>When a bug is market as <code>NEEDINFO</code>, please provide as soon
as possible the required information so that bug can be understood and fixed. Be aware that
+no information is provided after team requires more information and bug is not reproductible,
then bug will be closed as <code>WORKSFORME</code>. You can always reopen it later
once you provide the required information.</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
 If using Eclipse, please set the patch root to "<code>Project</code>", not the
default "<code>Workspace</code>" which is harder to apply.</li>

View raw message