-
Notifications
You must be signed in to change notification settings - Fork 42
Update release guide #491
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 guide #491
Conversation
I'd love some input in the translations and packaging sections, as I don't know what happens there. The constraints section has been recently updated so should be ok. |
Translations are unmaintained and will remain so until the software is more mature. I had a discussion about this with @goanpeca (that I neglected to post about sorry 😞) where we decided that it didn't make sense to spend so much maintenance effort when many of these strings (e.g. deprecation messages) will actually disappear before any translation even sees the light of day. (Currently, there are no localised binaries available at all.) Packaging I'm less sure of but my understanding is that @jaimergp and @goanpeca maintain some CI recipes that get triggered during the GH Release build process. In general, indeed it would be good for this page to have more notes about what's actually happening. ("When a tag gets pushed, it triggers THIS workflow, which pushes artifacts to PyPI using TRUSTED PUBLISHERS, which can be configured by STEERING COUNCIL." "Within 24h, the release will be picked up by the conda-forge bot, which will make a PR like THIS ONE. You should check that the PR dependencies match any recent changes to the PYPROJECT.TOML dependencies." Finally, the thing that is still missing is that the version_chooser.json and the symlink must be updated manually. Ideally we would automate that but in the meantime, we should document it. |
Perfect, will add those. Thanks! |
I think we have some content for that in https://napari.org/stable/developers/coredev/packaging.html already. Maybe we just need to rehash some of the details in a more "workflow-y" way. The basics:
|
Updated release notes generation instructions and removed outdated information. Also deletes the obsolete script that was used to generate release notes, replaced now by the script in napari-release-tools.
70f4802
to
20ace14
Compare
Co-authored-by: jaimergp <jaimergp@users.noreply.github.com>
References and relevant issues
N/A
Description
Updated release notes generation instructions and removed outdated information.
Also deletes the obsolete script that was used to generate release notes, replaced now by the script in napari-release-tools.