Skip to content
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

More explicitly list safe config changes to merge #3972

Merged
merged 1 commit into from
Apr 23, 2024

Conversation

yuvipanda
Copy link
Member

Code review work is also work, and especially for a split TZ team like ours, latency here can be a real velocity killer. A lot of config changes only take a 'rubber stamp' approval, because someone still needs to verify that the change actually propagated.

This PR more explicitly lists some of these config changes that don't need review, as there isn't any effective way for someone to really provide review here. This list will get bigger over time, and should give us more confidence to move faster.

Code review work is also work, and especially for a split
TZ team like ours, latency here can be a real velocity killer. A
lot of config changes only take a 'rubber stamp' approval, because
someone still needs to verify that the change actually propagated.

This PR more explicitly lists some of these config changes that
don't need review, as there isn't any effective way for someone
to really provide review here. This list will get bigger over time,
and should give us more confidence to move faster.
Copy link
Member

@consideRatio consideRatio left a comment

Choose a reason for hiding this comment

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

Good separation on "when asked by the community"

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