Skip to end of banner
Go to start of banner

Release 11.x Series

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

The 11.x series began with the release of the Application Pathways page, which replaces the Learning Plan List page as the organizing hub of a Practitioner’s credentialing journey.

This series also saw the introduction of the “Long Term Support” / “Long Term Stable” branch.

Overview

For release notes, choose a branch:

Historically, we’ve released new versions of LearningBuilder (e.g. 10.1.x, 10.2.x) every six to eight weeks.

This made things difficult for our Implementation Analysts to manage their client’s annual upgrades because each upgrade would be planned for the latest available release. Thus, each upgrade that an analyst performed would potentially get a new version, making it difficult to create reusable upgrade plans.

The long-term support model addresses this by creating two divergent lines of LearningBuilder:

  • The LTS release (11.0.x for now) will be updated regularly to contain defect fixes, stability improvements, and low-risk enhancements.

  • The innovation line (11.1.x, 11.2.x, etc) will contain more significant changes, new features, and anything that doesn’t clear the “low risk” bar for the LTS version.

When a client is upgraded, unless they specifically need new functionality in the innovation line, they will be upgraded to the latest LTS version.

At some point in the future, the innovation line will become the “new LTS version” (e.g. 12.0.0) and the process will start over.

Term

Meaning

Long Term Support (LTS) release

This is the “designated release” for a given period of time.

Every client that gets upgraded during that period of time, and is NOT funding any innovation, gets upgraded to the most recent patch version of the LTS release.

A LTS release number always has a zero as the middle digit. (e.g. 11.0.0)

Innovation release

Major new functionality is released as “innovation releases” These releases are usually fully backwards-compatible, but may require client-specific UAT.

An innovation release number number has a non-zero digit in the middle. (e.g. 11.1.0)

Patch release

A patch release contains defect fixes and low-risk, backwards-compatible enhancements. Typically, deploying a patch release (to the same major version) does not require client-specific UAT.

A patch release has a non-zero as its final digit. (e.g. 11.1.1)

  • No labels