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

DOC: whatsnew note for MultiIndex Sorting Fix #21316

Merged
merged 2 commits into from
Jun 5, 2018

Conversation

WillAyd
Copy link
Member

@WillAyd WillAyd commented Jun 4, 2018

@WillAyd WillAyd changed the title Updated whatsnew Whatsnew Note for MultiIndex Sorting Fix Jun 4, 2018
@jschendel
Copy link
Member

jschendel commented Jun 4, 2018

Should this be in the 0.24.0 whatsnew instead? The xref'd PR has a 0.24.0 milestone. Not opposed to this going in 0.23.1, just want to make sure this is aligned with the xref'd PR.

@WillAyd
Copy link
Member Author

WillAyd commented Jun 4, 2018

Good question. Since it's a bug fix I am assuming v0.23.1 but can move if we want

@codecov
Copy link

codecov bot commented Jun 4, 2018

Codecov Report

Merging #21316 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master   #21316   +/-   ##
=======================================
  Coverage   91.85%   91.85%           
=======================================
  Files         153      153           
  Lines       49549    49549           
=======================================
  Hits        45512    45512           
  Misses       4037     4037
Flag Coverage Δ
#multiple 90.25% <ø> (ø) ⬆️
#single 41.87% <ø> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b32fdc4...6235bea. Read the comment docs.

@jorisvandenbossche jorisvandenbossche changed the title Whatsnew Note for MultiIndex Sorting Fix DOC: whatsnew note for MultiIndex Sorting Fix Jun 5, 2018
@jorisvandenbossche jorisvandenbossche added this to the 0.23.1 milestone Jun 5, 2018
@jorisvandenbossche
Copy link
Member

OK, the fix seems rather small and it fixes an actual data corruption, so let's target it as 0.23.1

@jorisvandenbossche jorisvandenbossche merged commit 15b39cd into pandas-dev:master Jun 5, 2018
TomAugspurger pushed a commit to TomAugspurger/pandas that referenced this pull request Jun 12, 2018
TomAugspurger pushed a commit that referenced this pull request Jun 12, 2018
david-liu-brattle-1 pushed a commit to david-liu-brattle-1/pandas that referenced this pull request Jun 18, 2018
@WillAyd WillAyd deleted the mi-docstr branch December 25, 2018 06:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants