Hi, It is painful to wait for the next beta, especially when PRs fixing ci are in queue.
It would be nice if a beta release is made automatically every week. Since a github workflow may run like a cronjob, this seems doable. Let's call it "beta (release) manager". Some ideas for the beta manager. 1. The beta manager runs only if the previous release was also a beta. 2. The beta manager keeps a special branch "beta_branch" that is always based on "develop" branch. 2. At the end of the week, the beta manager merges "beta_branch" to "develop" branch, and make a beta release. 3. During the week, the human release manager keeps adding PR branches to "beta_branch" The beta release manager may do some smart things to keep the beta release as stable as possible. The beta release manager is basically a helper to our human release manager. He should keep the button to switch on and off the beta bot. As I don't know the precise workflow and concerns of the release manager, this idea may be unrealistic. What do you think? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/23f3cd3a-abd9-45c4-a62f-97394256739cn%40googlegroups.com.
