Interim Release and Move to Monthly Stable Cadence

[akashsriramganapathy]

The four-month gap since v0.28.1, which left 350+ commits piled up in master. Releasing all of this at once is heavy for one developer and overwhelming for users. While nightly builds exist, many people only rely on stable releases. A monthly cadence would break the work into smaller chunks and give users smoother, easier updates.

We suggest two steps:

1. Publish a stable release soon to clear the backlog.
2. Move to monthly stable releases going forward.

This way, nightly users still get cutting-edge updates, while stable users receive steady, reliable fixes and features without long waits.

[dhanuarf]

Wouldnt this break the purpose for splitting up builds (stable and nightly) in the first place?

'Stable' build is supposed to a bug-free experience (although in reality they're not completely bug-free). These builds are targeted for general public users, who have little to no experience on technical stuff. So realeasing 'stable' builds monthly doesnt guarantee that build to be stable, which breaks the purpose of the name "stable".