<!DOCTYPE html><html><head><title></title></head><body><div>Hi,</div><div><br></div><div>Looking at the recent history, I think we could have cut a release at any point in time and there wouldn't have been any issues with the release. So yes, I do think that simplifying and shortening the release process makes a lot of sense!</div><div><br></div><div>On Tue, May 20, 2025, at 10:03 PM, Simon Ser wrote:</div><blockquote type="cite" id="qt" style=""><div>Hi all,</div><div><br></div><div>With years passing by, development in the main Wayland repository has</div><div>slowed down quite a bit, activity has moved over to wayland-protocols</div><div>and compositors. However, cutting a new Wayland release is still a</div><div>heavyweight process: it takes at least one and a half months with at</div><div>least 3 pre-releases. I'm also not sure about the value of all of these</div><div>pre-releases: historically they've been used to push the last features</div><div>over the fence before the RCs, but it's easy enough to talk and</div><div>coordinate over the bits that we want to wait on for the release.</div><div><br></div><div>I would suggest to drop the alphas/betas from the release process, ie.</div><div>go straight to RC1. The process would then continue as usual, with</div><div>weekly RCs. As a release manager this would help reduce the load. This</div><div>is also what I've been doing for Sway and wlroots for a very long time.</div><div><br></div><div>Would this make sense? Are there other reasons why alphas/betas were</div><div>valuable?</div><div><br></div><div>Thanks,</div><div><br></div><div>Simon</div><div><br></div></blockquote><div><br></div></body></html>