Release v4.2.8

[jibees]

Preparation on Thursday

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

Testing

• [x] Find build of the release commit and copy it below. https://semaphoreci.com/openfoodfoundation/openfoodnetwork-2/branches/master/builds/3679
• [x] Move this issue to Test Ready and notify testers.
• [x] Test: :warning: link to the build of the release commit https://semaphoreci.com/openfoodfoundation/openfoodnetwork-2/branches/master

Finish on Tuesday

• [x] Update translations unless content has been removed from config/locales/en.yml between this release draft and current master.
  Command line instructions

  git checkout master # same version as the release draft
  git fetch upstream
  git diff upstream/master -- config/locales/en.yml
  tx pull --force # if no changes or only additions in the locale
  git checkout --detach # if we need to commit new translations
  git commit -a -m "Update translations"
  git tag vx.y.z # put the release number in here
  git push upstream vx.y.z
  

• [x] Publish and notify #global-community:

  The next release is ready: https://github.com/openfoodfoundation/openfoodnetwork/releases/latest

• [x] 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
  

• [x] Notify #instance-managers:

  @instance_managers The new release has been deployed.

• [x] Nudge next release manager

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

[RachL]

@openfoodfoundation/core-devs a comment on the release template issue: I never use the link next to the testing checkbox to stage, always https://semaphoreci.com/openfoodfoundation/openfoodnetwork-2/branches/master/builds/3679 am I doing something wrong? Otherwise maybe the template can be updated.

[jibees]

You're right, we need to test that build ie. https://semaphoreci.com/openfoodfoundation/openfoodnetwork-2/branches/master/builds/3679 because it's the build of the commit on which the release is drafted. Not sure to understand what for stand the other link (ie. https://semaphoreci.com/openfoodfoundation/openfoodnetwork-2/branches/master)

[RachL]

yep me neither, I think we can remove it.

Testing done, another one ready to ship! ⛵

https://docs.google.com/document/d/1SJQGDKhylYgYcBzS5awFME7kNkd7ATgadkGVi__i5zQ/edit#

[sigmundpetersen]

Hey guys. I think that the

Find build of the release commit and copy it below.

are instructions for the drafter and that copy it below means copy the link to the step

Test: ⚠️ link to the build of the release commit https://semaphoreci.com/openfoodfoundation/openfoodnetwork-2/branches/master

and not straight below i.e. next line.

The https://semaphoreci.com/openfoodfoundation/openfoodnetwork-2/branches/master link is a template meant to be substituted with the actual build link.

😅

So the output in the description should really be:

• [x] Find build of the release commit and copy it below.
• [x] Move this issue to Test Ready and notify testers.
• [ ] Test: https://semaphoreci.com/openfoodfoundation/openfoodnetwork-2/branches/master/builds/3679

I agree it's a bit confusing and could be improved. I may not have the correct understanding either 🙂

[sigmundpetersen]

Maybe the two steps "Find build" and "Move this issue" could be moved up to the "Preperations" section?

[jibees]

No, I think you're right: I misunderstood the below ;)

If you read at @mkllnk issue, like this one: https://github.com/openfoodfoundation/openfoodnetwork/issues/9471 It's way cleaner !

Thanks @sigmundpetersen will take care the next time! Sorry for the confusion @RachL !

[mkllnk]

I tried to clarify: https://github.com/openfoodfoundation/openfoodnetwork/commit/63d2d69d08e3002bb1d3bde0916207d041375112

This also removes the need to replace text. There's just an empty space now.

[jibees]

I tried to clarify: 63d2d69

This also removes the need to replace text. There's just an empty space now.

Thanks perfect, thanks!