Add final? 0.7.0 highlights and group by topic

[DragaDoncila]

References and relevant issues

Description

This PR adds sections for the remaining highlights for v0.7.0 and groups most highlights into sections:

Breaking changes:

• Transition to npe2
• Fixed camera angles
• Negative axis labels

New features & widgets:

• What's my metadata? napari-metadata to the rescue
• (Layer) Features galore
• Smarter new layer buttons
• Better text overlays

Rendering & display:

• More pixels to play with - texture tiling
• Points - any size you like

Performance:

• Lightning labels
• Grid mode -- bigger, better, faster
• Add & delete layers without delay
• Shapes layers -- select, zoom, delete, repeat

There is one single entry at the bottom that is not otherwise grouped:

• Infrastructure & dependencies

[brisvag]

Maybe note that this is not public for now cause we'r enot sure on the api.

[DragaDoncila]

@brisvag added a note in the latest commit.

[brisvag]

• Transition to npe2

• Fixed camera angles

• Negative axis labels

• Infrastructure & dependencies

I would put the top 3 in something like "Breaking changes". Let last one is fine at the bottom as an FYI.

[psobolewskiPhD]

I would probably hold off on trumpeting this like this?
It's still pretty bad, so people will still have a poor experience if they try IMO.
I have a more comprehensive PR to better address the underlying performance issue:
napari/napari#8636

[brisvag]

(Sorry about that waiting PR, I've been looking into it often but it's always a bit overwhelming and long to review 😅 )

[psobolewskiPhD]

No worries!

[DragaDoncila]

@psobolewskiPhD I've reworded a little and flagged that we're still working on it - happy with that?

[psobolewskiPhD]

I know this is mostly for fun, but I don't love conflating resolution with a compression codec, one that could be lossless. It's already something a lot of people confuse...
Can we use a different phrasing?

[DragaDoncila]

I've reworded while trying to keep it fun - let me know if you'd like to workshop it a little still

[DragaDoncila]

@brisvag @psobolewskiPhD I think I've addressed comments! I made a new breaking changes section at the top, and reworded stuff/added notes as suggested. Let me know if there's any other changes you'd like to make!

[psobolewskiPhD]

I would still drop the labels speedup stuff from the highlights and leave it just in the other section.
There are a lot of highlights in this release and they are real highlights, so we don't need to polish a turd, so to speak, just to have a highlight.
Hopefully, we have that as a highlight when it's really meaningful, maybe in the next release!
But i like how you changed the tiling part a lot!

[DragaDoncila]

I would still drop the labels speedup stuff from the highlights and leave it just in the other section.

@psobolewskiPhD gotcha, I've removed it from highlights and now it's listed only in the performance section!

[jni]

ah with webm you can't just use markdown, this is the syntax:

docs/docs/release/release_0_5_5.md

Lines 38 to 49 in a2feafd

	```{raw} html
	<figure>
	<video width="100%" controls autoplay loop muted playsinline>
	<source src="../_static/images/triangle-edge.webm" type="video/webm" />
	<source src="../_static/images/triangle-edge.mp4" type="video/mp4" />
	<img src="../_static/images/triangle-edge.png"
	title="Your browser does not support the video tag"
	alt="napari viewer showing a shapes layer and associated layers depicting the triangulation of the elements of the Shapes layer."
	>
	</video>
	</figure>
	```

(and yes, you refer to the mp4 without seeing it, because it is automatically generated during docs build, thanks to @melissawm! 🤩 I'm not sure about the image fallback, that might need to be done manually...)

[jni]

Result: https://napari.org/dev/release/release_0_5_5.html

[melissawm]

Yes the image fallback is a screenshot I do take manually - let me know if you need help!

[TimMonko]

I'll bring it up because I always do, but Github kind of competes with how we build our docs
Looking at the release notes on Github (which I think newer Github folks like me often do) you would just see this html, even though it shows in the docs. I used github content as gifs for my release notes, but I know that Juan always didn't like that they weren't videos (and I agree).

https://github.com/DragaDoncila/docs/blob/b27ec8b071d255c0c2607a9d1e1708b21a6b1158/docs/release/release_0_7_0.md#points---any-size-you-like-

[DragaDoncila]

yeah I know @TimMonko I usually have done gifs, but Juan doesn't like gifs and they are kinda huge tbf. Also limited to 10MB via gh-lfs, so I opted for a video here. I do think I prefer having the docs rendered nicely with a high-res video to having the github release notes fully functional (in a world where we can't have both), so I'm going to leave this as is.

[TimMonko]

@DragaDoncila I assume you are going to run the script one more time? Just want to make sure because the recent PRs aren't on there (I noticed because of looking for Clement Caporal's name)

[DragaDoncila]

I assume you are going to run the script one more time? Just want to make sure because the recent PRs aren't on there (I noticed because of looking for Clement Caporal's name)

Yes, just before cutting the RC there will be a final run! Just want to make reviews for that final update easier hopefully by merging this first

[DragaDoncila]

@jni I "fixed" the github user links like you'd suggested, but it looks like our docs do their own magic, or maybe sphinx does, for displaying github links.

Here's the raw code showing both ways I've tried:

With a lot of work from our community contributor, Carlos Mario Rodriguez Reza
(https://github.com/carlosmariorr), and
our venerable community manager Tim Monko ((**@TimMonko**)[https://github.com/timmonko]),

and here's the screenshot:

Sooo.. for now I'm going to go with just the github link in brackets, without any kind of hyperlinking. If you see this and decide you hate it, lmk! I'll get it in follow-up PR before RC.