...
Part of the release process, merge code changes to “stable” branch whenever we are ready for release. We could do bi-weekly or anything that stakeholders want (when we make Prod customer facing).
In the interim till we have a customer facing Prod, we can do a merge when the leads think they have an non-breaking addition. We can use the Scrum of scrums or some shared meeting to decide. Managers can check with the leads around end of sprint to see when can we release something non-breaking (because the codebase itself is lot unstable and new features tend to be incomplete at the end of sprint/don’t align with sprint schedule). There might be inconsistencies/breakage in stable branches during this time, but the developer who made the change can fix it as the first priority.
...