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.

Sign up for GitHub

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

Jump to bottom

Release v0.10 #765

Closed
15 of 18 tasks
choldgraf opened this issue Jun 28, 2022 · 5 comments
Closed
15 of 18 tasks

Release v0.10 #765

choldgraf opened this issue Jun 28, 2022 · 5 comments
Assignees
@jarrodmillman
Milestone
0.10

Comments

@choldgraf
Copy link
Collaborator

choldgraf commented Jun 28, 2022 •
edited by jarrodmillman

We've got a lot of nice new features in main and I think it's time to make a release so others can benefit from them. There are a few extra pieces that I've added to the 0.10 milestone. But I wanted to open up this issue to see if anybody objected to making the new release when they're done.

Checklist below

Double check for quality-control

Release candidate

Prepare the codebase for a new version

  • Bump __version__ in __init__.py1
  • Update our version switcher .json file with the new version
  • Make a release commit: git commit -m 'RLS: v0.2.0'
  • Push the RLS commit git push upstream master

Make the release

  • Start a new GitHub release
  • Call the release the current version, e.g. v0.2.0
  • In the Choose a Tag: dropdown, type in the release name (e.g., v0.2.0) and click "Create new tag"
  • In the Target: dropdown, pin it to the release commit that you've just pushed.
  • Add release notes in the field below (if it's a minor/major version bump)2
  • Confirm that the publish github action job has completed successfully in the actions tab
  • Confirm that the PyPI version is updated
  • Celebrate, you're done!

Footnotes

  1. Use semantic versioning to decide whether it's a major, minor, or patch bump. Before we have released 1.0, treat minor versions as breaking releases, and patch versions as feature / patch releases. ↩

  2. If you wish, use github-activity to generate a changelog, eg github-activity pydata/pydata-sphinx-theme --since v0.2.2 --until v0.3.0. ↩
@choldgraf choldgraf added this to the 0.10 milestone Jun 28, 2022
@drammock
Copy link
Collaborator

I'd like to fix #752 before the next release, if possible. I've been quite busy but I might have time later this week to dig deeper... it may end up being mostly a documentation fix.

@jarrodmillman jarrodmillman self-assigned this Jul 1, 2022
@choldgraf
Copy link
Collaborator Author

We are getting closer folks! If possible, I think it would be great if we can get a release out during SciPy so that we can generate some buzz around it :-)

@choldgraf
Copy link
Collaborator Author

I'm hoping to cut a release candidate today! As long as nobody objects I'll try to get it out the door quickly after fixing the last two bugs in our milestone

@choldgraf choldgraf mentioned this issue Jul 15, 2022
Merged
@choldgraf choldgraf pinned this issue Jul 30, 2022
@jarrodmillman
Copy link
Collaborator

We tagged 0.10, but it won't automatically upload to PyPI. This should be fixed by #900.

@jarrodmillman
Copy link
Collaborator

https://pypi.org/project/pydata-sphinx-theme/0.10.1/

@jarrodmillman jarrodmillman unpinned this issue Aug 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jarrodmillman jarrodmillman

Labels
None yet
Projects
None yet
Milestone
0.10
Development

No branches or pull requests
3 participants
@jarrodmillman @drammock @choldgraf