Announcement about Cleaning the Cherry-pick PRs

#1

Hi everybody! We(PingCAP EP team) decide to clean up some unnecessary cherry-pick PRs in the following period of time. The following is the background and the actions we will take.

Background

There is a git bot(ti-chi-bot) helping developers to automatically cherry-pick PRs to target release branch, which has helped our developers saving remarkable cost so far.
But it also created some redundancy PRs such as PRs for issues won’t be fixed. And which further causes the number of opening PRs too large to be managed easily.
So PingCAP EP team makes the decision to solve above problems by following actions! (These actions have been approved by committee inside PingCAP.)

Actions

Restrain the Creation of Cherry-pick

For versions supported for more than 1 year or released DMR versions(3.0, 4.0, 5.0, 5.1, 5.2, 6.0, 6.2), we’ll close the automatic PR cherry-picking.
Cherry-pick PRs needed on these versions can be created using bot.( ti-community-cherrypicker (tidb.net))

Batch Closing the Cherry-pick

For the versions listed above(3.0, 4.0, 5.0, 5.1, 5.2, 6.0, 6.2), we’ll close the current opening cherry-pick PRs.
Cherry-pick PRs closed can be regenerated using bot.( ti-community-cherrypicker (tidb.net))

Actions above all support blacklist (PR, repo, org ) and will be double checked by the committee.

Best,
Yuchao Li.

#2

For versions supported for more than 1 year or released DMR versions(3.0, 4.0, 5.0, 5.1, 5.2, 6.0, 6.2), we’ll close the automatic PR cherry-picking.

Can I assume that the later patch versions of those released versions(3.0, 4.0, 5.0, 5.1, 5.2) will not be released in the future?

#3

No. There is no official announce about the EoSD of above versions so this conclusion can’t be driven. These versions are included in this action according to their release rate and internal suggestions.