Design a Process for updating the Glean SDK & glean_parser in mozilla-central
Categories
(Toolkit :: Telemetry, task, P1)
Tracking
()
People
(Reporter: chutten, Assigned: Dexter)
Details
(Whiteboard: [telemetry:fog:m2])
Attachments
(1 file)
Project FOG uses both the Glean SDK and glean_parser
. On Android, Gradle can be used to keep these up-to-date and in-sync.
In m-c we're currently relying on a fairly manual process for vendoring glean_parser
(bug 1602773), and the Glean SDK is coming in via mach vendor rust
thanks to artefacts published to crates.io (bug 1596132).
Propose a process to update the sdk and parser that will
- Keep them in sync
- Be straightforward if not also simple
- Does not require special roles/powers that only a few team members will have
- Understands that the release schedule of the Glean SDK and Firefox Desktop and Geckoview are not required to line up
This process may rely on humans to start, but it'd be ideal if it considered how we might use tooling to reduce the effort in future. This design should probably also include a survey/summary of how and how often these pieces have updated in the recent past.
This process will be documented in the Project FOG documentation (bug 1618910) after it has been proposed and accepted.
Assignee | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Reporter | ||
Comment 2•5 years ago
|
||
Comment 3•5 years ago
|
||
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
Closing this, all the feedback in the doc was addressed!
Description
•