Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Moodle App Release Process: Difference between revisions

From MoodleDocs
(Update migration status and path)
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Template:Migrated|newDocId=/general/app/development/release-process}}
== Two weeks before (Code freeze) ==
== Two weeks before (Code freeze) ==
{| class="table table-striped table-bordered"
{| class="table table-striped table-bordered"
|-
|-
Line 47: Line 47:
| Tester
| Tester
|}
|}
== 1 day before ==
{| class="table table-striped table-bordered"
|-
! style="width:20px" | #
! Task
! style="width:12%" | Responsibility
|-
| 1.
| Backport to local_mobile (all branches) all the new required Web Services by new features.
Check if existing Web Services should be added to the local_mobile service (because they were added to the Mobile app service).
Once all the Web Services are backported and tested, publish a new version in the plugins database (via TAGS) so admin can updates their sites.
| Integration Lead
|}
== The release day ==
== The release day ==
{| class="table table-striped table-bordered"
{| class="table table-striped table-bordered"
|-
|-
Line 73: Line 55:
|-
|-
| 1.  
| 1.  
| Fix the version name in integration/config.xml and integration:src/config.json (remove the -dev).
| Fix the version name in integration/config.xml, integration/package.json and integration:src/config.json (remove the -dev).
| Integration Lead
| Integration Lead
|-
|-
Line 104: Line 86:
| Integration Lead
| Integration Lead
|}
|}
== The following days ==
== The following days ==
{| class="table table-striped table-bordered"
{| class="table table-striped table-bordered"
|-
|-
Line 130: Line 110:
|-
|-
| 5.
| 5.
| Bump version numbers in the following files in the integration branch: config.xml, src/config.json (appending a -dev to the versionname field to indicate that is a development version), package.json (including mac->bundleVersion) and desktop/assets/windows/AppXManifest.xml.
| Bump version numbers in the following files in the integration branch: config.xml (version), package.json (version), moodle.config.json (versionname) appending a -dev to indicate that is a development version).
| Integration Lead
| Integration Lead
|-
|-
Line 138: Line 118:
|-
|-
| 7.
| 7.
| Execute the combine CSS gulp task to generate a new CSS file for the BMA designer.
| Check that the [https://cloud.docker.com/u/moodlehq/repository/docker/moodlehq/moodleapp/general Docker image] for the new version was successfully built.
| Developer
| Integration Lead
|-
|-
| 8.
| 8.
| Check that the [https://cloud.docker.com/u/moodlehq/repository/docker/moodlehq/moodleapp/general Docker image] for the new version was successfully built.
| Update of the [https://moodle.org/plugins/view.php?id=997 local_moodlemobileapp] plugin (as final release) in moodle.org/plugins.
| Integration Lead
| Developer
|-
| 9.
| Update of the [https://moodle.org/plugins/view.php?id=997 local_moodlemobileapp] plugin (as final release) in moodle.org/plugins (only for Moodle version 2.6).  
| Dev
|}
|}


== See also ==
== See also ==
* [[Moodle App Release Notes]]
* [[Moodle App Release Notes]]
[[Category:Processes]]
[[Category:Processes]]
[[Category:Mobile]]
[[Category:Mobile]]
{{DISPLAYTITLE:Moodle app release process}}
{{DISPLAYTITLE:Moodle app release process}}

Latest revision as of 13:03, 14 July 2022

Important:

This content of this page has been updated and migrated to the new Moodle Developer Resources. The information contained on the page should no longer be seen up-to-date.

Why not view this page on the new site and help us to migrate more content to the new site!

Two weeks before (Code freeze)

# Task Responsibility
1. Create an issue in the tracker for the release, like: MOBILE-1248 Integration Lead
2. Force an update of the local_moodlemobileapp plugin (as release candidate) with new strings in moodle.org/plugins (only for Moodle version 2.6). Dev
3. Ask someone from sites or community team to review the new English strings. Community or Sites team
4. Announce in the moodletranslation forums the new strings available: https://lang.moodle.org/mod/forum/view.php?id=5. This will allow translators to add the new strings during the days prior to the release. Integration Lead
5. Add the release notes in the release issue created (search for the release_notes tag). Ask someone from the documentation team or Martin to review the release notes. Integration Lead
6. Contact the marketing team announcing the new release and highlights. Integration Lead
7. Add new QA tests to the “Testing cases” document. New QA tests should be labeled with qa_test_required. Remove that label once are added to the document. Tester
8. Run npm audit to ensure all the dependencies are OK. Developer
9. Freeze Cordova plugins and Javascript libraries versions (node modules) in the integration branch. Developer
10. Start testing Tester

The release day

# Task Responsibility
1. Fix the version name in integration/config.xml, integration/package.json and integration:src/config.json (remove the -dev). Integration Lead
2. Integrate the integration branch onto the master one. Integration Lead
3. Do some testing with the production builds before sending the application to the stores (overall testing to see that nothing is broken because of the branch merge done in step 2):
  • Correct definitive version name displayed (and commit)
  • AOT compiling worked
  • Language strings synchronised from lang.moodle.net
  • New language packs added
 All the team
4. Send the applications to the stores for review. Integration Lead
5. Create a TAG/Release in github (moodlehq/moodleapp) with the version number. Integration Lead
6. Mark the issue and the version as released in the tracker. Integration Lead
7. Update release notes Moodle_Mobile_Release_Notes . Integration Lead

The following days

# Task Responsibility
1. Social media announcements (Forum and Twitter). All the team & Marketing team
2. Post in moodle.org/news. Team Lead
3. Review the users and developers documentation (check that everything is in order). Review the docs_required and dev_docs_required_tags. Review the Mobile features wiki documentation. All the team
4. Delete the integration and desktop branches and create it again based on master. Team Lead
5. Bump version numbers in the following files in the integration branch: config.xml (version), package.json (version), moodle.config.json (versionname) appending a -dev to indicate that is a development version). Integration Lead
6. Unfreeze Cordova plugins and Javascript libraries versions (node modules). Developer
7. Check that the Docker image for the new version was successfully built. Integration Lead
8. Update of the local_moodlemobileapp plugin (as final release) in moodle.org/plugins. Developer

See also

Retrieved from "https://docs.moodle.org/dev/index.php?title=Moodle_App_Release_Process&oldid=63544"
Powered by MediaWiki