![\"Image](\"https:\/\/devblogs.microsoft.com\/devops\/wp-content\/uploads\/sites\/6\/2024\/12\/new-boards-1.png\")
<\/a><\/p>\n\ud83d\ude80 How we release updates<\/h2>\n
Before diving into the details of rolling out the New Boards Hub, it\u2019s helpful to explain how Azure DevOps releases updates and features to customers. We use a ring-based release process, dividing Azure DevOps customers into six distinct rings.<\/p>\n
The process begins with Ring 0<\/strong>, our canary ring, which is exclusively used by the Azure DevOps engineering team. Ring 1<\/strong> includes early adopter customers who receive new features early and aggressively share feedback to help shape features. Each subsequent ring contains a progressively larger group of customers, ending in Ring 5<\/strong>, which includes the broadest audience.<\/p>\n This ring-based approach ensures that updates are thoroughly tested as they progress through each ring. By the time updates reach Ring 5, they have undergone extensive usage and testing in earlier rings, allowing us to identify and address issues. As a result, problems rarely make it to Rings 4 and 5.<\/p>\n As we enable the New Boards Hub for each new ring, customers often identify edge cases and provide valuable feedback on issues that need to be addressed. To ensure a smooth transition, we allow the New Boards Hub to \u201cbake\u201d for a period of time with each ring. This gives us the opportunity to thoroughly address customer feedback and resolve any issues before moving to the next ring.<\/p>\n While this process is time-consuming, it allows us to be deliberate and minimizes the potential disruption customers might experience if the rollout were more aggressive.<\/p>\n It\u2019s important to emphasize that the old Boards experience is on a path to deprecation, to be fully replaced by the New Boards Hub. The timing of this transition depends on the ring your organization is in.<\/p>\n For customers in Rings 1 and 2, reverting to the old Boards is no longer an option. For those who still have the ability to revert, we encourage you to remain on the New Boards and share your feedback with us<\/a>. Doing so not only ensures your input helps shape the experience but also makes the transition smoother for you and your team.<\/p>\n \ud83d\udd17 Learn more<\/a> about the features exclusive to the New Boards Hub.<\/p>\n Starting in early January 2025, we will make the New Boards Hub the only experience for the next set of customers that reside in Ring 3. At the same time, we will enable the New Boards Hub as the default experience for the remaining 40% of customers that are in Ring 5.<\/p>\n As with previous stages, we will allow a short period for feedback and issue resolution to ensure a smooth transition. However, our goal is to fully convert all customers to the New Boards Hub, removing the option to revert, by April of 2025.<\/p>\n If you find a problem, please don\u2019t turn off the New Boards Hub. Report the issue via Feedback Ticket<\/a> or email me directly<\/a>. We need to know if there is an issue so we can fix it. All feedback is appreciated.<\/p>\n","protected":false},"excerpt":{"rendered":" Although the process may seem slow, we are steadily progressing toward rolling out the New Boards Hub to all customers. Our plan is to deprecate the old Boards experience for all Azure DevOps service users by the end Q1 2025. The rollout is advancing on two fronts. First, we are setting the New Boards Hub […]<\/p>\n","protected":false},"author":921,"featured_media":69896,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[227,224,229,1],"tags":[],"class_list":["post-69894","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agile","category-azure","category-community","category-devops"],"acf":[],"blog_post_summary":" Although the process may seem slow, we are steadily progressing toward rolling out the New Boards Hub to all customers. Our plan is to deprecate the old Boards experience for all Azure DevOps service users by the end Q1 2025. The rollout is advancing on two fronts. First, we are setting the New Boards Hub […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/69894","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/users\/921"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/comments?post=69894"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/posts\/69894\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media\/69896"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/media?parent=69894"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/categories?post=69894"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/devops\/wp-json\/wp\/v2\/tags?post=69894"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\u23f3 Why is the rollout taking so long?<\/h2>\n
\ud83e\udd1a Can I turn New Boards Hub off?<\/h2>\n
\u23ed\ufe0f What\u2019s next?<\/h2>\n
\ud83d\udc1e What happens if I find an issue?<\/h2>\n