I sometimes ask users to test a try build to verify that the build fixes their problem. This is an important tool, especially when the problem is hard to reproduce or when the definition of “fix” is a bit nebulous (as it sometimes is in performance-related bugs).
However, I don’t want to run the risk of causing users to lose data when they test these builds! That’s especially true in light of the fact that we sometimes make backwards incompatible changes to on-disk data structures between releases (like the recent IndexedDB changes), which could result in users being stuck on Nightly if they experiment with a try build. We do have instructions available for changing profiles, and for backing up and restoring your profile, which would mitigate this issue to an extent: https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data?redirectlocale=en-US&redirectslug=Profiles <https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data?redirectlocale=en-US&redirectslug=Profiles> In my opinion, though, these instructions are *way* too complex for less-technical users. Making a mistake when following these instructions could result in data loss in some cases, as well, which is exactly what I’m trying to prevent. And even for more experienced users, backing up and restoring a profile or switching profiles manually is tedious as implemented today. I think one way we could reduce the burden on users would be to just make try builds default to a different profile than channel builds. Can we do this? Any better ideas? - Seth _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
