we are moving towards complete DirectAdmin and CustomBuild integration, but this is not something we can do in a single step. Next step would be to deprecate DA autoupdates via CustomBuild leaving only DA built-in auto-update functionality. Much simpler than re-implementing gradual rollout in CustomBuild.
we really like the DirectAdmin and CustomBuild merge. This makes it much easier to ensure software compatibility compared to the situation we had before where you could be running very old DA with latest CB, or latest DA with extremely old CB. Without tight coupling of DA and CB we could not easily make the native CustomBuild integration in Evolution we have right now. So long story short - we knew very well this will be a breaking change (breaking change in DA/CB behaviour) and the consequences it would bring, and pros of this decision still out-weights the cons
This is my case, with the 1.645 release, all the problems was fixed after 11 hotfixes , when a problem goes live we as hosters can get hundreds of reports of our clients, for you can be only one license, for us can be 100 clients , so to avoid this for this week I configured on all my directadmin instances "autoupdate=0", but today all my servers are on the 1.646 version caused by the custombuild cronjob, and at 8 AM (GMT-3) we start to get reports of problems (the json problem fixed in the first hotfix of this release), the DirectAdmin staff need to see this from our shoes, and if I'm (We?) discussing this isnt for fun, this is a real problem(dont have a real control of when an update its applied) for our me (us?) as service provider.
You can said "so why you dont change the update channel to stable", yesterday (and still today) the stable version is 1.644 and based on the custombuild behavior all my DA instances will be downgraded from 1.646 to 1.644
# dig stable-version.directadmin.com txt +short
So if you are on the 1.645 version isnt way to still in that version if you are using custombuild cron or ./build update, the only choices are 1.644 or 1.646....
May be a way to avoid this kind of situations, bump the stable version before the release of the new version, at least 10 minutes before (based on the dns TTL of 5 minutes of stable-version.directadmin.com txt record).
and "we are moving towards complete DirectAdmin and CustomBuild integration, but this is not something we can do in a single step.", I agree with this, but this change in custombuild can be done "quickly" without integrate all the functions in one step, as a "hotfix"