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

release: backport patrol for 19.2 #41629

Closed
tbg opened this issue Oct 16, 2019 · 0 comments
Closed

release: backport patrol for 19.2 #41629

tbg opened this issue Oct 16, 2019 · 0 comments
Assignees
Milestone

Comments

@tbg
Copy link
Member

tbg commented Oct 16, 2019

We don't have a good process around making sure everything that needs to be backported is actually backported. As a stand-in, I'm doing this manually for now. Below is a list of PRs that were not backported into 19.2; please check off any line that has been "acted upon" (i.e. it was decided that no backport is needed, or a backport PR opened). Reminder: we're being very conservative at this point.

Instead of pulling in all of the original authors, I'm asking the TLs to do a pass, which I assume will take care of most items (pretty sure that the majority below won't need backports).

done!

Created via

cat backport.txt  | grep -vE '(✓|◷)$' | grep -vE '(roachtest:)|(sqlsmith:)|(roachprod:)' | cut -c33- | sort | sed -E 's/^/- [ ] /' | pbcopy

where backport.txt was copy-pasted from backboard (pedestrian, I know, but it works fine, and the data isn't readily available as a SQL query, I checked) as of last refresh timestamp 2019-10-16 08:17.

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

No branches or pull requests

7 participants