Moodle Mobile release process
Two weeks before (Code freeze)
|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.|| Bump version numbers in config.xml, www/config.json, package.json and desktop/assets/windows/AppXManifest.xml.
Push all this changes using the release issue number and integrate them into the integration branch.
|9.||Bump version numbers in moodlehq/moodlemobile-phonegapbuild:integration/config.xml and push the changes.||Integration Lead|
1 day before
|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.
The release day
|1.||Replace the master config.xml file with the integration one in the moodlemobile-phonegapbuild repository.||Integration Lead|
|2.||Integrate the 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)||All the team|
|4.||Send the applications to the stores for review.||Integration Lead|
|5.||Update release notes Moodle_Mobile_Release_Notes .||Integration Lead|
|6.||Create a TAG/Release in github (moodlehq/moodlemobile2) with the version number.||Integration Lead|
|7.||Update the local mobile plugin short description to indicate which is the latest Moodle Mobile version supported and date.||Integration Lead|
|8.||Mark the issue and the version as released in the tracker.||Integration Lead|
|9.||Social media announcements (Forum and Twitter).||All the team & Marketing team|
|10.||Post in moodle.org/news.||Team Lead|
|11.||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|