EdX has just released the newest version of the edX platform on edx.org and edX Edge.

This release includes the following updates.

For more information about these and other changes in this release, see the edX Release Notes. You can access the weekly release notes, as well as all of the edX documentation, at docs.edx.org.

  • In courses that offer proctored exams, course teams can now control whether learners in the verified track must use online proctoring to take proctored exams. Previously, verified learners could choose to take a proctored exam as a regular exam without online proctoring, and accept that they would no longer be eligible to receive credit for the course by making this choice. Now, if course teams set the new Allow Opting Out of Proctored Exams option on the Advanced Settings page in Studio to false, verified learners no longer have the option to take proctored exams without proctoring. For more details, see Allowing Verified Learners to Opt Out of Proctored Exams in the Building and Running an edX Course guide.

  • In Insights, the Weekly Student Engagement chart and the Content Engagement Breakdown report now both include discussion participation counts for each week. Learners who added a post, a response, or a comment are included in this count. The “Participated in Discussions Last Week” metric includes users who added a post, response, or comment to any course dicussion topic during the last week, and also provides this value as a percentage of currently enrolled learners. For more information, see the Engagement Activity section in the Using edX Insights guide.

  • This release resolves an issue where report generation tasks that were in progress on the Data Download tab in the instructor dashboard did not display in the Pending Tasks table. The Pending Tasks table now correctly displays tasks that are in progress as well as the status of completed tasks.

  • EdX has updated Django, the web framework that edX uses to develop Studio and the LMS, from version 1.8.15 to version 1.8.16. This update reflects a Django security release and does not result in any user-visible changes. For more information about Django version 1.8.16, see this Django security releases post.