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
(review lang strings, provide the APK file)
(40 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== 2 weeks before ==
== Two weeks before (Code freeze) ==
 
{| class="table table-striped table-bordered"
|-
! style="width:20px" | #
! Task
! style="width:12%" | Responsibility
|-
| 1.
| Request a native English speaker to review the new strings.
| Integration Lead
|}
 
== 4-7 days before (when possible) ==


{| class="table table-striped table-bordered"
{| class="table table-striped table-bordered"
Line 25: Line 12:
|-
|-
| 2.
| 2.
| Update the local_moodlemobileapp plugin with new strings in moodle.org/plugins (only for Moodle version 2.6). Use the moodlemobile-scripts/json-to-string2.php to convert the build lang file to a valid string file. This will allow translators to add the new strings during the days prior to the release.
| Force an update of the [https://moodle.org/plugins/view.php?id=997 local_moodlemobileapp] plugin (as release candidate) with new strings in moodle.org/plugins (only for Moodle version 2.6).  
| Integration Lead
| Dev
|-
|-
| 3.
| 3.
| Announce in the moodletranslation forums the new strings available: https://lang.moodle.org/mod/forum/view.php?id=5
| Ask someone from sites or community team to review the new English strings.  
| Integration Lead
| Community or Sites team
|-
|-
| 4.
| 4.
| 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.
| 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
| Integration Lead
|-
|-
| 5.
| 5.
| Contact the marketing announcing the new release and highlights .
| 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
|}
 
== 3 days before (testing days) ==
 
{| class="table table-striped table-bordered"
|-
! style="width:20px" | #
! Task
! style="width:12%" | Responsibility
|-
| 1.
| Create a new branch with the release tracker issue number for integrating all the version and string changes.
| Integration Lead
|-
| 2.
| Run gulp and then execute detect-string-core-changes.php and auto-translate strings with the script auto-translate2.php, commiting the results
| Integration Lead
|-
| 3.
| Run gupl and update language strings from AMOS using the fetch-langpacks2.sh script, commit the result
| Integration Lead
|-
| 4.
| Bump version numbers in config.xml, www/config.json and in www/errorreport.js (is hardcoded there).
Push all this changes using the release issue number.
Then integrate the changes into the master branch.
| Integration Lead
|-
| 5.
| Switch to the master branch and update from master (git fetch moodlehq; git merge moodlehq/master master)
Execute gulp to build all the files (and bower install if necessary to update javascript libraries)
| Integration Lead
| Integration Lead
|-
|-
| 6.
| 6.
| Copy the code of master (after doing gulp) to the moodlemobile-phonegapbuild repo
| Contact the marketing team announcing the new release and highlights.
| Integration Lead
| Integration Lead
|-
|-
| 7.
| 7.
| Bump version numbers in /config.xml
| 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.
| Integration Lead
| Tester
|-
|-
| 8.
| 8.
| Rebase for iOs and Android (all the commits that apply the specific styles, includes the errorreport.js library etc.. will be applied)
| Freeze Cordova plugins and Javascript libraries versions (node modules) in the integration branch.
| Integration Lead
| Developer
|-
|-
| 9.
| 9.
| Create two different builds (one for ios and another one for android branch) in Phonegap Build using the Development certificate for iOs and not using any certificate for Android
| '''Start testing'''
And '''Start testing'''
| Tester
| All the team
|}
|}


Line 100: Line 54:
| 1.
| 1.
| Backport to local_mobile (all branches) all the new required Web Services by new features.
| 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)
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.
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.
Line 114: Line 68:
! style="width:12%" | Responsibility
! style="width:12%" | Responsibility
|-
|-
| 1.
| 1.  
| Build the app for Android and iOs using the Distribution certificate. Remember to do two different builds (pointing to the ios and android branches).
| Fix the version name in integration/config.xml and integration:src/config.json (remove the -dev).
| Integration Lead
| Integration Lead
|-
|-
| 2.
| 2.
| Send the applications to the stores for review.
| Integrate the [https://github.com/moodlehq/moodleapp/compare/master...integration integration branch onto the master one].  
| Integration Lead
| Integration Lead
|-
|-
| 3.
| 3.
| Update release notes [[Moodle_Mobile_Release_Notes]] with the notes reviewed in the issue.
| 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):
| Integration Lead
* 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.
| 4.
| Create a TAG/Release in github ([https://github.com/moodlehq/moodlemobile2/releases moodlehq/moodlemobile2]) with the version number.
| Send the applications to the stores for review.  
| Integration Lead
| Integration Lead
|-
|-
| 5.
| 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.
| Create a TAG/Release in github ([https://github.com/moodlehq/moodleapp/releases moodlehq/moodleapp]) with the version number.
| Integration Lead
| Integration Lead
|-
|-
Line 139: Line 97:
|-
|-
| 7.
| 7.
| 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).
| Social media announcements (Forum and Twitter).
| All the team & Marketing team  
| All the team & Marketing team  
|-
|-
| 8.
| 2.
| Post in moodle.org/news.
| Post in moodle.org/news.
| Team Lead
| Team Lead
|-
|-
| 9.
| 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 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
| All the team
|-
|-
| 10.
| 4.
| Provide the APK file for including in [https://download.moodle.org/mobile/ Moodle downloads:Moodle mobile].
| 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, 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.
| Integration Lead
| Integration Lead
|-
| 6.
| Unfreeze Cordova plugins and Javascript libraries versions (node modules).
| Developer
|-
| 7.
| Execute the combine CSS gulp task to generate a new CSS file for the BMA designer.
| Developer
|-
| 8.
| Check that the [https://cloud.docker.com/u/moodlehq/repository/docker/moodlehq/moodleapp/general Docker image] for the new version was successfully built.
| Integration Lead
|-
| 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
|}
|}
[[Category:Processes]]
[[Category:Mobile]]
{{DISPLAYTITLE:Moodle app release process}}

Revision as of 11:35, 26 June 2020

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. Freeze Cordova plugins and Javascript libraries versions (node modules) in the integration branch. Developer
9. Start testing Tester

1 day before

# Task 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

# Task Responsibility
1. Fix the version name in integration/config.xml 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, 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. Integration Lead
6. Unfreeze Cordova plugins and Javascript libraries versions (node modules). Developer
7. Execute the combine CSS gulp task to generate a new CSS file for the BMA designer. Developer
8. Check that the Docker image for the new version was successfully built. Integration Lead
9. Update of the local_moodlemobileapp plugin (as final release) in moodle.org/plugins (only for Moodle version 2.6). Dev
Retrieved from "https://docs.moodle.org/dev/index.php?title=Moodle_App_Release_Process&oldid=57662"
Powered by MediaWiki