What is the criteria and plan for the next release?

[chebread]

I have a question regarding the release process for devd.

With the recent PRs successfully merged (fixing localhost routing, updating Go modules, etc.), the codebase has been significantly improved. I am curious about what the criteria are for cutting a new release.

I am cautious about proposing a new release directly. However, in my personal opinion, devd is currently in need of a new release so that users can actually benefit from these recent improvements, rather than being stuck on the old v0.9 binaries.

Could you share how the timing for a new release is typically decided for this project?

[wader]

Agree, it would be nice with a new release once we merge most of the maintenance stuff. Maybe should figure out a release build plan also? https://goreleaser.com, something else or just "manual" script in github actions that builds various binaries and copy artifacts?