05-10-2015, 07:44 PM
@ThuGie The problem is that model you then need to stop developing features into master, whilst you're stabilizing it for testing. because otherwise you will never get something that can be promoted to stable. Which means testing will either be a copy of master, or an imutable branch thats the same as release. There is never any point in having a testing branch. Its primarily for when master and testing are actually on different hardware, or when the release process is slow.
What we want to do is to go through the feature freezes on testing, and then master can keep working on features whilst testing stabilizes.
What we want to do is to go through the feature freezes on testing, and then master can keep working on features whilst testing stabilizes.