Release process: Difference between revisions
From MoodleDocs
(Archive old versions in the tracker.) |
(Adding David as Moodle Docs maintainer) |
||
Line 15: | Line 15: | ||
|- | |- | ||
| <span id="amos">AMOS Maintainer</span> | | <span id="amos">AMOS Maintainer</span> | ||
| [https://moodle.org/user/view.php?id=1601&course=5 David Mudrák] | |||
|- | |||
| <span id="docs">Moodle Docs Maintainer</span> | |||
| [https://moodle.org/user/view.php?id=1601&course=5 David Mudrák] | | [https://moodle.org/user/view.php?id=1601&course=5 David Mudrák] | ||
|- | |- | ||
Line 24: | Line 27: | ||
|} | |} | ||
Updated 18 June 2013. | Updated 18 June 2013. | ||
==6 weeks prior== | ==6 weeks prior== |
Revision as of 09:22, 1 July 2013
Roles
Role | Person responsible |
---|---|
Lead Developer | Martin Dougiamas |
Integration Lead | Eloy Lafuente |
Community Manager | Helen Foster |
AMOS Maintainer | David Mudrák |
Moodle Docs Maintainer | David Mudrák |
Plugins Directory Maintainer | Aparup Banerjee |
Development Manager | Michael de Raadt |
Updated 18 June 2013.
6 weeks prior
# | Major | Minor | Task | Responsibility |
---|---|---|---|---|
1. | ✓ | Create the next "X.Y+1" (next dev) version in the Tracker (MDL and CONTRIB), so people can move delayed stuff to next major release if needed. | Integration Lead | |
2. | ✓ | Freeze stable development and post in the General developer forum to inform everyone of the freeze. (example) | Development Manager |
4 weeks prior
# | Major | Minor | Task | Responsibility |
---|---|---|---|---|
1. | ✓ | Update the New features document. | Lead Developer | |
2. | ✓ | Start working on the release notes (template) and upgrading notes of the upcoming version . | Development Manager | |
3. | ✓ | Release normal weeklies but with these changes in the master branch:
|
Integration Lead | |
4. | ✓ | (Optionally) Announce Beta release in forums (ideally once packages are available). | Integration Lead | |
5. | ✓ | Start QA. | Community Manager | |
6. | ✓ | Review documentation for all issues with labels "docs_required", "dev_docs_required" and "qa_test_required", removing this label when relevant docs are updated. | Community Manager | |
7. | ✓ | During the QA weeks integration becomes continuous; release STABLE weeklies normally but master release as often as possible (or on demand). | Integration Lead | |
8. | ✓ | At some points produce release candidates (Z = 1, 2, 3..), which are normal builds with:
|
Integration Lead | |
9. | ✓ | Add a new version in the Plugins Directory with the beta version build number and the anticipated release version build number (https://moodle.org/plugins/admin/softwareversions.php). | Plugins Directory Maintainer |
1 week prior
# | Major | Minor | Task | Responsibility |
---|---|---|---|---|
1. | ✓ | Clone as many filters as needed in the Tracker, modifying them to point to the new, upcoming, branch (keeping same perms, title...). | Integration Lead | |
2. | ✓ | ✓ | Create new minor version X.Y.Z in the Tracker (MDL and CONTRIB). Archive any version > 6 months old. | Integration Lead |
3. | ✓ | Clone MDL-39434 and bump all versions, requires and dependencies along all plugins in codebase to current date. | Integration Lead | |
4. | ✓ | ✓ | Post a "Heads-up" message on the Partners forum and General Developer forum | Development Manager |
5. | ✓ | ✓ | Merge fixes from en_fix pack and then integrate them. | AMOS Maintainer |
6. | ✓ | In https://github.com/moodlehq/moodle-behat-extension project:
|
Integration Lead | |
7. | ✓ | ✓ | Identify security issues that need to be integrated using the security_held label.
|
Integration Lead |
8. | ✓ | ✓ | Collect security issues into a clone of MDL-39530 to prepare for release of Security Advisories.
|
Development Manager |
9. | ✓ | ✓ | Review and complete the release notes for the upcoming minor versions.
|
Development Manager |
Day of release
Packaging
# | Major | Minor | Task | Responsibility |
---|---|---|---|---|
1. | ✓ | ✓ | Make sure there are no real blockers introduced in the last weekly (install / upgrade ...) | Integration Lead |
2. | ✓ | ✓ | Verify all unit tests and integration tests have passed. | Integration Lead |
3. | ✓ | Verify QA tests have passed. | Integration Lead | |
4. | ✓ | ✓ | Run the mdlrelease process, with the special steps for a Major release.
|
Integration Lead |
5. | ✓ | ✓ | Wait for the automated moodle-package to finish building for all versions. Verify the process has ended successfuly (email). | Integration Lead |
6. | ✓ | ✓ | On the download server:
|
Integration Lead |
7. | ✓ | ✓ | In the Tracker...
|
Integration Lead |
8. | ✓ | Create the new "Pull X.Y Branch" and "Pull X.Y Diff URL" custom fields and spread them to all the screens needing them (copy from previous ones). Reindex Tracker. Order them properly on each screen. Hide from all screens the custom fields belonging to 100% unsupported branches. | Integration Lead | |
9. | ✓ | ✓ | Add/update the release date, build number and link on the Releases page and date in new version pages. | Integration Lead |
10. | ✓ | ✓ | Post a "git repos updated & tagged" message on the Partner forum | Integration Lead |
Release
# | Major | Minor | Task | Responsibility |
---|---|---|---|---|
1. | ✓ | ✓ | The execution of "moodle-package-extract-and-postprocess X" script may be needed if the releases *are not going to be published on Monday* but another weekday (X is the weekday, (1-7) starting in Monday). | Integration Lead |
2. | ✓ | ✓ | Replace the download/index.php page with its updated counterpart. | Integration Lead |
3. | ✓ | ✓ | Replace the download/windows/index.php page with its updated counterpart. | Integration Lead |
4. | ✓ | ✓ | Notify all registered sys admins, including security notes with CVE identifiers. | Development Manager |
5. | ✓ | Post about the Major release on the moodle.org News forum | Lead Developer | |
6. | ✓ | ✓ | Post about minor releases on the moodle.org News forum | Development Manager |
7. | ✓ | AMOS needs new "X.Y+1dev" branch to be created, to have master changes performed there. | AMOS Maintainer | |
8. | ✓ | Clone MDL-39753 and MDL-39754, to be resolved ASAP. | Integration Lead | |
9. | ✓ | Force update of moodle.org/dev/ | Integration Lead | |
10. | ✓ | Update Moodledocs default redirect and add version link to https://docs.moodle.org/overview/ | Integration Lead | |
11. | ✓ |
|
Development Manager |
1 week after
# | Major | Minor | Task | Responsibility |
---|---|---|---|---|
1. | ✓ | ✓ | Publish the X.Y+ packages for download.moodle.org (should be automatic once weeklies are packaged). | Integration Lead |
2. | ✓ | ✓ | Update the version.php in git to be X.Y.Z+ during the next weekly integration process | Integration Lead |
3. | ✓ | ✓ | Create a new release notes page for the next minor versions (using the release notes template.) | Development Manager |
4. | ✓ | ✓ | Add all security advisories to Security news and release notes with links to security advisories | Development Manager |
5. | ✓ | ✓ | Send a plain text email to the OSS mailing list: oss-security@lists.openwall.com. An appropriate message when sending the issues is...
...followed by the security notes. |
Development Manager |
1 month after
# | Major | Minor | Task | Responsibility |
---|---|---|---|---|
1. | ✓ | Publish the X.(Y+1)dev packages for download.moodle.org | Integration Lead |
See also
- Major release process (deprecated)
- Release process (deprecated)
- Deprecation process (not deprecated)