The survey results are in, and you’ve told us you’re looking for an easier way to see what’s changing in Canvas. Our engineering teams are working on an initiative to simplify on their end, but until then, we’re making a change on September 17 to streamline the Community experience.
Fixed bugs have been included in the deploy notes since, well—the creation of the deploy notes. And for the last few years, the “Known Issues” board in the Community has only included notable bugs, which didn’t always align with the bugs posted in the deploy notes.
It’s time to evolve our process for greater clarity, and this time we’re putting our focus into our Known Issues board to give you more timely updates when you need them.
[UPDATE 18 MARCH 2021—The content in this post has been adjusted from user feedback (thank you!) Stay tuned for revisions being implemented in the 2021-04-17 Canvas Release Notes, which will be published on March 22.]
Effective March 22, we are changing how release notes comments are managed to provide a better experience for everyone.
Our teams have several projects still in progress related to our COVID-19 response. These features may continue to be released weekly when available through May 2020. If no features are ready to be released on a given weekend, no Ready Release will take place.
Way back in 2014—which in Canvas time feels like an eon ago—product and engineering devised the idea of a feature option, which was a way to help each Canvas admin manage larger features that may disrupt the workflow if included as part of a regular release cycle. In the Account Settings and Course Settings pages, this new concept was given its own tab where most included features could be managed at any time. Depending on functionality, features may be able to be allowed or turned on at the account, sub-account, course, and user levels.
Last November we posted a proposal for Canvas release changes in 2019. Our proposal intends to improve the quality of Canvas releases, resolve bugs more quickly, and create more predictable releases with a more manageable pace. Community feedback proved highly supportive, and our engineering teams have continued to make progress with necessary adjustments. Thanks for your patience as we’ve been working out the specifics to share with you.
Last week we made a change in the Canvas Community to update all Arc references to Canvas Studio. Some of you have already seen this change. A more official announcement is being unveiled by our marketing team in a few weeks. Although we can't formallysteal their thunder, we can share with you what's coming!
Every day, we come to work with one purpose in mind: we want to help you achieve your goals and find success within the life-changing field that is education. Canvas is the LMS that makes teaching and learning easier. And every day we want to give you our very best, no matter what it takes.
Over the last few years, we’ve been making constant modifications to improve the release notes for Instructure products. Recently some of you may have participated in the Canvas Community health check—a survey that helps the Community team gauge your experiences with the Canvas Community. For better or worse, we use that survey to help us find ways to make your experience with the Canvas Community even better!