Release 0.19.2 scope of work discussion #675
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
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:
ModelSaversave-path collision for SeedVR2, then add its tiny test #621
CUDA
All reactions
Replies: 4 comments 7 replies
All reactions
during the repo flag period i could not publish 0.19.1, I can do that now from the main branch state?
All reactions
-
👍 1
I think so. Recent commits were more bugs and nits, not be fears.
All reactions
@plz12345 @ianscrivener @fxd0h @filipstrand lets try out this peer-approved release process!
imageAll reactions
-
👍 2
All reactions
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.
All reactions
-
👍 1
No biggie, just looked weird to me and figured it was some pypi cooldown.
All reactions
-
👍 1
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.
All reactions
-
👍 1
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).
All reactions
It was the "every two or three days" bit. Maybe I misinterpretted it.
All reactions
-
👍 1