Handing over the sharing work

Before this: three things are verified, three are only claimed, and you start with the claims.

Sharing lives in five places. Two are done and checked. The other three are built, but each carries one claim that nobody has checked.

• Sync serverShare, accept and remove are deployed. The sharing flag is off in production.
• Web appThe share and accept screens are done, behind the same flag.
• Android appDone. A store email says approved, but nobody has checked the console.
• iPhone appBugs fixed and the build is in review. It works on iOS 18 and is untested on iOS 16.
• Invite emailsThey reach Gmail and Outlook. iCloud is untested.

Take from this: everything is built. What is left is checking, switching on and watching.

server/sharing/        share, accept and remove, and the flag check
server/mail/invite.ts  the invite email
web/src/share/         share and accept screens
android/app/share/     share screen and accept link
ios/Share/             share screen and accept link

Remember: everything is built, and what is left is checking, switching on and watching.

Before this: everything is built, and what is left is checking, switching on and watching.

Both builds are with the stores, and review usually takes one to three days. Nothing you do speeds it up. After that, one switch is left to flip.

1. ReviewiPhone is in review. Android may be done.
2. ApprovedYou confirm it in both consoles.
3. Flag onYou switch sharing on, Thursday 29 October.
4. Day oneYou watch errors and invite emails.

Take from this: nothing ships until both stores approve, and the flag is the last switch anyone touches.

npm run flag -- sharing on     # switch sharing on in production
npm run flag -- sharing off    # the way back

Remember: nothing ships until both stores approve, and the sharing flag is the last switch.

Before this: nothing ships until both stores approve, and the flag is the last switch.

I did not re-run these three. Each is quick, and a wrong one would surface on release day, when it costs the most.

Take from this: the checks take 27 minutes together, and the slowest needs an old phone. Mara has one.

npm test -- sharing        # repo root, main at a41c9e2
  server   38 passed
  web       9 passed
  android  14 passed
  iphone   14 passed

Remember: three claims are unchecked, and all three take under half an hour.

Before this: three claims are unchecked, and all three take under half an hour.

1. Get access on Monday 26 October. Ask Mara to add you to both store consoles and the server dashboard.
2. Run the sharing tests. One command from the repo root. Expect 75 passes and no failures.
3. Check the three claims. The console, an iCloud invite and an iPhone with iOS 16.
4. Confirm both stores approve. Wait if either still says "In review".
5. Switch sharing on at release. Thursday 29 October, only after step 4 and after Mara says go.
6. Watch the first day. Check accept errors and invite emails every two hours.

Take from this: the first three steps are checks and cost nothing. The flag only moves in step 5.

Remember: get access, run the tests, check the three claims, and only then switch sharing on.

Before this: you check, then switch sharing on, then watch.

I am away from 26 October to 6 November and will not read messages. Mara is your contact for everything.

• Ask Mara before a production migration. Since the 13 October incident each one runs by hand, once.
• Ask Mara before resubmitting a build. A resubmission restarts the review clock.
• When in doubt, switch the flag off. It hides the feature and keeps every shared notebook.

Take from this: your work is the sharing code and release day. Two of the three rules send you to Mara first.

Remember: you own the sharing work, Mara owns what ships, and two rules say to ask her first.