We previously agreed to support upgrades over two versions at anytime. E.g., we could support 2.0 -> 2.2 in master, but any migration logic prior to 2.0 in master could be removed from the code.
Since the latest branch is 2.5, if nothing has changed we should support upgrading from 2.1 -> 2.5, but anything <= 2.0 can be removed from the codebase. Best, Kevin On Fri, Jan 15, 2016 at 4:05 AM, Tim Guan-tin Chien <[email protected]> wrote: > Hi, > > With the "pivot to connected devices" and the fact that v1.x devices > are fall out of partner support, do we still care about the > possibility of having these profiles being upgraded to v2.6 (current > master) *directly*? > > I am looking at, particularly, preferences saved in mozSettings. > Dropping those support will help us free up development time on > supporting future products, and also help us making booting the (even > brand new phones) faster*. > > * See https://bugzilla.mozilla.org/show_bug.cgi?id=1095034; we have > not exposed things like DB_VERSION to Gaia so Gaia System has too > check for *every* old keys *everytime* the System boots. At least it > would have to check a version flag set and we unfortunately have not > yet concentrate all the migration there ** > > ** Like the badly-written keyboard layout migration > https://bugzilla.mozilla.org/show_bug.cgi?id=1180607 which no longer > need to be checked for post 1.3 new phones. > > > Tim > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
