-
Notifications
You must be signed in to change notification settings - Fork 36
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
Add some more docs about packaging details and conda-forge releases #48
Conversation
Anything else needed here so this gets merged? 🙏 |
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.
To me this is all clear. I can't say I've tested it though.
I've made the most nitpick-y of comments—feel free to ignore.
For one, it looked like conda-forge was mostly conda-forge
so I tried to add the ` but I'm not sure I got everything 👀
Co-authored-by: Peter Sobolewski <76622105+psobolewskiPhD@users.noreply.github.com>
Thank you @psobolewskiPhD! |
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.
Please add version substitution
Co-authored-by: Melissa Weber Mendonça <melissawm@gmail.com>
As far as I'm concerned this is good to go now, @Czaki any last comments? |
Anything else needed, team? |
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.
If you think that manually updating yaml file is ok, then it should be added to the list of things need to be done before release. Next to Ensure conda-recipe/meta.yaml...
line
docs/developers/packaging.md
Outdated
@@ -113,10 +118,10 @@ specs: # specs for the 'base' environment | |||
- mamba # we add these to manage different napari versions | |||
- pip # we add these to manage different napari versions | |||
extra_envs: | |||
napari-0.4.16: # this is the environment that will actually contain the napari packages | |||
napari-0.4.17: # this is the environment that will actually contain the napari packages |
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.
could we generate this yaml file using template tags to ensure that it will be kept up to date without manual interventions?
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.
Unfortunately this is not supported in MyST. See warnings.
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.
Instead I added the term "hypothetical" to make clear we are only providing an example that is not meant to be up to date with the current version. Let me know what you think @Czaki
Is this good to go? :D |
Description
The packaging docs needed some subtle changes in wording and content.
Type of change
References
Closes napari/packaging#2
How has this been tested?
Final checklist:
trans.
to make them localizable.For more information see our translations guide.
Side question: is the issue template accurate for this repository? It feels we could have a more relatable one :D