on 10-13-2022 10:50 AM
Hello everyone! Here are the release notes for our most recent updates to Duo.
You can subscribe to notifications for new release notes by following the process described here. If you have any questions about these changes, please comment below.
New features, enhancements, and other improvements
Duo Central Device Management is Now in General Availability
Duo Passwordless platform authenticators now support multi-device authentication
Verified Duo Push and Risk-based factor selection policies now let administrators set verification code length
Updated certificate issuer name for Azure SCEP certificate profiles in Microsoft Intune Managed Endpoint Device Deployment
CN=Duo Endpoint Validation Issuing CA 2
.New and updated applications
Duo Device Health application stable version 3.1.0 released
Duo Device Health application public beta version 3.0.1 released
Duo Mobile for Android version 4.26.0 released
Duo Mobile for iOS version 4.26.0 released
Where are the release notes for D252? Our Admin Panel shows version 252, but there appear to be no release notes.
Hi @hawley.35 ,
We publish these public notes every other Friday after a D-release completes deployment to commercial customers. So, you can expect the D252 notes post tomorrow.
Would it be possible to get release notes when the deployment starts (or earlier) instead of after it finishes?
Hi @owenhael thank you for posting your question. I think your suggestion is worth exploring. At this time, it’s not possible given our process of developing in biweekly sprints. A fair amount of work goes into orchestrating several engineering and QA teams to organize, clarify, and verify the accuracy of Release Notes before we’re ready to publish here.
Hi Tim, I’m not sure I understand. How do biweekly sprints preclude putting release notes out at the start of the release or beforehand? Duo is a mission-critical application and having release notes in advance so administrators know what to look for in case of issues is pretty standard.
Hi Owen, I’m sorry to be unclear … I mean that our current process of orchestrating info from several teams is what locks me into the current timing of posting Release Notes a day after the release is completed. Historically, this practice was meant to avoid the back-and-forth of Release Notes updates and revisions when specific changes are rolled back when acceptance testing discovers problems in the final deployment.
All that said, I think you make a good suggestion, and I’m already discussing with others at Duo how we can make it happen. Just takes time and coordination of multiple teams.
Thank you Tim, all I can ask for is consideration. Thanks for responding to my questions here.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: