-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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: Update release process #53435
DOC: Update release process #53435
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for writing this up. Just one minor nit.
1. Update symlinks to stable documentation by logging in to our web server, and | ||
editing ``/var/www/html/pandas-docs/stable`` to point to ``version/<latest-version>`` | ||
for major and minor releases, or ``version/<minor>`` to ``version/<patch>`` for | ||
patch releases. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a command/script to do this?
I haven't really done symlinks before, so this is probably something that I shouldn't just figure out on the fly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's just something like ln -sf 2.0.2 2.0
from the command line. I don't think it's worth having a script, happy to have a call to show you, and do it together during the release (that part and any really).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, that would be really helpful (I guess I'll ping you as 2.0.3 draws closer).
It might be good to write down the step-by-step commands regardless, though (since that makes less room for error, and is helpful for others too).
I dunno if the public docs is the right place to do so, since we wouldn't want to list e.g. the IP of the docs VM publicly(maybe a google doc shared to the core team would be best?).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just updated the instructions, let me know if there is anything that is not clear or can be improved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
thanks @datapythonista. |
) Backport PR #53435: DOC: Update release process Co-authored-by: Marc Garcia <[email protected]>
* DOC: Update release process * Add exact symlinks instructions
@lithomas1 can you have a look and let me know if everything is clear please?