mozilla-releng / mozilla-releng/relengdocs
Document the process for adding a new platform to the Firefox release pipeline
Open
@gabrielbusta is already working on this.
Since Feb 3, 2025.
- Dominant language
- Python
- Stars
- 10
- Forks
- 25
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 2
Description
The process for adding builds for a new computing platform is only documented in Bugzilla (as far as I know.)
It would be useful to have a How-To guide that outlines the common requirements, like l10n changesets and bouncer entries, for example.
Since past bugs can be used as references to piece together the process, having a document seems feasible and would make it easier to repeat.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.