Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v4.4.43 #12422

Closed
12 tasks done
rioug opened this issue Apr 30, 2024 · 4 comments
Closed
12 tasks done

Release v4.4.43 #12422

rioug opened this issue Apr 30, 2024 · 4 comments
Assignees

Comments

@rioug
Copy link
Collaborator

rioug commented Apr 30, 2024

1. Preparation on Thursday

  • Merge pull requests in the Ready To Go column
  • Include translations: script/release/update_locales
  • Increment version number: git push upstream HEAD:refs/tags/vX.Y.Z
    • Major: if server changes are required (eg. provision with ofn-install)
    • Minor: larger change that is irreversible (eg. migration deleting data)
    • Patch: all others. Shortcut: script/release/tag
  • Draft new release. Look at previous releases for inspiration.
    • Select new release tag
    • Generate release notes and check to ensure all items are arranged in the right category.
  • Notify #instance-managers of user-facing 👀, API ⚠️ and experimental 🚧 changes.

2. Testing

3. 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.

  • Create issue for next release and confirm with next release manager in #core-devs.

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

@rioug rioug self-assigned this Apr 30, 2024
@rioug rioug changed the title Release Release v4.4.42 May 1, 2024
@filipefurtad0 filipefurtad0 self-assigned this May 1, 2024
@filipefurtad0 filipefurtad0 added no-staging-FR A tag which does not trigger deployments, indicating a server is being used and removed no-staging-FR A tag which does not trigger deployments, indicating a server is being used labels May 1, 2024
@filipefurtad0
Copy link
Contributor

Hey @rioug ,
The release is good to go, nothing spotted:
https://docs.google.com/document/d/1TpXM1pdsVzoaoyDv5d-tdgahAkD60CxFsdn0jan7uMw/edit

@mkllnk mkllnk changed the title Release v4.4.42 Release v4.4.43 May 2, 2024
@mkllnk
Copy link
Member

mkllnk commented May 2, 2024

I had an urgent translation update for this release. I should have done that yesterday before it was drafted but I was sick. Anyway, I added a commit and updated the release draft to use the new commit under a new tag name. I think that it doesn't need testing. We used to pull translation updates on Monday before final release in the past but nowadays we don't need to most of the time.

@mkllnk
Copy link
Member

mkllnk commented May 2, 2024

I also deleted the tag named v.

@mkllnk
Copy link
Member

mkllnk commented May 3, 2024

I added another bug fix to the release:

@rioug rioug closed this as completed May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants