v0.23.0 planning

[AkihiroSuda]

Or just release v0.22.1 from the current master, after merging this one, but before merging other major changes

Originally posted by @AkihiroSuda in #2511 (comment)

[jandubois]

Every patch release has always updated templates

Ok, but I would argue that is not proper for a patch release; it should only fix bugs, not change functionality.

Even more so if the change includes removing features/templates (centos-stream-8, deprecated/centos-7).

I guess it doesn't really matter, it is just a question of policy. But it is not like we are running out of minor version numbers.

[afbjorklund]

Updating snapshots should be OK, though. That is, just changing dates and digests of existing releases.

Even the bumping of minor releases, of those RHEL distros that follow a major track... But not removal.

[AkihiroSuda]

@lima-vm/maintainers @norio-nomura
For v0.23, shall we skip:

• docker{,-rootful}.yaml: Use param in docker templates #2515

I assume we do not have to revert:

• limayaml: add a param field for defining variables used to customize scripts and other elements within lima.yaml. #2498

[AkihiroSuda]

@lima-vm/maintainers

Let me release v0.23 after merging

• Revert "Temporarily disable CI on archlinux"  #2543

and bumping up the templates.

Then we can merge the PRs associated with the v1.0 milestone and release v1.0 beta.