Allow separate weave and storage versions

RESOLVED FIXED in 0.5

Status

()

RESOLVED FIXED
10 years ago
3 months ago

People

(Reporter: Mardak, Assigned: Mardak)

Tracking

unspecified
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

10 years ago
We set both versions to whatever the weave version is. This can cause unnecessary server wipes on updates that don't actually change record formats.
(Assignee)

Comment 1

10 years ago
http://hg.mozilla.org/labs/weave/rev/fb1fa1f09a67
Update the substitution names to separately replace the storage version with the new storage version Makefile variable.
Assignee: nobody → edilee
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → 0.5
(Assignee)

Comment 2

10 years ago
thunder: Should we bump storage_version to 0.5pre2 because bug 479189 introduces a new record type.. BookmarkQuery for place: queries. Right now they get synced as Bookmark, so a wipe is needed to make sure they get uploaded with the right type.

But then again how many people have smart tags folders?
(In reply to comment #2)
> thunder: Should we bump storage_version to 0.5pre2 because bug 479189
> introduces a new record type.. BookmarkQuery for place: queries. Right now they
> get synced as Bookmark, so a wipe is needed to make sure they get uploaded with
> the right type.
> 
> But then again how many people have smart tags folders?

The local metadata wipe should take care of fixing the broken records.  So long as we can read the 0.5pre1 server format, we should not bump the min storage version.
Component: Firefox Sync: Build → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.