Definitions¶
| Branch | Definition | Supported Devices | Description | Stability/Readiness |
|---|---|---|---|---|
release |
Release branch | Comma 3X | Stable release branch. After testing on staging, updates are pushed here and published publicly. |
Ready to Use: Highly stable, recommended for most users. |
staging |
Staging branch | Comma 3X | Pre-release testing branch. Community feedback is essential to identify issues before public release. | Varied Stability: Generally stable, but intended for testing before public release. |
dev |
Development branches | Comma 3X | Experimental branch with the latest features and bug fixes brought in manually. Expect bugs and braking changes. | Experimental: Least stable, suitable for testers and developers. |
master |
Primary development branch | Comma 3X | All Pull Requests are merged here for future releases. CI automatically strips, minifies, and pushes changes to staging. Running the master branch is suitable for development purposes but not recommended for non-development use. |
For Development Use: Suitable for developers, may be unstable for general use. |
release-tici |
Release branch | Comma 3 | Stable release branch. After testing on staging-tici, updates are pushed here and published publicly. |
Ready to Use: Highly stable, recommended for most users. |
staging-tici |
Staging branch | Comma 3 | Pre-release testing branch. Community feedback is essential to identify issues before public release. | Varied Stability: Generally stable, but intended for testing before public release. |
Tip
Your feedback is invaluable. Testers, even without software development experience, are encourage to run dev or staging and report issues.