-
Notifications
You must be signed in to change notification settings - Fork 41
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
Update release process and procedure documentation #628
Conversation
Add reference to #486 to the process. |
Read through this the other day, and as a 'new' contributor, I found the 'our release cycle is super fast better keep up' to be very intimidating. So, these edits are both a positive change and seems to reflect the reality of how things are currently done. |
|
||
The latest release candidate can be installed with | ||
The latest prerelease (alpha or release candidate) can be installed with: | ||
|
||
`python -m pip install --pre napari` |
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.
The command can be problematic, because it installs all dependencies as --pre
as well, which can lead to errors, see napari/napari#7707 (comment)
I think it's worth adding a note here.
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.
See below
Co-authored-by: Peter Sobolewski <[email protected]>
Co-authored-by: Juan Nunez-Iglesias <[email protected]>
References and relevant issues
Addresses #626
Description
Update the release process page based on current state of releases.