4.2 version skip for Open LMS EDU and WORK - FAQ

After careful consideration and discussions with our product development teams, we've made some adjustments to our product roadmap. Instead of integrating Moodle version 4.2, we're focusing on internal development efforts and addressing technical aspects to ensure a seamless experience for our customers.

Key Highlights:

• A more robust roadmap guiding the evolution of the EDU and WORK platforms.

• Redesign and enhancement of core patches of PLD to elevate performance and reliability for both EDU and WORK users.

• Unification of the Open LMS Report Builder reporting tool across WORK and EDU for more streamlined and consistent reporting capabilities.

• Catalog user experience improvements spanning across WORK and EDU ensuring an intuitive and efficient experience.

• An array of enhancements to WORK's programs, multitenancy, user development plans, certifications, and notification framework, all aimed at providing a more tailored and effective experience.

• Improvements to EDU's SNAP, conduit, PLD, and theme accessibility, enhancing the overall usability and inclusivity of the platform.

• Introduction of growth experiments and adoption initiatives, incorporating in-app feature description and data analytics through Appcues for both EDU and WORK features.

We are confident that these enhancements will contribute significantly to our customer's learning and work environments, supporting their goals and objectives in meaningful ways.

What is the main focus of the project?

The project's core focus is on bypassing the review and integration of Moodle version 4.2, with the aim of directing efforts towards internal development initiatives and addressing technical debt. This shift enables the fulfillment of roadmap commitments and effective management of technical prerequisites for maintaining the EDU and WORK platforms.

What is the proposed strategy for code integration?

The proposed strategy involves skipping the code integration process for Moodle 4.2 and proceeding directly to merging the code for Moodle 4.3. This strategy would apply to our EDU and WORK products.

Who is the targeted audience of this strategy?

The decision to skip merging the 4.2 Moodle version applies to EDU SaaS clients and WORK clients. Managed Hosting and Enterprise clients will follow their standard upgrade procedures, though we are recommending our MH clients stay in 4.1 and skip the 4.2 upgrade.

How will the upgrade affect Open LMS EDU clients?

By skipping the code integration for version 4.2, Open LMS EDU clients will continue to operate using the 4.1 Moodle underlying version code. Scheduled maintenance pack releases are planned throughout the year, with the EDU platform being upgraded to Open LMS EDU 4.1 MP3 in December.

What can be expected in the maintenance pack releases for EDU clients?

The maintenance pack releases for EDU clients will encompass retaining the Moodle 4.1.X series for both production and sandbox sites. Additionally, clients will experience regularly scheduled maintenance pack upgrades within this timeframe, which include resolution of security issues, bug rectification, plugin upgrades, augmentation of platform and plugin functionality, and introduction of new features.

When is the major upgrade of EDU to the Moodle version 4.3 scheduled?

The major upgrade to EDU version 4.3 is planned for July 2024.

How will the upgrade impact Open LMS WORK clients?

Similar to the EDU platform, bypassing the 4.2 code integration will maintain Open LMS WORK clients on the 4.1 Moodle version code. Minor releases are planned for the rest of 2023 and the start of 2024, with an upgrade to Moodle version 4.3 in April 2024.

What will be included in the minor upgrades for WORK clients?

Minor upgrades for WORK clients will involve both production and sandbox sites retaining the Moodle 4.1.X series. Regularly scheduled minor upgrades encompass resolution of security issues, bug rectification, plugin upgrades, augmentation of platform and plugin functionality, and introduction of new features.

What advantages will the upgrade strategy offer?

The advantages include a more robust roadmap for both EDU and WORK, PLD redesign and rectification of underlying core patches, unification of the Open LMS Report Builder tool, catalog UX improvements, enhanced program features, and improvements to accessibility and notifications.

What initiatives will be taken to address technical debt and other developmental requirements?

The strategy involves upgrading products and plugins to PHP 8.1-supported versions, eliminating core patches from Open LMS plugins, enhancing security, upgrading community and vendor plugins, discontinuing unused plugins, and ensuring compatibility with Moodle versions 4.2 and 4.3 for Open LMS maintained plugins that are required for MH, Enterprise, and Community clients.

Are there any risks associated with this strategy?

Risks include the potential existence of clients seeking to upgrade to Moodle version 4.2 for its new features.

Additionally, as we remain on the underlying Moodle 4.1 version, while community, vendor, and third-party plugins advance to versions 4.2 or 4.3, we'll explore integrating their 4.1-compatible versions with the latest enhancements. However, there's a chance that the latest plugin version might solely be compatible with Moodle 4.2 and higher, necessitating us to wait until the Open LMS 4.3 upgrade before implementation.

Concerns also exist about maintaining Open LMS plugins for version 4.2 among different client groups. Rest assured, we are developing a new process to support these plugins in versions 4.2 and 4.3, with priority given to target audiences ahead of the EDU and WORK scheduled releases.

What are the restrictions for EDU and WORK clients?

EDU and WORK clients are not provided the option to upgrade to the 4.2 version. Instead, they will continue on version 4.1 and receive minor releases until transitioning to version 4.3.