What's the best version control/QA workflow for a legacy system?
- by John Cromartie
I am struggling to find a good balance with our development and testing process.
We use Git right now, and I am convinced that ReinH's Git Workflow For Agile Teams is not just great for capital-A Agile, but for pretty much any team on DVCS. That's what I've tried to implement but it's just not catching.
We have a large legacy system with a complex environment, hundreds of outstanding and undiscovered defects, and no real good way to set up a test environment with realistic data. It's also hard to release updates without disrupting users.
Most of all, it's hard to do thorough QA with this process... and we need thorough testing with this legacy system.
I feel like we can't really pull off anything as slick as the Git workflow outlined in the link. What's the way to do it?