Skip to content

Commit 39360c8

Browse files
authored
Merge pull request #36 from moodlemobile/relase-notes-45
Update release process for app
2 parents 44c0cc6 + c0863bc commit 39360c8

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

general/development/process-moodleapp/release.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -29,13 +29,14 @@ tags:
2929
| 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 |
3030
| 2. | Launch the internal release github workflow. | Developer |
3131
| 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 |
32-
| 4. | Send the applications to the stores for review. | Team Lead |
33-
| 5. | Check TAG/Release have been created in github ([moodlehq/moodleapp](https://github.com/moodlehq/moodleapp/releases)) with the version number. | Developer |
34-
| 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 |
35-
| 7. | Update [upgrade guides](../../app/upgrading). | Developer |
36-
| 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 |
37-
| 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 |
38-
| 10. | Update [release notes](../../app_releases.md). | Team Lead |
32+
| 4. | Launch behat tests (latest branch). | Developer |
33+
| 5. | Send the applications to the stores for review. | Team Lead |
34+
| 6. | Check TAG/Release have been created in github ([moodlehq/moodleapp](https://github.com/moodlehq/moodleapp/releases)) with the version number. | Developer |
35+
| 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 |
36+
| 8. | Update [upgrade guides](../../app/upgrading). | Developer |
37+
| 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 |
38+
| 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 |
39+
| 11. | Update [release notes](../../app_releases.md). | Team Lead |
3940

4041
## The following days
4142

0 commit comments

Comments
 (0)