Skip to content

Add a CODEOWNERS#558

Merged
olix0r merged 4 commits intomasterfrom
ver/codeowners
Jun 12, 2020
Merged

Add a CODEOWNERS#558
olix0r merged 4 commits intomasterfrom
ver/codeowners

Conversation

@olix0r
Copy link
Member

@olix0r olix0r commented Jun 11, 2020

This CODEOWNERS change will ensure that proxy-maintainers are requested on all PRs.

This CODEOWNERS change will enforce a requirement that I approve all
PRs to master. This is already practically the case, but it's not
codified.

I'd like to follow this by relaxing the PR review requirement to 1. This
allows me to merge my own PRs with only a single review, and will allow
me to unblock any other PR. Practically, I plan to continue to solicit
>1 review on changes; but I don't think this needs to be enforced by
GitHub.
@olix0r olix0r self-assigned this Jun 11, 2020
@hawkw
Copy link
Contributor

hawkw commented Jun 11, 2020

This CODEOWNERS change will enforce a requirement that I approve all
PRs to master.

IIRC, CODEOWNERS, on its own, doesn't actually require a review from code owners to merge a PR; it just adds you as a reviewer automatically. I think there's also a repo setting to "require a review from CODEOWNERS" that needs to be flipped.

This is already practically the case, but it's not
codified.

This is basically true, yeah. I feel like I also review pretty much all proxy changes, but I don't feel like my review needs to be blocking, unlike yours.

My only concern about doing this for now is bus factor --- if you're OOO for a week, we can't merge anything during that time. I don't think we would merge any major functional changes even without Github enforcing that your approval is required, and minor changes like spelling fixes or whatever could just wait until you got back, but it could be good to be able to get a hypothetical fix for a major issue through without having to track you down in the woods or whatever?

@olix0r olix0r requested a review from a team June 12, 2020 17:36
Copy link
Contributor

@kleimkuhler kleimkuhler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@olix0r olix0r merged commit b72f156 into master Jun 12, 2020
@olix0r olix0r deleted the ver/codeowners branch June 12, 2020 19:53
olix0r added a commit that referenced this pull request Jun 15, 2020
This CODEOWNERS change will ensure that proxy-maintainers are requested on all PRs.
hawkw pushed a commit that referenced this pull request Jun 15, 2020
* make: Support CARGO_TARGET for multi-arch builds (#497)

This change adds support for a `CARGO_TARGET` environment variable.
When set, this value is passed to i.e. `cargo build --target` to support
cross-compilation for multi-architecture builds.

Signed-off-by: jaerik <[email protected]>
Co-authored-by: Erik Jansson <[email protected]>

* Add a CODEOWNERS (#558)

This CODEOWNERS change will ensure that proxy-maintainers are requested on all PRs.

Co-authored-by: Erik Jansson <[email protected]>
Co-authored-by: Erik Jansson <[email protected]>
olix0r added a commit to linkerd/linkerd2 that referenced this pull request Jun 23, 2020
This release primarily features an upgrade of the proxy's underlying
Tokio runtime and its related libraries. We've observed lower latencies
in initial benchmarks, but further testing and burn-in is warranted.

Also, the proxy now honors the `LINKERD_PROXY_LOG_FORMAT=json`
configuration to enable JSON-formatted logging.

---

* Add a CODEOWNERS (linkerd/linkerd2-proxy#558)
* Fix shellcheck issues in shell scripts (linkerd/linkerd2-proxy#554)
* update the proxy to use std::future and Tokio 0.2 (linkerd/linkerd2-proxy#568)
* Prune unused dependencies (linkerd/linkerd2-proxy#569)
* Support LINKERD_PROXY_LOG_FORMAT=json (linkerd/linkerd2-proxy#500)
* Change docs references from "master" to "main" (linkerd/linkerd2-proxy#571)
* Upgrade tokio-rustls & webpki. (linkerd/linkerd2-proxy#570)
* Makefile: Add shellcheck recipe (linkerd/linkerd2-proxy#555)
* Update proxy-api dependencies (linkerd/linkerd2-proxy#573)
* integration: fix missing traces (linkerd/linkerd2-proxy#572)
* Update Rust to 1.44.0 (linkerd/linkerd2-proxy#574)
* Use async/await to simplify connection-accept task (linkerd/linkerd2-proxy#575)
* Update Rust to 1.44.1 (linkerd/linkerd2-proxy#576)
* outbound: Split HTTP endpoint builder (linkerd/linkerd2-proxy#578)
* Simplify protocol detection with async/await (linkerd/linkerd2-proxy#577)
* Pin proxy-api at v0.1.13 (linkerd/linkerd2-proxy#579)
olix0r added a commit to linkerd/linkerd2 that referenced this pull request Jun 24, 2020
This release primarily features an upgrade of the proxy's underlying
Tokio runtime and its related libraries. We've observed lower latencies
in initial benchmarks, but further testing and burn-in is warranted.

Also, the proxy now honors the `LINKERD_PROXY_LOG_FORMAT=json`
configuration to enable JSON-formatted logging.

---

* Add a CODEOWNERS (linkerd/linkerd2-proxy#558)
* Fix shellcheck issues in shell scripts (linkerd/linkerd2-proxy#554)
* update the proxy to use std::future and Tokio 0.2 (linkerd/linkerd2-proxy#568)
* Prune unused dependencies (linkerd/linkerd2-proxy#569)
* Support LINKERD_PROXY_LOG_FORMAT=json (linkerd/linkerd2-proxy#500)
* Change docs references from "master" to "main" (linkerd/linkerd2-proxy#571)
* Upgrade tokio-rustls & webpki. (linkerd/linkerd2-proxy#570)
* Makefile: Add shellcheck recipe (linkerd/linkerd2-proxy#555)
* Update proxy-api dependencies (linkerd/linkerd2-proxy#573)
* integration: fix missing traces (linkerd/linkerd2-proxy#572)
* Update Rust to 1.44.0 (linkerd/linkerd2-proxy#574)
* Use async/await to simplify connection-accept task (linkerd/linkerd2-proxy#575)
* Update Rust to 1.44.1 (linkerd/linkerd2-proxy#576)
* outbound: Split HTTP endpoint builder (linkerd/linkerd2-proxy#578)
* Simplify protocol detection with async/await (linkerd/linkerd2-proxy#577)
* Pin proxy-api at v0.1.13 (linkerd/linkerd2-proxy#579)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants