Release Timeline From early versions to the modern
EM
Published · 18 slides · 0 views
1 / 1
Description
Release Timeline From early versions to the modern family release model (2011-2026) Based on the ServiceNow Community article ServiceNow versions Release and timeline visuals Why this article matters A community-built reference that
Related Topics
Share
Embed code
Download this presentation From Below
"Release Timeline From early versions to the modern" is the property of its rightful owner. Permission is granted to download and print the materials on this website for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Presentation Transcript
01
Release Timeline From early versions to the modern family release model (2011-2026) Based on the ServiceNow Community article "ServiceNow versions / Release" and timeline visuals<br>
02
Why this article matters A community-built reference that people return to when planning upgrades, certifications and timelines. Community knowledge The article consolidates family names, key dates, end-of-life notes, exam windows, and community corrections into one living reference. Upgrade planning Release names are not trivia: they anchor upgrade programs, N-1 support conversations, testing windows, and certification deadlines. Timeline storytelling The visual timeline helps non-technical audiences understand the rhythm of ServiceNow releases. From monthly/seasonal naming to city-based family releases.
Two major family releases per year became the common pattern.
After Zurich, the article notes a shift toward country-based names such as Australia, Brazil, Canada and Denmark. ServiceNow Release Timeline | Community article synthesis<br>
Two major family releases per year became the common pattern.
After Zurich, the article notes a shift toward country-based names such as Australia, Brazil, Canada and Denmark. ServiceNow Release Timeline | Community article synthesis<br>
03
Evolution of ServiceNow release naming The naming pattern evolved over time and became part of the platform culture. 2004-2011
Early era GlideSoft, calendar months and seasonal names such as Summer, Winter, Spring and Fall. 2011-2025
City era Alphabetical city-style family names: Aspen, Berlin, Calgary... through Zurich. 2026+
Country era The article tracks Australia and Brazil, with later mentions for Canada and Denmark. ServiceNow Release Timeline | Community article synthesis<br>
Early era GlideSoft, calendar months and seasonal names such as Summer, Winter, Spring and Fall. 2011-2025
City era Alphabetical city-style family names: Aspen, Berlin, Calgary... through Zurich. 2026+
Country era The article tracks Australia and Brazil, with later mentions for Canada and Denmark. ServiceNow Release Timeline | Community article synthesis<br>
04
The city-release timeline at a glance A simplified overview of the main family names most teams reference today. London - Madrid - New York established the 2018-2019 period.
Orlando and Paris carried 2020; Quebec and Rome carried 2021.
San Diego and Tokyo represented 2022; Utah and Vancouver represented 2023.
Washington and Xanadu represented 2024; Yokohama and Zurich represented 2025. ServiceNow Release Timeline | Community article synthesis<br>
Orlando and Paris carried 2020; Quebec and Rome carried 2021.
San Diego and Tokyo represented 2022; Utah and Vancouver represented 2023.
Washington and Xanadu represented 2024; Yokohama and Zurich represented 2025. ServiceNow Release Timeline | Community article synthesis<br>
05
Modern release cadence The article repeatedly points to a two-release-per-year rhythm, typically around Q1/Q2 and Q3/Q4. Planning pattern Organizations often plan around a spring and fall family release cycle, then map upgrade readiness, testing, and change windows. N and N-1 support mindset Community discussion highlights the need to remain on currently supported release families, typically the current and immediate previous family. EOL moves with GA The article includes guidance that EOL timing is tied to the GA of newer families and later community notes reference GA + 60 days. ServiceNow Release Timeline | Community article synthesis<br>
06
Release Testing Preview and Early Availability RTP and EA are the levers that let customers test before general availability. Release Testing Preview (RTP) Begins before GA and gives customers an opportunity to upgrade sub-production environments to pre-release builds. Early Availability (EA) Offers a production-ready version for upgrade before market launch, giving customers and partners time to test and prepare. Who should participate? Teams that want early testing, extra upgrade time, prompt feedback loops, and early awareness of upcoming features. Register Self-nominate via Now Support RTP Sub-production testing EA Production-ready access GA Market launch ServiceNow Release Timeline | Community article synthesis<br>
07
Certification and exam windows Release changes have operational impact beyond platform upgrades. The article tracks blackout periods, last dates to test on a prior release, and first dates to complete exams on the next release.
Examples in the article include Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, Washington and Zurich exam-window notes.
For Zurich, the article notes a Delta exam window opening in January 2026 and closing in April 2026. Message for stakeholders Upgrade planning should include platform owners, app teams, integration owners, and certification holders - not only administrators. ServiceNow Release Timeline | Community article synthesis<br>
Examples in the article include Quebec, Rome, San Diego, Tokyo, Utah, Vancouver, Washington and Zurich exam-window notes.
For Zurich, the article notes a Delta exam window opening in January 2026 and closing in April 2026. Message for stakeholders Upgrade planning should include platform owners, app teams, integration owners, and certification holders - not only administrators. ServiceNow Release Timeline | Community article synthesis<br>
08
Support lifecycle and End-of-Life The article emphasizes staying current to access features, security updates and supported upgrade paths. Supported families Community discussion points to a support policy focused on current and immediately previous release families. Unsupported releases If an instance falls behind, ServiceNow can schedule upgrades to bring the instance to a supported family. GA + 60 days Recent community comments in the article discuss EOL timing as GA + 60 days for N-1 transitions. Practical takeaway: do not treat release names as labels only. They drive risk management, compliance, testing and change governance.
Upgrade decisions should be tied to business calendars and integration validation plans. ServiceNow Release Timeline | Community article synthesis<br>
Upgrade decisions should be tied to business calendars and integration validation plans. ServiceNow Release Timeline | Community article synthesis<br>
09
Release families, patches, security patches and hotfixes A useful distinction for explaining what changed and why an upgrade is required. Family A complete solution release with new capabilities plus fixes. Patch An upgrade within a family; no new family features. Security patch A patch produced to address security issues. Hotfix A small, targeted fix or urgent correction inside a family. Example language A name such as Xanadu refers to a family release; Patch 9, Security Patch 9a, and HF1 describe later maintenance layers within that family. ServiceNow Release Timeline | Community article synthesis<br>
10
Visual release roadmap Use visuals to turn a long reference article into a story executives can understand quickly. Timeline What changed and when. Cadence How often teams must act. Impact Why upgrades matter. ServiceNow Release Timeline | Community article synthesis<br>
11
Key releases to highlight in a talk A compact presenter-friendly sequence from the article. Aspen (2011) Start of the modern city-release sequence. London/New York (2018-2019) Common baseline for older enterprise upgrade stories. Orlando/Paris (2020) Key transition period for many customers. San Diego/Tokyo (2022) Modern Now Platform cadence became visible in many roadmaps. Utah/Vancouver (2023) RTP/EA and GA planning became central to upgrade messaging. Washington/Xanadu (2024) N-1 and exam-window planning became especially visible. Yokohama/Zurich (2025) End of the alphabetic city cycle. Australia/Brazil (2026) Beginning of country-based release naming in the article. ServiceNow Release Timeline | Community article synthesis<br>
12
Practical upgrade conversation How to convert release knowledge into an upgrade readiness discussion. Which family are we on today?
Is it supported under the current N / N-1 policy?
What integrations, Store apps and customizations must be regression-tested?
Do we need RTP or EA to test earlier?
Are certification holders affected by Delta exam windows?
What is the change window and rollback plan? Admin check The article notes that users can check the release/version through System Diagnostics > Stats. Governance check Align upgrades with change management, business blackout windows and ownership of integrations. Executive check Explain the risk of falling behind in business terms: supportability, security, availability and feature access. ServiceNow Release Timeline | Community article synthesis<br>
Is it supported under the current N / N-1 policy?
What integrations, Store apps and customizations must be regression-tested?
Do we need RTP or EA to test earlier?
Are certification holders affected by Delta exam windows?
What is the change window and rollback plan? Admin check The article notes that users can check the release/version through System Diagnostics > Stats. Governance check Align upgrades with change management, business blackout windows and ownership of integrations. Executive check Explain the risk of falling behind in business terms: supportability, security, availability and feature access. ServiceNow Release Timeline | Community article synthesis<br>
13
Suggested narrative for your presentation A simple story arc for turning the article into a conference or community talk. 1 Origin From GlideSoft and early naming to a recognizable platform release culture. 2 Pattern City names, alphabetic order and a twice-yearly release rhythm. 3 Operation RTP, EA, GA, EOL, patches and exam windows. 4 Future End of the city alphabet and the move toward country names. ServiceNow Release Timeline | Community article synthesis<br>
14
Closing takeaway Release literacy is operational literacy. Closing takeaway The ServiceNow release name tells a story: where the platform is, what support window you are in, what upgrade motion is next, and how teams should prepare. Stay current Treat upgrades as a recurring operating model, not a one-time project. Test early Use RTP/EA when risk, complexity or timing requires earlier validation. Communicate impact Translate release dates into business risk, security, compliance and certification actions. Source: ServiceNow Community article "ServiceNow versions / Release" by tiagomacul; user-provided PDF snapshot dated 25/06/2026.<br>
15
Full release table (1/4): Early releases Source table from ServiceNow Community article snapshot; added as reference appendix. ServiceNow Release Timeline | Detailed release table appendix<br>
16
Full release table (2/4): City release era begins Source table from ServiceNow Community article snapshot; added as reference appendix. ServiceNow Release Timeline | Detailed release table appendix<br>
17
Full release table (3/4): Recent city releases Source table from ServiceNow Community article snapshot; added as reference appendix. ServiceNow Release Timeline | Detailed release table appendix<br>
18
Full release table (4/4): End of city cycle and country era Source table from ServiceNow Community article snapshot; added as reference appendix. ServiceNow Release Timeline | Detailed release table appendix<br>