Release v4.4 - No masters

[dacook]

Preparation on Thursday

• Merge pull requests in the Ready To Go column
• Include translations: tx pull --force
• Draft new release. Look at previous releases for inspiration.
• Notify #instance-managers of user-facing changes.

Testing

• Find build of the release commit and copy it below.
• Move this issue to Test Ready.
• Notify @testers in #testing.
• Test build: https://semaphoreci.com/openfoodfoundation/openfoodnetwork-2/branches/v4-4-0-master-variants/builds/1

Finish on Tuesday

• Publish and notify #global-community (this is automatically posted with a plugin)
• Deploy the new release to all managed instances.
  Command line instructions

  cd ofn-install
  git pull
  ansible-playbook --limit all-prod --extra-vars "git_version=vx.y.z" playbooks/deploy.yml
  

• Notify #instance-managers:

  @instance_managers The new release has been deployed.

• Nudge next release manager

The full process is described at https://github.com/openfoodfoundation/openfoodnetwork/wiki/Releasing.

[drummer83]

Hi @dacook,

Thanks for preparing the release! I have tested this on all three staging servers and did a bit more than our standard release test, e.g. create variants, run some reports, due to the big change around master variants. Yes - I am nervous. 😉

I couldn't find any problems. Testing notes are here: https://docs.google.com/document/d/1IXhyqPA2KSmTRZ1FK0BChvS426VLJTrMiuMUd0Sk208/edit

There is just one new (handled) Bugsnag when an order cycle closes during checkout. I didn't see any issue in the shopfront around this, but I thought I'd mention it here - just in case.
https://app.bugsnag.com/yaycode/openfoodnetwork-aus/errors/6493c3f52dc0cc0007a36bac?filters[event.since]=30d&filters[error.status]=open&filters[app.release_stage]=staging

Moving to Ready to go! 🤞

[jibees]

Yes - I am nervous. 😉

This is probably a good news here. Thanks for the deep testing @drummer83 !!

[filipefurtad0]

Awesome, great to hear @drummer83,

There is just one new (handled) Bugsnag when an order cycle closes during checkout.

This was introduced a while ago - Jan 31, 2022, to trigger a Bugsnag notification, each time an order cycle closes, when a customer in on the process of completing an order. So, nothing to worry about here - just our monitoring working.

[mkllnk]

Deploy plan draft

UTC dates and times:

Monday early morning ~1:00 am:

• be-prod
• es-prod
• de-prod
• ie-prod
• hu-prod not ready for deploy yet

Tuesday early morning ~1:00 am:

• fr-prod
• uk-prod

Tuesday morning ~6:00 am:

• ca-prod
• us-prod

Tuesday midday ~14:00 UTC:

• au-prod
• nz-prod

[dacook]

Two more instances deployed:

• UK
• FR

I had a quick look around and nothing seems amiss. On UK, I added to cart and proceeded to payment step, and also viewed the bulk products screen successfully. No bugsnag alerts. FR reported a momentary outage

Out of interest, UK's db migration took 64s, and FR 35s.

[dacook]

Deployed on:

• CA (one temporary error affecting a shopper: https://openfoodnetwork.slack.com/archives/CG7NJ966B/p1687847791063419?thread_ts=1687742134.975229&cid=CG7NJ966B)
• US

[dacook]

It looks like the local time was 11pm for Canada, so in hindsight it would have been better to wait a few hours later.

@jibees, the planned time for AU is also 11pm local time, so I suggest we move it later. I think 14:00 UTC is 4pm your time, would that be ok for you?

[jibees]

14:00 UTC is fine for me as well!

[jibees]

I've edited the comment to:

Tuesday midday ~14:00 UTC:

[jibees]

A bit late, starting at 14:45 UTC.

[jibees]

[mkllnk]

Well done, team! 💪