paulcurtis
Veteran
Thanks for the honesty Mitch, it really is appreciated and helps put my mind at rest, even if there are daily struggles with bugs and quirks.
It it sounds like you need an even more intense beta / bug squashing phase. Or maybe even a public beta where many people represented here would be more than happy to help out by testing. I know there's always the risk of someone using a beta on a live shoot and coming unstuck, no matter how much you say the beta shouldn't be used as such - maybe a beta could have a watermark to prevent that. I know I'd still be happy to test even if I couldn't use it in production.
Public betas aren't such a bad idea because a lot of folk here are individuals rather than large productions and do have the ability to do the beta thing during downtime and everyone here has such a different set up and perspective. Hand in hand with a formalised bug tracking solution otherwise that could overwhelm. Software companies like the foundry (nuke et al) have a very organised way of handling this.
AFAICG (can guess) CD are working with FGPA programming which complicates matters? Otherwise when running most source control systems branching a new build whilst maintaining current builds is a standard operating procedure - something like microsofts TFS allows for branching and merging of codebases in this way. I presume that's why it's more difficult bouncing between builds.
cheers
Paul