Enterprise teams rarely ship one change at a time. They often have multiple streams of work moving at different speeds, with dependencies that need to converge safely.

Early bundles, release candidates and long-term projects support these workflows in different ways. The right option depends on whether you need to coordinate related work, rehearse a Production release, or isolate a long-running project.

An early bundle combines a subset of related features at a nominated environment where work streams converge. The bundle then moves through the pipeline as a single unit and can later be included in a release candidate or release.

Use one when several ready features or dependencies belong together and promoting them separately would create repeated conflicts, validations or coordination work.

Learn more about bundles here.

A release candidate combines the complete scope of an upcoming Production release in the nominated penultimate environment.

Use one when that environment closely represents Production and you want to validate and test the complete package before release day. When promoted, the release candidate becomes the release in the final environment.

Learn more about release and release candidates here.

A long-term project creates a sub-pipeline alongside your main pipeline. It allows project work to progress independently before feeding back into the main delivery workflow.

Use one when project work needs to remain separate from day-to-day releases and move through testing at its own pace. Read more about Long term project here.