Anki 25.06 Beta

[dae]

@vaibhav

Assorted minor issues with new launcher is closed, but Anki still appears as Python in the Task Manager.

My conclusion was “can’t fix without a different architecture”, but I’d love to be proved wrong. I’ve logged it in a separate issue: Anki appears as Python in the task manager on Windows · Issue #4144 · ankitects/anki · GitHub

@vaibhav

uv cache is enabled by default, but I can’t see any benefit of doing so, especially if we anyway clear the cache when uninstalling Anki. During updates, the packages aren’t redownloaded if they were unchanged even if the cache was cleared.
Edit: Having packages cached helps when downgrading, but is downgrading so common that the cache should be enabled for all users by default?

It makes for a nicer out-of-the-box experience when switching between versions, and given how many users depend on add-ons, it’s not so uncommon for them to downgrade when they find an add-on is not working. I can appreciate the argument for making it default to off, and that may happen in the future, but I think defaulting to on might make more sense at the moment, especially given how skeptical people are to change, and how they may play around with this at first.

@Expertium

TLDR: replace CMRR with a desired retention - workload graph

Generally blockers are regressions, not extra features I think this and Jarrett’s last review time work are probably not going to be ready on time, and are best deferred to the next update - I don’t anticipate it following far behind the current one, and this new system has made making releases easier than it was previously.

@sorata

Does the RMSE/log-loss being exposed in debug console not count? That was the compromise we already made (but the required changes haven’t yet been yet iirc).

Logged on Expose old evaluate API to the debug console · Issue #4143 · ankitects/anki · GitHub so it doesn’t get missed.