On 7/31/12 4:57 AM, Jonathan M Davis wrote:
The simplest way to do this would probably be to branch for a release whenever we do a beta. We then continue to merge stuff into master as normal. But when there's a fix that we need for the beta, we cherry pick it from master and put it in the release branch. And when the release is finally ready to go, we tag the appropriate commit on the release branch, and that's the release. That way, doing a beta does not halt normal development at all. Rather, it's done in parallel.
Yah, I think that's a good way to go. We should start that practice now and refine it (e.g. with x.y.z releases) later.
Andrei
