A release represents a scheduled event when customer-affecting code is intended to be visible in a specified environment. Canvas release notes maintain a current list of features and other customer-impacting changes that will be included in an upcoming Canvas release.
Features are subject to change based on user feedback and QA testing.
Some features may only be available in the beta environment as indicated in the release notes. Production availability will be announced at a later date based on user feedback.
Some features may be deployed to production before the scheduled release. Such changes are indicated in the release notes for the specified feature.
Canvas engineers may also modify or add additional code to the beta environment after the initial beta deploy. Modifications to the release notes are indicated in the Change Log section at the end of each release notes document.
What information is not in the release notes?
Features that are currently in development or could be in development
Please review the application using the Beta environment for potential customization conflicts along with Canvas Deploys every two weeks
Features in Canvas mobile apps
Visit the Mobile release notes (not all features will apply to mobile apps, and some functionality may be implemented at a later date)
What is the Canvas release schedule?
The release date indicates the date the features will be available in the production environment, unless otherwise noted. Updates are available on the third Saturday of every month.
On the following Monday, all customer-affecting code for the following month will be available in the beta environment. Customers are welcome to experiment in the beta environment at this time, but the environment is still subject to change. Release notes announcing all specified changes will not be published until one week later.
Unlike traditional software, Canvas updates on a regular cadence identified by its release date, not a version number.
How can I try out new features?
Changes described in the release apply to Canvas as accessed through a desktop browser.
All features are available for testing in the beta environment unless otherwise indicated directly in the release notes. Some features may not yet be supported in the beta environment.
Please note that beta environments are refreshed weekly on Saturdays. Any changes made in the beta environment will refresh with the latest data in the production environment. For more information, please see What is the Canvas beta environment?
Some features are available in Canvas as feature options, which may either be enabled by a Canvas admin in Account Settings or by a Canvas Customer Success Manager as indicated in the release notes.
Feature options are features that may change the workflow for common activities in Canvas during an institution's current term and allows Canvas admins to enable the feature based on their preferred timeline. However, after a specified period of time, feature options may become standard features in Canvas. Feature options that will become enforced for all institutions will be indicated in the release notes with adequate advance notice.
How can I enable a feature option?
Feature options can be managed by an institution’s Canvas admin. Feature options can either be turned on for all users or allowed at the sub-account and course levels. Allowed features at the course level can be managed by instructors within each individual course.
Some feature options enable beta features, which may be associated with user groups in the Canvas community.
The term Beta means the feature is available for use in the production environment but is still being tested for usability and accessibility behavior. However, occasionally features may only be available for testing in the beta environment.
Enabling a beta feature may create unintended behavior within a Canvas account.
Note: In the near future, terminology will be adjusted to help better define the intention of a beta release and minimize confusion between the state and the environment.
Beta features are initially included and announced in the release notes. Not all institutions may be comfortable exploring beta features, so an institution may not choose to participate until the feature has been generally announced for all users. Most beta features are incorporated into Canvas as a feature option or an account setting.
What is a beta user group?
Some beta features may use customer feedback to provide additional development to the feature. Once all refinements have been made to the feature, our product teams will determine when it should be made generally available to all users.
These types of beta features employ the use of a Community beta user group, which houses all user documentation, release notes, known bugs, and other resources specific that feature. It also provides beta users a location to ask questions, find answers, and share feedback about the feature.
Participating in a beta feature associated with a user group may come with user advisories. For instance, some features may not be backward compatible, depending on the functionality. Additionally, updates to the feature can be deployed outside the regular Canvas release schedule.
Once the feature is no longer in a beta state and is ready for the production environment, the user group will be discontinued, and all specific resources for that feature will be transitioned into the existing resources for all Canvas users.