-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve issue management (closes #346). #347
Conversation
Thanks for your PR. The following commands are available:
These commands can only be run by members of the vmware-tanzu organization. |
Some of the file changes in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Adding Abhishek who wrote most of the original contributing.md guide
I think you're the only one who will be able to edit the graffle file :)
This does not document our commands for running tests, (/test-all
, etc.) but these are likely to change in the near future and postponing to a future PR is likely the right thing to do.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
found 2 more typos as I was giving this a second read through
Thanks for your PR. The following commands are available:
These commands can only be run by members of the vmware-tanzu organization. |
/skip-all |
Thanks for your PR. The following commands are available:
These commands can only be run by members of the vmware-tanzu organization. |
2 similar comments
Thanks for your PR. The following commands are available:
These commands can only be run by members of the vmware-tanzu organization. |
Thanks for your PR. The following commands are available:
These commands can only be run by members of the vmware-tanzu organization. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did another thorough review of this. LGTM, apart from a few things I pointed out. This has been opened for a while, so hopefully we can merge it soon.
docs/github-labels.md
Outdated
| Label | Description | Added By | | ||
|-------|-------------|----------| | ||
| approved | Indicates a PR has been approved by OWNERS in accordance with [GOVERNANCE.md](GOVERNANCE.md) guidelines. | Maintainers | | ||
| vmware-cla: no | Indicates the PR's author has not signed the (VMware CLA)[https://cla.vmware.com/faq] | VMware CLA Bot | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The link does not render properly: there can be no whitespace between (VMware CLA)
and [https://cla.vmware.com/faq]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Corrected.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
still not fixed (when I look at the Github markdown rendering for the file), maybe they need to be on the same line...
docs/github-labels.md
Outdated
|-------|-------------|----------| | ||
| approved | Indicates a PR has been approved by OWNERS in accordance with [GOVERNANCE.md](GOVERNANCE.md) guidelines. | Maintainers | | ||
| vmware-cla: no | Indicates the PR's author has not signed the (VMware CLA)[https://cla.vmware.com/faq] | VMware CLA Bot | | ||
| vmware-cla: yes | Indicates the PR's author has signed the (VMware CLA)[https://cla.vmware.com/faq] | VMware CLA Bot | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
corrected.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same
fae87c1
to
a96c7fb
Compare
Thanks for your PR. The following commands are available:
These commands can only be run by members of the vmware-tanzu organization. |
/skip-all |
The forced push was due to a rebase to ensure we are reviewing latest set of docs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another thorough review and found a few more typos
The CI spell checker also found a couple
CONTRIBUTING.md
Outdated
Once an issue has been submitted, the CI (GitHub actions) or a human will | ||
automatically review the submitted issue or PR to ensure that it has all relevant | ||
information. If information is lacking or there is another problem with the | ||
submitted issue, an appropriate [`triage/<?>`](#triage) label will be |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not a valid link, there is no triage
section in this doc
CONTRIBUTING.md
Outdated
applied. | ||
|
||
After an issue has been triaged, the maintainers can prioritize the issue with | ||
an appropriate [`priority/<?>`](#priority) label. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not a valid link, there is no priority
section in this doc
CONTRIBUTING.md
Outdated
* [`kind/feature`](docs/issue-management.md#feature) -- for proposing a feature | ||
* [`kind/support`](docs/issue-management.md#support) -- to request support. You may also get support by | ||
using our [Slack](https://kubernetes.slack.com/archives/CR2J23M0X) channel for | ||
interactive help. If you have not setup the appropriate accounts, please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: s/setup/set up
setup is the noun, set up is the verb
docs/github-labels.md
Outdated
| Label | Description | Added By | | ||
|-------|-------------|----------| | ||
| approved | Indicates a PR has been approved by OWNERS in accordance with [GOVERNANCE.md](GOVERNANCE.md) guidelines. | Maintainers | | ||
| vmware-cla: no | Indicates the PR's author has not signed the (VMware CLA)[https://cla.vmware.com/faq] | VMware CLA Bot | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
still not fixed (when I look at the Github markdown rendering for the file), maybe they need to be on the same line...
docs/github-labels.md
Outdated
|-------|-------------|----------| | ||
| approved | Indicates a PR has been approved by OWNERS in accordance with [GOVERNANCE.md](GOVERNANCE.md) guidelines. | Maintainers | | ||
| vmware-cla: no | Indicates the PR's author has not signed the (VMware CLA)[https://cla.vmware.com/faq] | VMware CLA Bot | | ||
| vmware-cla: yes | Indicates the PR's author has signed the (VMware CLA)[https://cla.vmware.com/faq] | VMware CLA Bot | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same
docs/issue-management.md
Outdated
processes. | ||
* `help wanted` -- issues that represent clearly laid out tasks that are | ||
generally tractable for new contributors. The solution has already been | ||
designed and requires no further discussion from the community. This labels |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/This labels/This label
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
corrected.
docs/issue-management.md
Outdated
3. Apply [`size/<size>`](#size) label to the submission. (TODO: we plan to | ||
automate this with a GitHub action and apply size based on lines of code). | ||
4. Ensure that the PR references an existing issue (exceptions to this should be | ||
rare). If the PR is missing this or needs any additional information, notate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought "notate" was used specifically for music. Maybe "note it in a comment"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are correct. Changed.
docs/issue-management.md
Outdated
|
||
### Size | ||
|
||
Size labels beting with `size/<size>` and estimate the relative complexity or work |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/beting/begin
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Corrected. Not sure why spell check plugin not picking this up. Will investigate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's my understanding that the spell checker only catches the most common spelling mistakes and does not lookup each work in a dictionary, as I would image there would be too many false positives for technical documentation.
docs/issue-management.md
Outdated
|
||
### Triage | ||
|
||
As soon as new issue are submitted, they must be triaged until they are ready to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/new issue are submitted, they/new issues are submitted, they
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
corrected.
docs/issue-management.md
Outdated
TODO: Additional CI automation (GitHub actions) will be used to automatically | ||
apply and manage some of these lifecycle labels. | ||
|
||
Lifecycle labels are defined in [`docs/github-labels.md`](docs/github-labels.md). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
link not working because of missing leading slash
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should have relative link so this work correctly in site docs. Have corrected.
/skip-all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@McCodeman actually looks like you haven't fixed the errors reported by the spell checker yet? |
* Added a new `docs/labels.md` to reference all labels used in GitHub issues and pull requests. * Added a visual developer workflow diagram at `docs/assets/developer-workflow-opaque-bg.png` (original src graffle added as well). * Updated `CONTRIBUTING.md` to reflect the improved issue management process.
* whitespace, punctuation, and spelling corrections * wording on purpose of size labels * removed /approve-api-change until action ready * added and changed area github labels for OVS and testing * instructions apply to both issues and PRs * changed name of labels.md to github-labels.md
* moved issue-management detail topics in `CONTRIBUTING.md` to `docs/issue-management.md` * grammar, spelling, formatting corrections * requested information for upgrades on `kind/api-change` * updated links to `github-labels.md`
* spelling, grammar, formatting, typo corrections
* corrected typos
* simplified the section on filing-an-issue by merging with a previous section on new issues * consistent reference to "maintainers" and "owners" * fixed broken links
127ce24
to
0e80588
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/skip-all |
Ignoring failed Kind test because this is purely a documentation PR |
* Improve issue management (closes antrea-io#346). * Added a new `docs/labels.md` to reference all labels used in GitHub issues and pull requests. * Added a visual developer workflow diagram at `docs/assets/developer-workflow-opaque-bg.png` (original src graffle added as well). * Updated `CONTRIBUTING.md` to reflect the improved issue management process. * Added newline to end of .gitignore * Typo fixes and suggestions for CONTRIBUTING.md and github-labels.md * whitespace, punctuation, and spelling corrections * wording on purpose of size labels * removed /approve-api-change until action ready * added and changed area github labels for OVS and testing * instructions apply to both issues and PRs * changed name of labels.md to github-labels.md * Moved issue management detail topics to `docs/issue-management.md` * moved issue-management detail topics in `CONTRIBUTING.md` to `docs/issue-management.md` * grammar, spelling, formatting corrections * requested information for upgrades on `kind/api-change` * updated links to `github-labels.md` * Clarify good first issue and help wanted labels. * spelling, grammar, formatting, typo corrections * Added `area/component` labels. * Added github label `area/interface` * Added label `area/build-release` * Corrected developer workflow visualization URL * corrected typos * Removed spurious asterix in priority bullet list * Added `area/monitoring/health-performance * Added link for how to use good first issue and help wanted. * Spelling/typo corrections to issue-management. * Documentation edits based on feedback * simplified the section on filing-an-issue by merging with a previous section on new issues * consistent reference to "maintainers" and "owners" * fixed broken links * Fixed additional spelling, grammar, links. * Fixed spelling errors.
docs/labels.md
to reference all labels used inGitHub issues and pull requests.
docs/assets/developer-workflow-opaque-bg.png
(original srcgraffle added as well).
CONTRIBUTING.md
to reflect the improved issuemanagement process.