Note:

This site is no longer used and is in read-only mode. Instead please go to our new Moodle Developer Resource site.

Moodle App Release Process: Difference between revisions

From MoodleDocs
Juan Leyva (talk | contribs)
Update migration status and path
Tag: Replaced
 
(24 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Two weeks before (Code freeze) ==
{{Template:Migrated|newDocId=/general/development/process-moodleapp/release}}
 
{| class="table table-striped table-bordered"
|-
! style="width:20px" | #
! Task
! style="width:12%" | 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 [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE%20AND%20labels%20%3D%20release_notes 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 [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE%20AND%20resolution%20in%20(Unresolved%2C%20Fixed)%20AND%20labels%20%3D%20qa_test_required%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC qa_test_required]. Remove that label once are added to the document.
| Tester
|-
| 8.
| Freeze Cordova plugins and Javascript libraries versions (node modules) in both the Cordova project and PhoneGap Build (integration branch).
| Developer
|-
| 9.
| '''Start testing'''
| 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 ==
 
{| class="table table-striped table-bordered"
|-
! style="width:20px" | #
! Task
! style="width:12%" | Responsibility
|-
| 1.
| Replace the master config.xml file with the integration one in the moodlemobile-phonegapbuild repository.
| Integration Lead
|-
| 2.
| Fix the version name in integration:src/config.json (remove the -dev) and integrate the [https://github.com/moodlehq/moodlemobile2/compare/master...integration integration branch onto the master one].
| Integration Lead
|-
| 3.
| Do some testing 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
* AOT compiling worked
* Language strings synchronised from lang.moodle.net
| All the team
|-
| 4.
| Send the applications to the stores for review.
| Integration Lead
|-
| 5.
| Update the [https://moodle.org/plugins/view/local_mobile local mobile plugin] short description to indicate which is the latest Moodle Mobile version supported and date.
| Integration Lead
|-
| 6.
| Create a TAG/Release in github ([https://github.com/moodlehq/moodlemobile2/releases moodlehq/moodlemobile2]) with the version number.
| Integration Lead
|-
| 7.
| Mark the issue and the [https://tracker.moodle.org/projects/MOBILE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page version] as released in the tracker.
| Integration Lead
|-
| 8.
| Update release notes [[Moodle_Mobile_Release_Notes]] .
| Integration Lead
|}
 
== The following days ==
 
{| class="table table-striped table-bordered"
|-
! style="width:20px" | #
! Task
! style="width:12%" | 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 [https://tracker.moodle.org/issues/?jql=project%20%3D%20MOBILE%20AND%20labels%20in%20%28docs_required%2C%20dev_docs_required%29 docs_required and dev_docs_required_tags]. Review the [https://docs.moodle.org/en/Moodle_Mobile_features Mobile features wiki documentation].
| All the team
|-
| 4.
| Delete the integration branch and create it again based on master.
| Team Lead
|-
| 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 and desktop/assets/windows/AppXManifest.xml.
| Integration Lead
|-
| 6.
| Bump version numbers in moodlehq/moodlemobile-phonegapbuild:integration/config.xml and push the changes.
| Integration Lead
|-
| 7.
| Unfreeze Cordova plugins and Javascript libraries versions (node modules) in both the Cordova project and PhoneGap Build (integration branch for both).
| Developer
|-
| 8.
| Execute the combine CSS gulp task to generate a new CSS file for the BMA designer.
| Developer
|-
| 9.
| Check that the [https://cloud.docker.com/u/moodlehq/repository/docker/moodlehq/moodlemobile2/general Docker image] for the new version was successfully built.
| Integration Lead
|}
 
[[Category:Processes]]
[[Category:Mobile]]
{{DISPLAYTITLE:Moodle app release process}}

Latest revision as of 15:41, 9 July 2024

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!