Skip to content

DOC: Add 1.5.x note to main #50822

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

Merged
merged 1 commit into from
Jan 18, 2023
Merged

Conversation

phofl
Copy link
Member

@phofl phofl commented Jan 18, 2023

  • closes #xxxx (Replace xxxx with the GitHub issue number)
  • Tests added and passed if fixing a bug or adding a new feature
  • All code checks passed.
  • Added type annotations to new arguments/methods/functions.
  • Added an entry in the latest doc/source/whatsnew/vX.X.X.rst file if fixing a bug or adding a new feature.

Copy link
Member

@datapythonista datapythonista left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unrelated to this PR, but seeing the tricky things we need to do in the whatsnew when open PRs directly to a branch, I wonder whether would make sense to have the release note in the website, instead of versioned in the docs...

I wonder if there are differences between the release notes in 1.5.3 (or others) when checking the docs of it, compared to when checking the docs of a future version like 2.0. We'd solve that.

@datapythonista datapythonista merged commit a1babdc into pandas-dev:main Jan 18, 2023
@phofl phofl deleted the dep_warning branch January 18, 2023 18:10
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

Successfully merging this pull request may close these issues.

2 participants