Release 0.19.2 scope of work discussion

[ianscrivener]

Guys,
Wanted to start the ball rolling on the discussion on the next release.

@fxd0h do you want to do a mini release with what we have so far?

After the release I'll human write some copy that we can post to X, Reddit etc...

Here's an initial suggestion;

Chores

• chore: bump mlx to v0.32.2 #674
• chore: bump mlx to v0.32.1 #647

Release & CI Uplift

• Interface consistency fixes from the growth-week audit (P1) #578
• improvement: uplift release process removing the manual CHANGELOG.md #673
• improvement: review CodeRabbit & Greptile suggestions for .github/workflows/release.yml #648
• chore: refactor AI Agents - not everyone uses Cursor #626

Model Saving Issues

• bug: AttributeError: '[model_name]' object has no attribute 'save_model' #667
• Chore/fix: ModelSaver save-path collision for SeedVR2, then add its tiny test #621

CUDA

• CUDA rendering fails on some on MFlux quantised models (fix hinted at) #563
• bug: AttributeError: '[model_name]' object has no attribute 'save_model' #667

[ianscrivener]

@anthonywu @fxd0h @plz12345

[anthonywu]

during the repo flag period i could not publish 0.19.1, I can do that now from the main branch state?

[plz12345]

I think so. Recent commits were more bugs and nits, not be fears.

[anthonywu]

@plz12345 @ianscrivener @fxd0h @filipstrand lets try out this peer-approved release process!

[plz12345]

[anthonywu]

I hope you guys don't mind the timer. It is an zen opportunity to look at what is being pushed and a last chance to catch any unintended inclusions or worse.

[plz12345]

No biggie, just looked weird to me and figured it was some pypi cooldown.

[fxd0h]

The 0.19.1 that just went out covers the mini release. Going forward I'd cut a small release every two or three days whenever merged work is worth shipping, and keep majors for an integration that actually earns one. On the list: #578 is done and can just close, and #647/#674 are the same bump twice.

[plz12345]

Disagree on time-based versioning, it's already in SemVer format. Suggest instead

major - when we circle back to the CLI refactor, that big scale where the big 1.0 is merited.
minor - new model added or single model changed in a big way
patch - bug fixes and small tweaks (can be batched, but suggest keeping it to < 10 commits).

[ianscrivener]

@plz12345 Did somebody suggest time-based versioning? Where was that? I must have missed it.

@fxd0h seems to just want to release two or three times a week. I'm good with that.

0.19.99 anyone?!

[plz12345]

It was the "every two or three days" bit. Maybe I misinterpretted it.