Post AjyA8peLSyucTuhHVo by serebit@floss.social
 (DIR) More posts by serebit@floss.social
 (DIR) Post #AjyA8peLSyucTuhHVo by serebit@floss.social
       2024-07-13T21:37:13Z
       
       1 likes, 0 repeats
       
       @emersion I say keep it simple. If you're already doing the "slow period to fix bugs" thing for wlroots, you may as well tag an RC at the start of that slow period, and maybe tag new RCs every N weeks until you're satisfied with its stability.For example, you could finalize the feature set and API in 0.19, tag 0.19.0-rc1, and then tag new RCs every 2 weeks until there are no more blocking bugs—THEN tag 0.19.0 in place of a final RC.(1/2)
       
 (DIR) Post #AjyA8rxYsVTJe5hek4 by serebit@floss.social
       2024-07-13T21:39:55Z
       
       0 likes, 0 repeats
       
       @emersion By formalizing the slow period and making it obvious to downstreams, you would make it easier for us to jump onto a new version of wlroots before release. This benefits us by helping us line up a new release of our compositors with the new version of wlroots, and benefits you guys by giving us incentive to file bugs against release candidates. (2/2)