...
- During normal feature development, if a developer identifies a change that needs to be applied to the entire codebase, they open a new JIRA and assign it to the next SCUC SCU release. No work starts on the change at this point. The developer responsible for overseeing this change is the assignee of the ticket.
- Once the final release of the current feature release is tagged, the Release Manager declares that it is time for the Synchronous Code Update work to begin.
- If there are no JIRAs in the next SCUC SCU release, development proceeds to the next general feature release.
- During the checkpoint, no commits may be made to develop except those associated with SCUC SCU issues. Multiple SCUC SCU issues can be worked on in parallel if they are not dependent on each other.
- The expectation here is that there is no "in flight" work, however, if a developer is already working on a new feature for the next release, then it is that developer's responsibility to ensure any code for the new feature is updated as needed for the SCUC SCU issue(s) being addressed addressed before the new feature is committed to develop. The Release Manager may remind the developers of this requirements, but it is the developer's responsibility to adhere to it.
- Once the SCUC SCU issues are resolved, the SCUC SCU release is completed and work continues to the next feature release. The SCUC release SCU release does not result in a public release.
...