Transcript
Here, I have four open pull requests against production. However, perhaps only two have been approved for the next release.
Currently, we know these features validate successfully against production, but these have only been checked independently.
We don't yet know if these play well together.
A release into production will often contain multiple stories. So by opening a release, I'm now having gearset merge these separate features onto a common branch and gearset will compile and validate the whole release against production.
Of course, I can also add further pull requests to the release branch throughout this sprint. And in the Git repository, I'll find a clear paper trail of the release and the stories involved providing clear auditability.
Once the validation has run, I'll then have the option to either deploy now or schedule these releases to automatically deploy at my chosen time.
It's also possible to create multiple releases for various peer, work streams so that you can continually add PRs to these, have these validate to provide confidence they'll deploy successfully, and schedule them for the appropriate time.
So releases in GearSet ensure a streamlined, auditable, but also flexible release process to align seamlessly with the deployment schedule you're working towards for your clients.
