Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Upcoming Change: Simplified Release Schedule Format
We are making it easier for customers to understand release timelines. Starting soon, the release schedule page will move from a geo-based table to a simplified format that focuses on version cadence.
What’s Changing?
• Current format: Tables organized by region and station mapping.
• New format: A streamlined table showing:
o Release version
o Early Release Date
o Production Start Date
o Production End Date
Sample New Format Table
Why This Change?
• Simpler Experience: No more complex geo or station mapping—just clear dates.
• Predictable Upgrade Planning: Customers can estimate when they’ll receive a target version by comparing their current build and release cadence (e.g., 4 versions behind ≈ 4 weeks).
• Consistency Across Regions: Removes ambiguity caused by regional differences and station assignments.
• Self-Service Capability: Reduces dependency on support by enabling customers to calculate timelines using a simple rule.
• Future-Proof Design: Scales better as infrastructure evolves (e.g., reducing stations from six to four) without major documentation overhauls.
• Transparency & Trust: Communicates release cadence clearly, avoiding unnecessary complexity and misinterpretation.
How to Interpret the New Table
Find your current version in the table.
Use the start and end dates to estimate when your target version will arrive.
• Example: Refer to sample table for this example. If you are on version 9.2.25101.00190 and want version 9.2.25094.00204, note that each version is roughly one week apart, 190 to 212 will be one week. 212 to 204 will be another week. So, for 204, expect 2 weeks. .
What This Means for You
• No action is required—this is a documentation update.
• To get the current version of your environment, please check your Environment Details page in the Admin Center.