We did not agree with waddlesplash on this, so we settled on a compromise:
- We create a branch for beta1
- Development continues as usual in trunk
- After the beta1 release, I will keep cherry-picking bugfixes and well-tested features into the beta1 branch
- We can later see wether it makes sense to release beta2 from trunk, or from the beta branch with extra bugfixes
This means we have a “stable” channel starting from beta1, and we’ll see if it’s worth the effort or not. alpha and beta releases are also a way to experiment with the release process to see what works and what doesn’t.
In my view, if the plan is to just “code drop” the beta and then go on as usual with making changes to the trunk, we may have new bugs getting there and then it could take years before we have something stable enough to be a beta release again. Of course people will then be using the nightlies, and complain about how things keep getting broken, how software used to work but doesn’t anymore, how an old video driver worked on their hardware, but the new version doesn’t, etc.
I find this unacceptable, so I would prefer to provide a more stable version of Haiku. It may also help us compare two “live” codebases especially when debugging driver problems. I don’t have a problem with adding new features, I just want to make sure they don’t do more harm than good. And when people really want something from the nightly, it means it’s time to integrate it in the release channel, or maybe start thinking about R2.