Skip to content

Commit

Permalink
Merge pull request #36 from moodlemobile/relase-notes-45
Browse files Browse the repository at this point in the history
Update release process for app
  • Loading branch information
dpalou authored Nov 5, 2024
2 parents 44c0cc6 + c0863bc commit 39360c8
Showing 1 changed file with 8 additions and 7 deletions.
15 changes: 8 additions & 7 deletions general/development/process-moodleapp/release.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,13 +29,14 @@ tags:
| 1. | Set the right version number for the new Moodle LMS major release in the [authenticated-site.ts](https://github.com/moodlehq/moodleapp/blob/main/src/core/classes/sites/authenticated-site.ts#L63) constant `MOODLE_RELEASES`. | Developer |
| 2. | Launch the internal release github workflow. | Developer |
| 3. | Do some testing with the production builds before sending the application to the stores (overall testing to see that nothing is broken): <ul><li>Correct definitive version name displayed (and commit)</li><li>AOT compiling worked</li><li>Language strings synchronised from [lang.moodle.net](https://lang.moodle.net)</li><li>New language packs added</li></ul> | All the team |
| 4. | Send the applications to the stores for review. | Team Lead |
| 5. | Check TAG/Release have been created in github ([moodlehq/moodleapp](https://github.com/moodlehq/moodleapp/releases)) with the version number. | Developer |
| 6. | Update the `ci` branch in the behat tests plugin ([moodlehq/moodle-local_moodleappbehat](https://github.com/moodlehq/moodle-local_moodleappbehat/)) with the version number. | Developer |
| 7. | Update [upgrade guides](../../app/upgrading). | Developer |
| 8. | Open PR with release documentation updates (from [moodlemobile/devdocs:app-docs](https://github.com/moodlemobile/devdocs/tree/app-docs) to [moodle/devdocs](https://github.com/moodle/devdocs)). | Developer |
| 9. | Mark the issue and the [version](https://tracker.moodle.org/projects/MOBILE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page) as released in the tracker. | Team Lead |
| 10. | Update [release notes](../../app_releases.md). | Team Lead |
| 4. | Launch behat tests (latest branch). | Developer |
| 5. | Send the applications to the stores for review. | Team Lead |
| 6. | Check TAG/Release have been created in github ([moodlehq/moodleapp](https://github.com/moodlehq/moodleapp/releases)) with the version number. | Developer |
| 7. | Update the `ci` branch in the behat tests plugin ([moodlehq/moodle-local_moodleappbehat](https://github.com/moodlehq/moodle-local_moodleappbehat/)) with the latest behat code and features. | Developer |
| 8. | Update [upgrade guides](../../app/upgrading). | Developer |
| 9. | Open PR with release documentation updates (from [moodlemobile/devdocs:app-docs](https://github.com/moodlemobile/devdocs/tree/app-docs) to [moodle/devdocs](https://github.com/moodle/devdocs)). | Developer |
| 10. | Mark the issue and the [version](https://tracker.moodle.org/projects/MOBILE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page) as released in the tracker. | Team Lead |
| 11. | Update [release notes](../../app_releases.md). | Team Lead |

## The following days

Expand Down

0 comments on commit 39360c8

Please sign in to comment.