Skip to content

tools: adding some version notes alphabetization checks to check_format#10695

Merged
mattklein123 merged 4 commits intoenvoyproxy:masterfrom
alyssawilk:alpha
Apr 8, 2020
Merged

tools: adding some version notes alphabetization checks to check_format#10695
mattklein123 merged 4 commits intoenvoyproxy:masterfrom
alyssawilk:alpha

Conversation

@alyssawilk
Copy link
Contributor

Risk Level: n/a
Testing: manual as seen by new release notes
Docs Changes: n/a
Release Notes: sort of...

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
@mattklein123
Copy link
Member

Yes amazing!!! Can you merge master?

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Copy link
Contributor

@asraa asraa left a comment

Choose a reason for hiding this comment

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

Thank you! Just one small comment

reportError("Version history line malformed. "
"Does not match VERSION_HISTORY_NEW_LINE_REGEX in check_format.py\n %s" % line)
else:
first_word = match.groups()[0]
Copy link
Contributor

Choose a reason for hiding this comment

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

Based on the * quantifier in VERSION_HISTORY_NEW_LINE_REGEX could this just be :? Is that OK? (Alphabetization makes sense of it, but just as a release note)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I guess arguably - that'd be a useless release note but we should complain cleanly :-)

I'm doing a follow-up to make sure sentences end with . - OK if I change the * to + there, just for release reasons?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, that seems like a better place! LGTM otherwise

Copy link
Member

Choose a reason for hiding this comment

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

OK sounds good I will force merge once the docs build passes.

@mattklein123 mattklein123 merged commit 560e7d4 into envoyproxy:master Apr 8, 2020
@alyssawilk alyssawilk deleted the alpha branch August 27, 2020 16:33
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.

4 participants