In the Guidewire Cloud Platform (GWCP) development lifecycle, effective source control management is essential for maintaining a stable path to production. Guidewire recommends a specific branching strategy tailored for InsuranceSuite implementations using Git (typically hosted in Bitbucket).
The Project Release branch (often named release/*) serves a very specific purpose: stabilization. According to the " Developing with Guidewire Cloud " course, the standard workflow involves developers working on feature branches and merging them into a develop or integration branch. Once a set of features is deemed complete for a specific deployment cycle, a Release branch is created.
The primary goal of this branch is to isolate the release-ready code from the ongoing, potentially volatile development occurring in the main integration branch. On the Release branch, the team performs final GUnit testing, regression testing, and bug fixes specifically identified during the QA phase for that version. No new features should be introduced here. This isolation ensures that the " Candidate for Production " is stable and that any fixes applied are strictly for high-priority issues.
Option A refers to the master or main branch, which holds the current production state. Option B describes the function of feature or development branches. Option D is incorrect because product releases from Guidewire are provided as base code updates, which are typically merged into the customer ' s repository rather than existing as a " Project Release " branch. By focusing on stabilization, the Release branch minimizes the risk of introducing " noise " or untested features into the final production deployment.
