You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* or ask question on [stackoverflow](https://stackoverflow.com/questions/tagged/jmeter).
@@ -22,8 +23,8 @@ Simply contact:
22
23
23
24
See:
24
25
25
-
*[Open bug entries for JMeter](https://bz.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&bug_severity=Blocker&bug_severity=Critical&bug_severity=Major&bug_severity=Normal&bug_severity=Regression&bug_severity=Minor&bug_severity=Trivial&product=JMeter&order=Bug%20Number&list_id=164231)
26
-
*[Enhancement requests for JMeter](https://bz.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=NEEDINFO&bug_severity=Enhancement&product=JMeter&order=Bug%20Number&list_id=164232)
26
+
*[Open issues for JMeter](https://github.com/apache/jmeter/issues)
27
+
*[Enhancement requests for JMeter](https://github.com/apache/jmeter/issues?q=is%3Aopen+label%3Aenhancement)
27
28
28
29
## Development setup
29
30
@@ -66,7 +67,7 @@ The best way to make sure your issue or feature is addressed is to submit a patc
66
67
We accept patches through:
67
68
68
69
* pull requests
69
-
* patch attached to bugzilla.
70
+
* patch attached to [JMeter developers mailing list](https://jmeter.apache.org/mail2.html#JMeterDev).
70
71
71
72
However, before sending a patch, please make sure that the following applies:
<li>Create a <ahref="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request">pull request</a></li>
125
123
</ul>
126
124
127
-
<note>Different operation systems have different defaults for end-of-line markers.
125
+
<note>Different operating systems have different defaults for end-of-line markers.
128
126
Typical configuration is CRLF for Windows and LF for macOS and GNU/Linux.<br/>
129
127
It is recommended to follow that configuration by appropriate settings of <code>core.autocrlf</code>.
130
128
For Windows <source>git config --global core.autocrlf true</source>, and for macOS and GNU/Linux set <source>git config --global core.autocrlf input</source>
@@ -134,17 +132,17 @@ Check that patch does not break JUnit tests by running:
134
132
no matter the configuration of the developer workstation.
135
133
</note>
136
134
137
-
<h3>Create a PR using Patch</h3>
135
+
<h3>Proposing a change with a patch</h3>
136
+
<p>If you cannot to create a pull request at GitHub, you might submit your changes as a unified diff patch on JMeter dev mailing list.</p>
138
137
<ul>
139
-
<li>Open a bugzilla issue, see <atarget="_blank"href="issues.html">Issues page</a></li>
140
138
<li>Checkout Apache JMeter source</li>
141
139
<li>Code your fix</li>
142
140
<li>Create your patch by Right clicking on Eclipse project and select
143
141
<menuchoice>
144
142
<guimenuitem>Team</guimenuitem>
145
143
<guimenuitem>Create Patch …</guimenuitem>
146
144
</menuchoice></li>
147
-
<li>Attach your patch to the bugzilla issue</li>
145
+
<li>Attach your patch to email message on JMeter dev list</li>
<ahref="https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls#issues-and-pull-requests">references to the other
88
+
issues and the source code</a>.
89
+
</p>
90
+
<p>
91
+
When you create an issue at GitHub, it suggests one of the templates (e.g. "<em>Bug report</em>",
92
+
"<em>Feedback about the manual</em>", "<em>Feature Request</em>", "<em>Regression</em>"), and it guides which information is required for each case.
93
+
You could read more on <ahref="https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue">creating issues</a> in
94
+
GitHub documentation.
95
+
</p>
96
+
</dd>
97
+
<dt>Mailing list discussion</dt>
98
+
<dd>
99
+
<p>
100
+
If you are not sure if something is an enhancement, or if you are unsure regarding the possible solutions,
101
+
it might be a good idea to start a discussion on <ahref="https://jmeter.apache.org/mail2.html#JMeterDev">JMeter dev mailing list</a>
102
+
</p>
103
+
</dd>
104
+
<dt>GitHub pull request</dt>
105
+
<dd>
106
+
<p>
107
+
If you are positive regarding the solution, you could start a discussion by creating a
108
+
<ahref="https://github.com/apache/jmeter/pulls">pull request on GitHub</a>.
109
+
Pull requests are not much different from issues, however, sometimes it is easier to discuss with code at hand.
110
+
For instance, if you fix a typo or make other small fixes, there's no need to create "<em>issue and PR</em>" for each change.
111
+
The following <ahref="https://github.blog/2015-01-21-how-to-write-the-perfect-pull-request/">GitHub post</a> might be helpful
112
+
for creating your perfect pull request.
113
+
</p>
114
+
<note>
115
+
There's no guarantee that your contribution will be accepted, so it might be wise to discuss your suggestions
116
+
before you invest significant efforts on implementing the changes.
117
+
</note>
118
+
<p>
119
+
If you are providing a code patch, also provide a test case, and documentation on how to use the new feature (ideally as a documentation patch).
120
+
</p>
121
+
</dd>
122
+
</dl>
123
+
</p>
77
124
</section>
78
125
<sectionname="Raising an Issue">
79
-
<p>
80
-
First check that the issue has not already been reported.
81
-
If reporting a bug, are you sure it really is a bug in JMeter, not just a misunderstanding of how JMeter works?
82
-
</p>
83
-
<p>
84
-
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
85
-
main Bugzilla page: <ahref="https://bz.apache.org/bugzilla/">https://bz.apache.org/bugzilla/</a>.
86
-
</p>
87
-
<p>
88
-
Make sure you read and understand the information on the account creation page before signing up.
89
-
</p>
90
-
<p>
91
-
Once logged in you have 2 options:
92
-
<ul>
93
-
<li>At the bottom left of the screen click '<code>File a new bug in the "JMeter" product</code>' link</li>
94
-
<li>At the top left of the screen, click "<code>New</code>" link and select JMeter from the list.</li>
95
-
</ul>
96
-
</p>
126
+
<p>
127
+
First check that the issue has not already been reported on <ahref="https://github.com/apache/jmeter/issues">GitHub issues</a>
128
+
and <ahref="https://lists.apache.org/list.html?user@jmeter.apache.org">JMeter user mailing list</a>).
129
+
If reporting a bug, are you sure it really is a bug in JMeter, not just a misunderstanding of how JMeter works?
130
+
</p>
131
+
<p>
132
+
If you face a bug or regression, please create an <ahref="https://github.com/apache/jmeter/issues">issue on GitHub</a>.
133
+
In case you can't create an issue, you might send the bug report to <ahref="https://jmeter.apache.org/mail2.html#JMeterDev">JMeter dev mailing list</a>.
134
+
</p>
97
135
</section>
98
136
<sectionname="Required Information for bug reporting">
99
137
<p>
@@ -112,11 +150,10 @@ Use the checklist below to guide you.
112
150
Does it happen every time?
113
151
</li>
114
152
<li>If you have error messages, that you wish to report, copy them as text into the issue, as it makes it easier to search for them and re-use the message in our research for the origin of the issue</li>
115
-
<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>
116
-
<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 if
117
-
no information is provided after team requires more information and bug is not reproducible, then bug will be closed as <code>WORKSFORME</code>. You can always reopen it later once you provide the required information.</li>
118
-
<li>Select accurately the IMPORTANCE level, <code>ENHANCEMENT</code> means it's not a BUG while others mean it's a BUG</li>
119
-
<li>If you are providing a patch to fix a bug, please ensure it is in unified diff format.
153
+
<li>When a bug is market as <code>need info</code>, please provide as soon as possible the required information so that bug can be understood and fixed. Be aware that if
154
+
no information is provided after team requires more information and bug is not reproducible, then bug will be closed as <code>invalid</code>. You can always ask to reopen it later once you provide the required information.</li>
155
+
<li>Prefer using issue templates (e.g. "<em>Bug report</em>", "<em>Feedback about the manual</em>", "<em>Feature Request</em>", "<em>Regression</em>")</li>
156
+
<li>If you are providing a patch file to fix a bug, please ensure it is in unified diff format.
120
157
If using Eclipse, please set the patch root to "<code>Project</code>", not the default "<code>Workspace</code>" which is harder to apply.</li>
121
158
<li>New source files can be provided as is; please ensure they have the standard Apache License header (as per other JMeter files).
122
159
Please do not use <code>@author</code> tags (credit will be given in the changes file).
@@ -125,7 +162,7 @@ Please do not use <code>@author</code> tags (credit will be given in the changes
125
162
Components are documented in <code>xdocs/usermanual/component_reference.xml</code>.</li>
126
163
</ul>
127
164
<p><b>See also the following <ahref="https://bz.apache.org/bugwritinghelp.html">Bug writing guidelines</a>,
128
-
also the terms and conditions noted on the <ahref="https://bz.apache.org/bugzilla/createaccount.cgi">Bugzilla account creation page.</a></b></p>
165
+
also the terms and conditions noted on the <ahref="https://docs.github.com/en/site-policy/github-terms/github-terms-of-service">GitHub Terms of Service</a></b></p>
0 commit comments