@@ -11,7 +11,7 @@ __Jump To:__
11
11
* [ Additional Resources] ( #additional-resources )
12
12
13
13
## Bug Reports
14
- Bug reports are accepted through the [ Issues ] [ issues ] page.
14
+ Bug reports are accepted through the [ this ] [ bug-report ] page.
15
15
16
16
The following labels are used to track bug related issues: [ Bug] [ label-bug ] ,
17
17
[ Documentation Issue] [ label-doc-issue ] .
@@ -20,7 +20,7 @@ The following labels are used to track bug related issues: [Bug][label-bug],
20
20
Before submitting a bug report, please do the following:
21
21
22
22
1 . Do a search through the existing issues to make sure it has not already been
23
- reported. If there's an existing one, be sure give a +1 reaction which will
23
+ reported. If there's an existing one, be sure give a 👍 reaction which will
24
24
help us prioritize which issues to address first.
25
25
26
26
2 . If possible, upgrade to the latest release of the SDK. The SDK has a near
@@ -33,7 +33,7 @@ If, after doing the above steps, you determine that you need to submit a bug
33
33
report, refer to the next section.
34
34
35
35
### Submitting a Bug Report
36
- So that we are able to assist you as effectively as possible with the issue,
36
+ So that we are able to assist you as effectively as possible with the issue,
37
37
please ensure that your bug report has the following:
38
38
39
39
* A short, descriptive title. Ideally, other community members should be able
@@ -51,8 +51,7 @@ please ensure that your bug report has the following:
51
51
stacktraces.
52
52
53
53
## Feature Requests
54
- Like bug reports, feature requests are submitted through the [ Issues] [ issues ]
55
- page.
54
+ Feature requests are submitted through the [ this] [ feature-request ] page.
56
55
57
56
As with Bug Reports, please do a search of the open requests first before
58
57
submitting a new one to avoid duplicates. If you find an existing one, give it
@@ -65,7 +64,7 @@ the right design and that it makes sense to include in the SDK. Keep in mind
65
64
that other concerns like source and binary compatibility will also play a
66
65
deciding factor.
67
66
68
- Feature requests are labeled with [ Feature Request ] [ label-feature-request ] .
67
+ Feature requests are labeled with [ feature-request ] [ label-feature-request ] .
69
68
70
69
### Submitting a Feature Request
71
70
Open an [ issue] [ issues ] with the following:
@@ -118,7 +117,7 @@ checklist below:
118
117
119
118
* [ ] Includes tests to exercise the new behavior
120
119
* [ ] Code is documented, especially public and user-facing constructs
121
- * [ ] Local run of ` mvn install ` succeeds
120
+ * [ ] Local run of ` ./mvnw package ` (Linux) or ` ./mvnw.cmd package ` (Windows) succeeds
122
121
* [ ] Git commit message is detailed and includes context behind the change
123
122
* [ ] If the change is related to an existing Bug Report or Feature Request,
124
123
the issue number is referenced
@@ -148,25 +147,21 @@ days, especially if it's a large or complex one. If, after a week, your Pull
148
147
Request has not had any engagement from the SDK team, feel free to ping a
149
148
member to ask for a review.
150
149
151
- If your branch has more than one commit when it's approved, you will also be
152
- asked to [ squash] [ git-rewriting-history ] them into a single commit before it is
153
- merged in.
154
-
155
150
## Additional Resources
156
151
We maintain [ docs] ( docs/README.md ) where information like design decisions, internal
157
152
architecture, and style conventions are documented that you may find helpful
158
153
when contributing to the SDK.
159
154
160
- ## Getting in Contact
161
- * Come chat with us on [ Gitter] [ gitter ] !
162
155
163
156
[ license ] : ./LICENSE.txt
164
157
[ mwe ] : https://en.wikipedia.org/wiki/Minimal_Working_Example
165
158
[ markdown ] : https://guides.github.com/features/mastering-markdown/
166
159
[ issues ] : https://github.com/aws/aws-sdk-java-v2/issues
167
160
[ pull-requests ] : https://github.com/aws/aws-sdk-java-v2/pulls
168
- [ label-bug ] : https://github.com/aws/aws-sdk-java-v2/labels/Bug
169
- [ label-doc-issue ] : https://github.com/aws/aws-sdk-java-v2/labels/Documentation%20Issue
170
- [ label-feature-request ] : https://github.com/aws/aws-sdk-java-v2/labels/Feature%20Request
161
+ [ label-bug ] : https://github.com/aws/aws-sdk-java-v2/labels/bug
162
+ [ label-doc-issue ] : https://github.com/aws/aws-sdk-java-v2/labels/documentation
163
+ [ label-feature-request ] : https://github.com/aws/aws-sdk-java-v2/labels/feature-request
171
164
[ git-rewriting-history ] : https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History
172
165
[ gitter ] : https://gitter.im/aws/aws-sdk-java-v2
166
+ [ bug-report ] : https://github.com/aws/aws-sdk-java-v2/issues/new?assignees=&labels=bug%2Cneeds-triage&template=bug-report.yml&title=%28short+issue+description%29
167
+ [ feature-request ] : https://github.com/aws/aws-sdk-java-v2/issues/new?assignees=&labels=feature-request%2Cneeds-triage&template=feature-request.yml&title=%28short+issue+description%29
0 commit comments