Branching strategy for parallel development that won't be in the same release?
- by Telastyn
My team is working on a product, which for business reasons needs to be released on a regular schedule. An issue has arisen where we want to do development in parallel for the upcoming release, as well as the 'next' release. This is to become standard practice, so it's not as straightforward as cutting a feature branch for the new work. We'll continually have 2+ teams working on different releases of the same product.
Is there an SCM best practice for this sort of arrangement?