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

BUG: pull request 9087 modifies a tuple after use #9196

Merged
merged 1 commit into from
May 31, 2017
Merged

BUG: pull request 9087 modifies a tuple after use #9196

merged 1 commit into from
May 31, 2017

Conversation

mattip
Copy link
Member

@mattip mattip commented May 31, 2017

backported pull request #9195

@mattip
Copy link
Member Author

mattip commented May 31, 2017

my first backport, hope it is OK

@mhvk
Copy link
Contributor

mhvk commented May 31, 2017

@charris - could you check? I think it is OK, but I'm still a bit unsure about labels, including the commit title etc.

@charris charris added this to the 1.13.0 release milestone May 31, 2017
@charris
Copy link
Member

charris commented May 31, 2017

Looks good. Keeping the same title helps when generating the 1.13.0 changelog and the tags should be the same except for the Backport tag. I like to remove the candidate tag after the backport is done and add the milestone to allow searching for missing backports. As a general rule, it is OK to merge backports without review.

@charris
Copy link
Member

charris commented May 31, 2017

Note that I am considering leaving the Backport-candidate tag alone if the milestone is set on both PRs. The procedure isn't quite settled yet.

@charris charris merged commit 9ad431d into numpy:maintenance/1.13.x May 31, 2017
@mattip mattip deleted the backport-9087 branch June 1, 2017 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants