jedcunningham commented on code in PR #36918: URL: https://github.com/apache/airflow/pull/36918#discussion_r1459684225
########## dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md: ########## @@ -50,13 +50,13 @@ The succinct form of it is described in a prominent place in our most important # How does the selection process for cherry-picking work? In short (and this is the most important thing that every maintainer should be aware of): -**maintainers who think that issue should be included should mark it with the next patchlevel milestone** +**maintainers who think that issue should be included should mark it with the next patch level milestone** Review Comment: ```suggestion **maintainers who think that issue should be included should mark it with the next patch release milestone** ``` ########## dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md: ########## @@ -29,11 +29,11 @@ - [When proposed PRs are rejected?](#when-proposed-prs-are-rejected) - [Why are provider changes not cherry-picked?](#why-are-provider-changes-not-cherry-picked) - [What's the purpose of patch-level releases?](#whats-the-purpose-of-patch-level-releases) -- [Do we intentionally skip over some changes when releasing a patchlevel release?](#do-we-intentionally-skip-over-some-changes-when-releasing-a-patchlevel-release) +- [Do we intentionally skip over some changes when releasing a patch level release?](#do-we-intentionally-skip-over-some-changes-when-releasing-a-patch-level-release) Review Comment: I think we should just refer to it as "patch release". -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
