Context
VaultSync 1.8.2, 2.0.0, and 2.0.1 created and accepted regular vaults as Send & Receive. The #150 containment
boundary in the 2.0.2 candidate intentionally stops those folders before receive-side work, scanning, watching, and
local indexing.
Release gate
After upgrade, a regular existing vault therefore cannot receive server changes or index and upload new iPhone
edits. New vault creation and share acceptance are also unavailable. There is no supported safe in-app conversion,
and weakening #150 is not acceptable.
Decision required
Choose the 2.0.2 customer and availability strategy, including the impact on existing Cloud Relay subscribers,
before PR #168 engineering resumes.
Refs #150, #167, #168.
Context
VaultSync 1.8.2, 2.0.0, and 2.0.1 created and accepted regular vaults as Send & Receive. The #150 containment
boundary in the 2.0.2 candidate intentionally stops those folders before receive-side work, scanning, watching, and
local indexing.
Release gate
After upgrade, a regular existing vault therefore cannot receive server changes or index and upload new iPhone
edits. New vault creation and share acceptance are also unavailable. There is no supported safe in-app conversion,
and weakening #150 is not acceptable.
Decision required
Choose the 2.0.2 customer and availability strategy, including the impact on existing Cloud Relay subscribers,
before PR #168 engineering resumes.
Refs #150, #167, #168.