Shipmate

Kerbside

Week 2Builder: Priya6 of 8 resolved

Findings

3 blocking · 2 high · 3 medium
Sort:
blockingdb/policies/bookings.sqlOwner: PriyaStatus: Resolved
blockingsrc/routes/checkout.tsxOwner: PriyaStatus: Resolved
blockingdist/assets/index-4f2a91.jsOwner: YouStatus: Waiting on you
highsrc/server/bookings.tsOwner: PriyaStatus: Resolved
highsrc/server/availability.tsOwner: EscalatedStatus: Handed over
mediumsrc/components/BookingForm.tsxOwner: PriyaStatus: Resolved
mediumsrc/components/TimePicker.tsxOwner: PriyaStatus: Resolved
mediumsrc/routes/admin.tsxOwner: PriyaStatus: Resolved

Sorted by severity, blocking first.

Updates

  1. PriyaMon 12 Oct, 17:40 · day 1

    Audit done. Eight things, three of which I would not launch with: the bookings table is readable by anyone signed in, payments stop at the form, and two keys are in the published app. Starting on the bookings table tomorrow morning.

  2. PriyaWed 14 Oct, 16:05 · day 3Needs something from you

    Bookings are now private to each customer, and failed requests show a message instead of a blank screen. Both are on staging v0.3. The keys need rotating at the provider, which only you can do. I have written the three steps on that item.

  3. PriyaSat 17 Oct, 11:20 · day 6Needs something from you

    Payments work on staging v0.5 in test mode. To take real money I need you to create the payment account in your name and add me with developer access. I have not set anything up on your behalf.

  4. PriyaTue 20 Oct, 15:30 · day 9

    The double-booking issue is bigger than a fix. It needs a proper availability model across several valeters and time zones. I have added a simple lock so the same slot cannot be taken twice in one area, and written a handover for a specialist.

  5. PriyaSun 25 Oct, 10:15 · day 14

    Confirmation emails, the small-phone layout and your bookings page are done on staging v0.8. Launch checklist is 11 of 12. The twelfth is load testing, which I have left on purpose and explained.