Working Pane
When you start a new release, this page is your work pane. Everything about the current release is controlled from right here. You will likely spend most of your time in Tramline here.
This is what a typical successful release in Tramline looks like:
The work pane is auto-structured into four main sections:
- Kickoff: Overview, changeset tracking and the homepage for the Release Captain.
- Stability: Internal builds, Release Candidates, testing (coming soon).
- Metadata: Dedicated space for updating notes, store metadata.
- Store Release: Managing reviews and rolling out to production.
The tabs are alive — they always track the current state of that section — whether it's in progress, completed or pending. They also automatically get switched over to the most important tab in the current release.
Jump to
📄️ Overview
This tab of the work pane is the default starting tab when the release starts or once it is finished. It summarizes all the information about the release. This summary is dynamic while the release is in progress, but remains frozen once the release is completed.
📄️ Changeset Tracking
There is one dedicated page to track all the commits, PRs and changes going into the release.
📄️ Stability
There are a few things Tramline does as soon as the release starts:
📄️ Notes and Metadata
You can update release-related metadata prior to initiating your production store release. These details can be modified anytime between the beginning of the release and the commencement of a production deployment, as the metadata will be uploaded to the store during the production deployment process.
📄️ Screenshots
Screenshots are not yet supported. They are coming soon!
📄️ Approvals
Tramline supports an approvals system that allows you to add high-level approvals from various stakeholders for the release.
📄️ Store Releases
The production release across both stores in handled by Tramline slightly differently due to the different processes of these stores.
📄️ Finalizing the Release
Once the build has been successfully distributed to all channels in the release step, you can finalize your release.