| Age | Commit message (Collapse) | Author |
|
|
|
|
|
This edit on the Issue Triage document brings it up to date with the
style guideline while clarifying some language and doing some minor
edits.
Co-authored-by: Bob Killen <killen.bob@gmail.com>
|
|
* Changed all instancesof k-dev@ and kubernetes-dev@ to dev@kubernetes.io
Changes Removed From archive
updated the link
changes made
csv undo
changed links
* Fix last two instances of googlegroups.com
* Revert changes to election docs for past elections
Co-authored-by: Christoph Blecker <admin@toph.ca>
|
|
The issue triage instructions referenced `lifecycle/needs-information`, but the correct label is `triage/needs-information`. I also added the Prow command corresponding to this label.
|
|
Clarify when to create a PR to address an issue by a new contributor when
the issue is already assigned to someone else.
|
|
Update triage guidelines for the new automation.
Related #4743
|
|
The label triage/support has been reclassified as kind/support. The
kind/* family of labels makes more logical sense, as they describe the
"kind" of thing an issue or PR is.
For more information, see the announcement email:
https://groups.google.com/g/kubernetes-dev/c/YcaJpsjjLKw/m/i15cLLx5CAAJ
|
|
|
|
|
|
Doc was missing the link.
|
|
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update issue-triage.md
* Update issue-triage.md
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update issue-triage.md
* Update issue-triage.md
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update issue-triage.md
* Update contributors/guide/issue-triage.md
Co-Authored-By: Bob Killen <killen.bob@gmail.com>
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
* Update contributors/guide/issue-triage.md
Co-authored-by: Bob Killen <killen.bob@gmail.com>
* Update contributors/guide/issue-triage.md
Co-authored-by: Bob Killen <killen.bob@gmail.com>
* Update contributors/guide/issue-triage.md
Co-authored-by: Bob Killen <killen.bob@gmail.com>
* Update issue-triage.md
* Update issue-triage.md
* Update issue-triage.md
Co-authored-by: Bob Killen <killen.bob@gmail.com>
|
|
|
|
Fixing some spelling mistakes and grammatical errors in the
issue-triage guide.
|
|
|
|
|
|
Add hugo metadata to the contributor guides. Fixes #3769
|
|
Very small grammar corrections.
|
|
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
|
|
updated
|
|
Updated URL in contributors/guide/issue-triage.md
Updated URL in communication/meeting-notes-archive/q1-2_2018_community_meeting_minutes.md
Moved help-wanted from /devel to contributors/guide
Created tombstone for help-wanted.md
|
|
|
|
|
|
README.md updated - slackarchive removed
|
|
The sig-release repo has a set of old documentation looking for a
better home. The issues.md document there describes how a developer
targets an issue (or PR) to a milestone release. This logically
fits better in the community/contributors/devel/ guide, so this commit
brings it in and a parallel commit will remove it from the other repo.
With it comes two pictures of what a release cycle and the overall
release lifecycle look like.
The issues.md content is modified a bit to add more information
about the release process overall and remove outdated information
around the bot-driven workflow for targeting work to a milestone, and is
named release.md here.
Signed-off-by: Tim Pepper <tpepper@vmware.com>
|
|
commit 7bebc930399baa775ddead6d7d57de183d4e116f
Author: Ihor Dvoretskyi <ihor@linux.com>
Date: Thu Aug 30 14:44:23 2018 +0000
sig-governance.md updated
Signed-off-by: Ihor Dvoretskyi <ihor@linux.com>
commit ee0f24313fcdf6255798ef0b4f9bf3f736a87765
Author: Ihor Dvoretskyi <ihor@linux.com>
Date: Thu Aug 30 14:43:47 2018 +0000
contributors/guide/issue-triage.md updated
Signed-off-by: Ihor Dvoretskyi <ihor@linux.com>
commit 09bc3f6d9b6141bff2b8803f2d20e6a6a13751b0
Author: Ihor Dvoretskyi <ihor@linux.com>
Date: Thu Aug 30 14:42:38 2018 +0000
README.md updated
Signed-off-by: Ihor Dvoretskyi <ihor@linux.com>
commit 5b4146f10df50b6255a71144efd6b87bbeea8eb8
Author: Ihor Dvoretskyi <ihor@linux.com>
Date: Thu Aug 30 14:26:51 2018 +0000
README.md updated - slackarchive removed
Signed-off-by: Ihor Dvoretskyi <ihor@linux.com>
|
|
|
|
Since the fejta bot now actively triaging and closing issues, we should
mention it in the triage guidelines and if it has any impact on the usage of
the guidelines for closing issues. It should be helpful to anyone referencing
the guidelines specially to the new triagers.
|
|
The kind/support is replaced with triage/support label, so replace references
accordingly.
|
|
|
|
https://github.com/kubernetes/test-infra/blob/master/commands.md
redirects now to https://prow.k8s.io/command-help . Update the
documentation so that we link directly to
https://go.k8s.io/bot-commands as better automatic redirect.
|
|
Recently we have added new labels to identify issues that are candidates for close.
These issues are typically the one which are not goint to close via a fix. Add
description in triage guidelines about when to use these labels.
Related PR is,
kubernetes/test-infra#7554
|
|
Recently we have added new labels to identify issues that are candidates for close.
These issues are typically the one which are not goint to close via a fix. Add
description in triage guidelines about when to use these labels.
Related PR is,
https://github.com/kubernetes/test-infra/pull/7554
|
|
|
|
|