On Thu, 2012-11-29 at 12:45 +0100, eskimo wrote: > That is pretty much what I had in mind, but more concrete thought > through. I really like it :-) The only things to clear up would be, how > long must a release branch exist, before it is considered stable. Which > depends on how stable we want things to be. > > > On Thu, 2012-11-29 at 11:35 +0100, foobar wrote: > > This was mentioned in the group numerous times before, here's one > > more time to increase awareness even more: > > git flow - http://nvie.com/posts/a-successful-git-branching-model/ > > should be easily adapted for the D development process. >
We would then simply do regular dev releases of the development branch (which is pretty much the releases we have now), so many people test the stuff. Then lots of beta releases from the release branch and after six months or so, the final stable release is made.
