On Wed, Apr 8, 2015 at 4:06 PM, Mike Hommey <m...@glandium.org> wrote:
> On Wed, Apr 08, 2015 at 12:08:27PM -0700, Seth Fowler wrote: > > 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. > > It seems to me *this* is the actual problem that needs solving. > Switching between esr-release-beta-aurora-nightly is *very* common. If > running nightly screws up profiles for older versions, that's a serious > problem imho. > Really? Presumably not every forward DB migration can be reverted without some data loss in theory, and and in my limited practice, handling DB downgrades is pretty damn hard. Is there an expectation that Release -> Nightly -> Release will work? Preserve data? Nick _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
