You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Proposal: Weekly Stable Releases with Major Bug-Fix Exceptions | 建议:每周发布稳定版(重大 Bug 修复除外)
#7428
Could OpenViking consider moving to a predictable weekly stable release cadence, rather than publishing stable releases frequently?
A possible workflow:
Publish one stable release each week after the usual CI and regression checks.
When a candidate needs wider validation, publish a prerelease first, then promote it to the final stable release once it is ready.
Allow an out-of-band stable release when needed to fix a major bug.
A regular cadence would make upgrades, testing, and deployment planning more predictable while still leaving room to address major bugs promptly. Would the maintainers consider this approach?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
English
Could OpenViking consider moving to a predictable weekly stable release cadence, rather than publishing stable releases frequently?
A possible workflow:
A regular cadence would make upgrades, testing, and deployment planning more predictable while still leaving room to address major bugs promptly. Would the maintainers consider this approach?
中文
请问 OpenViking 是否可以考虑采用更可预期的每周一次稳定版发布节奏,而不是频繁发布稳定版?
一种可行的流程是:
固定的发布节奏有助于用户更好地安排升级、测试和部署,同时也能及时处理重大 Bug。维护者是否会考虑这种方式?
All reactions