Closed
Bug 1089962
Opened 11 years ago
Closed 10 years ago
Notify client when reviewboard extension is out of date
Categories
(MozReview Graveyard :: General, defect, P3)
MozReview Graveyard
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1177945
People
(Reporter: gps, Unassigned)
Details
We want users to have the best MozReview experience possible. That only happens if they are using the latest/greatest version of the reviewboard extension and the version-control-tools repository.
Let's have the client submit the changeset of vct their reviewboard extension is coming from so we can have the server issue a warning when it is out of date and they need to upgrade. We'll probably maintain a hard-coded "oldest acceptable commit" in the server and do some DAG traversal to identify whether the client is older.
We can sneak this in post release because omission of the vct node from the client means its too old and we can always alert in that case :)
There *might* be a small performance penalty associated with this. We should measure that as part of implementing it.
Comment 1•10 years ago
|
||
We have too many P1s, so I'm spreading out the priorities. P3 -> P4, P2 -> P3, and some portion of P1s will become P2.
Priority: P2 → P3
Comment 2•10 years ago
|
||
:gps, I thought you fixed this as part of a separate series a while back?
Flags: needinfo?(gps)
Reporter | ||
Comment 3•10 years ago
|
||
Yes, I did this work as a very roundabout way of implementing auto publish in bug 1177945.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(gps)
Resolution: --- → DUPLICATE
Assignee | ||
Updated•9 years ago
|
Product: Developer Services → MozReview
You need to log in
before you can comment on or make changes to this bug.
Description
•