Draft release notes for 0.5.0 #430
Conversation
github-actions
bot
added
the
documentation
|
We should add some check to validate if release is added to toc.yml |
docs/release/release_0_5_0.md
Outdated
| - ci(dependabot): bump WebFreak001/deploy-nightly from 1.2.0 to 2.0.0 ([napari/napari#5385](https://github.com/napari/napari/pull/5385)) | ||
| - ci(dependabot): bump docker/build-push-action from 3 to 4 ([napari/napari#5523](https://github.com/napari/napari/pull/5523)) | ||
| - ci(dependabot): bump toshimaru/auto-author-assign from 1.6.1 to 1.6.2 ([napari/napari#5524](https://github.com/napari/napari/pull/5524)) | ||
| - fix various keybinding/shortcut bugs ([napari/napari#5604](https://github.com/napari/napari/pull/5604)) |
There was a problem hiding this comment.
The labels:
I guess dependencies puts it here?
Maybe tag it with bugfix? that seems what it does based on the first post.
there are no missing labels (thanks @Czaki!), this is just where maintenance goes. We have discussed the issue of our PR ratio in the core-devs Zulip... 😅 |
|
btw I don't think we have been super diligent with the highlights label, so feel free to suggest other things that you want to tell the community about! |
It should be, but unfortunately I haven't been able to solve all other sphinx errors so this error would just die among all the other ~60 we currently have 😭 We are tracking this here: #227 and here: #409 |
docs/release/release_0_5_0.md
Outdated
| - implement copying spatial information via clipboard ([napari/napari#6864](https://github.com/napari/napari/pull/6864)) | ||
| - Add `axis_labels` and `units` to layers and transforms ([napari/napari#6979](https://github.com/napari/napari/pull/6979)) | ||
| - Alpha implementation of NAP-6 ([napari/napari#7011](https://github.com/napari/napari/pull/7011)) | ||
| - Screenshot without margins ([napari/napari#6730](https://github.com/napari/napari/pull/6730)) |
There was a problem hiding this comment.
Should we rename this? it's not screenshot anymore is it? different API only thing?
There was a problem hiding this comment.
"Export figure" or something like that.
docs/release/release_0_5_0.md
Outdated
| - Use Request/Response pattern for Vectors layer ([napari/napari#5918](https://github.com/napari/napari/pull/5918)) | ||
| - Lock dimensions / axes while rolling ([napari/napari#5986](https://github.com/napari/napari/pull/5986)) | ||
| - Added support for features in surface layers ([napari/napari#6515](https://github.com/napari/napari/pull/6515)) | ||
| - Add creating image from clipboard ([napari/napari#6532](https://github.com/napari/napari/pull/6532)) |
There was a problem hiding this comment.
To me, this one is 🔥 maybe worth highlight? if doing anything with remote data, like in S3 buckets, it's sick to be able to copy and open directly in napari -- assuming zarr/plugins anyways.
docs/release/release_0_5_0.md
Outdated
| - Add points/shapes highlight color setting to Appereance settings and preference page ([napari/napari#6689](https://github.com/napari/napari/pull/6689)) | ||
| - Include features index as key in FormatStringEncoding ([napari/napari#6703](https://github.com/napari/napari/pull/6703)) | ||
| - Reset all dims to be rollable ([napari/napari#6797](https://github.com/napari/napari/pull/6797)) | ||
| - implement copying spatial information via clipboard ([napari/napari#6864](https://github.com/napari/napari/pull/6864)) |
There was a problem hiding this comment.
This is also pretty sweet. Not sure how long we want the highlight section, but worth pointing to IMO.
| - ci(dependabot): bump docker/build-push-action from 4 to 5 ([napari/napari#6280](https://github.com/napari/napari/pull/6280)) | ||
| - ci(dependabot): bump docker/metadata-action from 4 to 5 ([napari/napari#6282](https://github.com/napari/napari/pull/6282)) | ||
|
|
||
| ## Documentation |
There was a problem hiding this comment.
Is it worth breaking out the maintenance label docs PRs to a different section?
maybe have a section:
Copy improvements
&
Maintenance
I can go and do some tagging if needed.
|
If @jni used |
|
Well, or @psobolewskiPhD — just realised it's quite late 😂 |
I thought after merging #430 that the fact that the release hasn't officially happened yet should be more prominent. 😅
No description provided.