Pending updates till Jan '25

[kitallis]

• Finalization of release: Automatic release finish
• Supported versions: SemVer, Partial SemVer, CalVer
• Changeset Tracking: Changelog since last release, ongoing work, latest applied commits
• Latest build numbers are fetched
• Previous workflow runs are cancelled
• Scheduled releases
  • All the ways in which it recovers / skips
• Internal Groups are also available in TestFlight
• Almost Trunk creates a merge-back PR at the end
• Build queue
• Backmerges (continuous or otherwise)
  • Differences between integrations
• DevOps charts (explain each chart)
• Reuse integrations
• Integrations requiring configuration before they are set up
  • Disconnects are allowed to some degree
• Default submission configuration
  • Artifact name pattern, suffix, auto-submit, mandatory things
• Cascading rollouts
• Staged rollout
• Purpose of multiple trains
• Notification settings (give usage examples)
  • How is a build shared over slack
  • Deep link to build download
• Hotfix releases + patch fix releases
  • Single platform hotfixes possible
• Teams in organization and its eventual purpose
• Update all the new integrations
  • Mention the build download oddity for BitBucket
  • Default to deploy action for GitHub at least
  • Also mention the upcoming ones
• SSO
  • Automatic viewer login
• How do release phases work / how do changes get build while stabilizing release
• Upcoming releases
• Auto-correction of version with partial SemVer
• App variants (Firebase only)
• Approvals (copy overs)
• Release captain and their role
  • Captain's Log
• Cross-platform releases
• Checks and balances
  • no diff since last release
  • no finalization without merge
  • correct tag for hotfix
  • locking upcoming prod rollout
  • block production for approvals
• Write better event timeline usage
• Multi-locale metadata
• Retries through the submission
• Review failure handling
• Changes between store builds / store versions
• Custom build metadata
• Custom release version
• Draft mode in Play Store
• Handling Managed Publishing on Play Store (or lack thereof)
• General differences between how store submissions work

[nid90]

Broken link on the homepage for the why page of Tramline website.

[nid90]

The link for the self-hosting docs are not properly linked to the correct section in the README.

[kitallis]

Basic structure / outline and order of the new stuff:

getting-started
integrations
├── [reuse integrations]
├── [integrations requiring configuration before they are set up]
├── [Disconnects are allowed to some degree]
├── [Mention the build download oddity for BitBucket]
├── [Default to deploy action for GitHub at least]
└── [Also mention the upcoming ones]
using-tramline
└── submission config
├── app overview (FIGURE OUT NAME)
│   ├── [DevOps charts (explain each chart)]
│   ├── [order of release snapshots]
│   └── [historical]
├── prepare new release
│   └── [custom release version]     
├── releases
│   ├── [How do release phases work]
│   ├── [how do changes get build while stabilizing release]
│   ├── release captain
│   │   └── [captains log]
│   ├── kickoff
│   ├── changeset tracking
│   ├── stability
│   │   ├── [Previous workflow runs are cancelled]
│   │   ├── [Changes between store builds / store versions]
│   │   ├── [Retries through the submission]
│   │   ├── [Internal Groups are also available in TestFlight]
│   │   ├── internal builds
│   │   ├── regression testing
│   │   ├── release candidates
│   │   └── beta soak
│   ├── release metadata
│   │   └── [Multi-locale metadata]
│   ├── screenshots
│   ├── approvals
│   ├── store releases
│   │   ├── app submission and review
│   │   │   ├── [Review failure handling]
│   │   │   └── [Handling Managed Publishing on Play Store]
│   │   └── rollouts
│   └── finalizing the release
│       └── [how does automatic work]
├── build matching
├── version management
│   └── [Auto-correction of version with partial SemVer]
├── build number management
│   └── [latest build numbers are fetched]
├── upcoming releases
├── branching strategies
├── versioning strategies
├── patch fixes
├── hotfixes
│   └── [Single platform hotfixes possible]
├── backmerges
│   ├── [Almost Trunk creates a merge-back PR at the end]
│   └── [continuous + Differences between integrations]
├── synchronized releases  
├── scheduled releases
│   └── [All the ways in which it recovers / skips]    
├── release health monitoring
├── release audit log (rewrite)
├── notifications
│   ├── [How is a build shared over slack]
│   └── [Deep link to build download]  
├── alternate release cycles
├── approvals
├── build queue
├── app variants
├── cascading rollouts
├── differences between store submissions
├── draft mode
└── build insights
    └── [custom build metadata]
reldex
automations
check and balances
├── no diff since last release
├── no finalization without merge
├── correct tag for hotfix
├── locking upcoming prod rollout
└── block production for approvals
team & memberships
└── sso
    └── [Automatic viewer login]
api
getting support