Track version number of active moz-phab installations
Categories
(Conduit :: moz-phab, enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: mhentges, Unassigned)
Details
(Keywords: conduit-triaged)
We're having issues with self-update on Windows.
There's workarounds (e.g.: delay deletion of old versions) but they could require a nontrivial amount of work to set up.
The current solution is to inform users when their moz-phab is out of date and tell them the pip command to run to auto-update.
However, we need to know how well this solution is working, and how necessary it might be to invest in auto-update anyways. To give us the information to make that decision, we should track how fragmented and out-of-date Windows moz-phab instances become.
Goals:
- Ideally, we'd have a nice dashboard that shows us which versions of
moz-phabwere used in the last week, and how much each version was used - We're going to want to be careful with telemetry - perhaps adding the
moz-phabversion to our request to Phabricator is acceptable?
|
Reporter | |
Updated•4 years ago
|
|
||
Comment 1•4 years ago
|
||
Currently we're sending moz-phab-hg, moz-phab-git or moz-phab-git-cinnabar.
We would like to add a version number.
Will moz-phab-0.1.74-{vcs} be a good option?
Appending the version number would make it easier to grep the logs, as would using a different delimiter - moz-phab-{vcs}:{version}
This is covered by the telemetry work in Bug 1621025.
Description
•