Allow incrementing Translation model versions while maintaining compatiblility with previous versions
Categories
(Firefox :: Translations, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox135 | --- | fixed |
People
(Reporter: nordzilla, Assigned: nordzilla)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
Description
The fix from Bug 1926100 introduces a cutoff point at which our larger "base" models are only compatible with versions of Firefox that contain that patch.
Likewise, the switch to the Bergamot WASM binary version 2.0 from Bug 1917851 introduces a similar cutoff point at which CJK models will only be compatible in versions of Firefox that contain that patch stack.
However, all of our current 1.x version models are compatible with both of the above source code changes. As such, we need to introduce a way to increment our model versions while still utilizing previous models that are backward compatible with the new changes.
We should adjust the hard-coded model versioning constraints for the models to be a range of major versions, rather than a single major version. This will allow us to increment the maximum supported version while maintaining the minimum supported version.
Assignee | ||
Updated•9 months ago
|
Assignee | ||
Comment 1•9 months ago
|
||
Renames the getMaxVersionRecords() function to
getMaxSupportedVersionRecords() because I think
it improves overall clarity and readability.
The record that is retrieved may not be the absolute
maximum record, but only the maximum that is supported
in this version of the source code.
Assignee | ||
Comment 2•9 months ago
|
||
Renames LANGUAGE_MODEL_MAJOR_VERSION to
LANGUAGE_MODEL_MAJOR_VERSION_MAX in preparation
for the changes following patch. This will reduce
noise and make the overall review of the logical
code changes easier to digest.
Depends on D231316
Assignee | ||
Comment 3•9 months ago
|
||
This patch improves the strategy around how we tie supported
Translations model versions to the source code by allowing us to
introduce new model versions while also allowing forward-compatible
models with older versions to still be used.
Depends on D231317
Assignee | ||
Updated•9 months ago
|
Updated•9 months ago
|
Updated•9 months ago
|
Updated•9 months ago
|
Backed out for causing junit failures.
Assignee | ||
Comment 6•8 months ago
|
||
I believe that I have fixed the issue on Android.
The junit tests are looking clean on the latest try run:
https://treeherder.mozilla.org/jobs?repo=try&revision=7c264c26e8f32892043d8cf66def5662c8fd3b97
Going to try re-landing.
Comment 8•8 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8d7743d3408a
https://hg.mozilla.org/mozilla-central/rev/6db34740bb10
https://hg.mozilla.org/mozilla-central/rev/03677f24ea9a
Description
•