Skip to content

Add mizer 3.2 announcement blog post#5

Open
gustavdelius wants to merge 1 commit into
masterfrom
mizer-3-2-announcement
Open

Add mizer 3.2 announcement blog post#5
gustavdelius wants to merge 1 commit into
masterfrom
mizer-3-2-announcement

Conversation

@gustavdelius

Copy link
Copy Markdown
Member

Adds a blog post announcing the mizer 3.2 release.

The post is framed around the two reasons for a release so soon after 3.1:

  • Consistent resource setting — the resource setters had grown inconsistent, balancing (and silently discarding scalar edits) when they shouldn't. The post explains the old behaviour, the fix that makes them behave like species_params<-, and points to the Upgrading mizer vignette.
  • Extensions that chain in any order — the static sibling-of-MizerParams marker classes prevented combining two extensions. The post explains the flaw and the dynamic-marker-class fix, with a worked mizerReef + mizerMR example drawn from mizerReef's multiple-resources.Rmd vignette.

It closes with a short roundup of the smaller 3.2 additions (steadyNewton(), adjustSizeGrid(), project() callback, nicer printing, cheatsheets) and an upgrading note.

Notes:

  • Written as a distill .Rmd matching the other posts; code chunks are illustrative (eval = FALSE) so the post renders without needing the extension packages installed.
  • Placeholder URLs used for the 3.1 announcement and the upgrading.html vignette — worth confirming the published slugs.

🤖 Generated with Claude Code

Covers the two reasons for the release: consistent resource setting and
the fix that lets extension packages be chained in any load order, with a
worked mizerReef + mizerMR example. Also summarises the smaller additions
in 3.2.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EyeA3WdYPB8TFo8Pssh1Kw
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant