Find the Best Cosmetic Hospitals

Explore trusted cosmetic hospitals and make a confident choice for your transformation.

“Invest in yourself — your confidence is always worth it.”

Explore Cosmetic Hospitals

Start your journey today — compare options in one place.

The evolution from XL Release → Digital.ai Release

1) Origins: XebiaLabs and the birth of XL Release (2008–2015)

  • Company founding (2008). XebiaLabs was founded in the Netherlands by Coert Baart and Vincent Partington (backed by the Xebia group). ()
  • XL Release launches (2013). XebiaLabs announced XL Release as an enterprise-class release coordination/orchestration product in Sept 2013. ()
  • Positioning & capabilities. XL Release was designed to plan, track, and execute releases (phases & tasks), acting as a “single source of truth” for release orchestration. ()
  • Community momentum (2014). XebiaLabs offered community editions of XL Release and XL Deploy to expand adoption. ()

Early feature trajectory (XL Release 4.x)

  • 4.5–4.7 era (2015–2016). The 4.x line cemented core concepts and added a stream of enhancements (API, triggers, etc.) documented in the historic 4.5/4.7 release notes. ()
  • XL Release’s reference manual from this period captures the canonical “releases → phases → tasks” model many enterprises standardized on. ()

2) The merger wave & rebrand to Digital.ai (2019–2020)

  • Pre-merger investment context. XebiaLabs had grown as a release/orchestration leader; on Jan 21, 2020 CollabNet VersionOne and XebiaLabs announced a combination to create an integrated Agile/DevOps platform (TPG Capital-backed). ()
  • Digital.ai is born (Apr 15, 2020). CollabNet VersionOne, XebiaLabs, and Arxan Technologies formally combined and rebranded as Digital.ai—an integrated value stream (DevSecOps) company. ()
  • Arxan’s role. Arxan (app protection) announced it “has come together with CollabNet VersionOne and XebiaLabs to form Digital.ai.” (Apr 16, 2020). ()

Post-formation acquisitions to fill out the platform (2020–2021)

  • Numerify (AI analytics) & Experitest (continuous testing) acquired June 16, 2020, extending analytics and mobile/web testing in the platform. ()

Branding/renaming impact on XL Release

  • The product name transitioned to Digital.ai Release (formerly XebiaLabs XL Release)—Digital.ai’s own materials state this directly. ()

3) What changed for customers after the rebrand

  • Continuity of product & artifacts. Documentation and container images retained legacy identifiers (e.g., xebialabs/xl-release) for continuity, while branding became Digital.ai Release. Red Hat’s container catalog still lists xebialabs/xl-release images (e.g., 9.0.11). ()
  • Support & lifecycle policies modernized. Digital.ai has published EOL/deprecation guidance (e.g., no “latest” Docker tag for Release images effective Oct 31, 2024; you must pull by explicit version). ()

4) Digital.ai corporate & platform milestones (selected)

  • Digital.ai launch & first value-stream vision (Apr 2020). ()
  • Forrester VSM leadership recognition (Q3 2020). ()
  • Named platform releases (e.g., Denali, Banff) highlight periodic, cross-portfolio drops. ()
  • Ongoing feature launches across Release/Deploy/Testing, including 2023–2026 updates to streamline enterprise delivery. ()

5) Product timeline: from XL Release to Digital.ai Release

XL Release era (pre-2020)

  • 2013: XL Release GA. ()
  • 2014: Community edition offered. ()
  • 2015–2016: XL Release 4.5 → 4.7 → 4.8 (and beyond) add robust API, trigger, and orchestration features (see 4.7.x notes & contemporaneous posts). ()

Digital.ai Release era (2020 → present)

Digital.ai documents the product simply as “Release” with numeric streams (22.x, 23.x, 24.x, 25.x). Selected highlights:

  • 22.x (2022): New Release versions under the Digital.ai banner appear in docs (e.g., 22.3; CLI enhanced for new operator-based install). ()
  • 24.x (2024): The Release docs standardize on current install/upgrade guidance and operator/Kubernetes paths (also see EOL policy introduced for Docker tags in 2024). ()
  • 25.3 (Oct 2026): Latest major stream at time of writing; Bitnami Helm charts deprecated beginning 25.3, to be removed in later versions. (Parallel 25.3 updates exist across Deploy/Testing as well.) ()

Tip: Digital.ai Release is now the canonical name. Legacy “XL” labels may still exist in image names, some configuration keys, and historical docs; functionally you’re looking at a continuous lineage. ()


6) Ownership today

  • Owner: Digital.ai (formed by the 2020 combination of CollabNet VersionOne, XebiaLabs, and Arxan; subsequently expanded via acquisitions like Numerify and Experitest). ()

7) Practical migration & versioning notes (for teams coming from “XL Release”)

  • Naming & artifacts: Expect mixed legacy naming in technical artifacts (e.g., Docker xebialabs/xl-release). Follow the EOL policy: always pin explicit versions (no :latest after Oct 31, 2024). ()
  • Upgrade approach: Use the current upgrade guides (JVM or Kubernetes/operator paths) aligned with your deployment model. ()
  • Compatibility planning: When moving from older 4.x/early “XL Release” versions, review historic release notes to catch deprecations and manual actions. ()

8) Concise timeline (company + product)

  • 2008: XebiaLabs founded. ()
  • 2013: XL Release launched (release orchestration). ()
  • 2014–2016: 4.x feature maturation; community editions announced (2014). ()
  • Jan 21, 2020: CollabNet VersionOne + XebiaLabs announce combination (TPG). ()
  • Apr 15–16, 2020: Digital.ai formed; Arxan joins the combined company; XL Release continues under the Digital.ai Release name. ()
  • Jun 16, 2020: Digital.ai acquires Numerify (AI analytics) and Experitest (continuous testing). ()
  • 2022–2026: Major Release streams 22.x → 25.x; operator-based install work, lifecycle tightening (Docker tag policy), and 25.3 deprecates Bitnami Helm charts. ()

9) Where to track “what’s new” next

  • Release (product) notes: Best single source for version-by-version changes (e.g., 25.3). ()
  • Upgrade guides & support policy: For impact/planning and supported paths. ()
  • Corporate history & press releases: For rebrand/acquisition context. ()

Find Trusted Cardiac Hospitals

Compare heart hospitals by city and services — all in one place.

Explore Hospitals
I’m a DevOps/SRE/DevSecOps/Cloud Expert passionate about sharing knowledge and experiences. I have worked at <a href="https://www.cotocus.com/">Cotocus</a>. I share tech blog at <a href="https://www.devopsschool.com/">DevOps School</a>, travel stories at <a href="https://www.holidaylandmark.com/">Holiday Landmark</a>, stock market tips at <a href="https://www.stocksmantra.in/">Stocks Mantra</a>, health and fitness guidance at <a href="https://www.mymedicplus.com/">My Medic Plus</a>, product reviews at <a href="https://www.truereviewnow.com/">TrueReviewNow</a> , and SEO strategies at <a href="https://www.wizbrand.com/">Wizbrand.</a> Do you want to learn <a href="https://www.quantumuting.com/">Quantum Computing</a>? <strong>Please find my social handles as below;</strong> <a href="https://www.rajeshkumar.xyz/">Rajesh Kumar Personal Website</a> <a href="https://www.youtube.com/TheDevOpsSchool">Rajesh Kumar at YOUTUBE</a> <a href="https://www.instagram.com/rajeshkumarin">Rajesh Kumar at INSTAGRAM</a> <a href="https://x.com/RajeshKumarIn">Rajesh Kumar at X</a> <a href="https://www.facebook.com/RajeshKumarLog">Rajesh Kumar at FACEBOOK</a> <a href="https://www.linkedin.com/in/rajeshkumarin/">Rajesh Kumar at LINKEDIN</a> <a href="https://www.wizbrand.com/rajeshkumar">Rajesh Kumar at WIZBRAND</a> <a href="https://www.rajeshkumar.xyz/dailylogs">Rajesh Kumar DailyLogs</a>

Related Posts

5 Ways AI is Replacing Manual GTM Work (And What to Do About It)

B2B revenue organizations have been drowning in operational friction. Think siloed data ecosystems, seemingly endless spreadsheet manipulation, and highly fragmented tech stacks. All stall execution velocity when…

Read More

Why Every DevOps Team Needs an AI Red Teaming Strategy

Source: DepositPhotos AI agents are already being connected to internal APIs, ticketing systems, cloud infrastructure, and deployment workflows. In many environments, they also interact with customer data,…

Read More

DevOps Lifecycle Components: CI/CD, Infrastructure, and Observability

Introduction In the current era of software development, the gap between writing code and delivering that code to end-users has narrowed significantly. Gone are the days when…

Read More

Ruby on Rails vs Node.js: Performance, Speed, and Scalability Compared

Choosing between Ruby on Rails and Node.js is a common decision when building modern web applications. Both frameworks power large-scale products, but they approach performance, concurrency, and…

Read More

How Zero-Knowledge Coprocessors Are Reshaping Web3 Computation

Developers often hit a brick wall when building decentralized apps. Standard infrastructure just fails to keep up. Clogging a main network with heavy workloads leads to slow…

Read More

5 Top Developer Experience (DevEx) Insight Tools for 2026

Developer experience has evolved from an internal engineering concern into a measurable operational discipline. As software organizations scale across distributed cloud environments, platform engineering initiatives, AI-assisted development…

Read More
Subscribe
Notify of
guest
1 Comment
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Skylar Bennett
Skylar Bennett
5 months ago

This article explains the evolution of XL Release into Digital.ai Release, highlighting the advancements in release orchestration that come with the rebranding. Initially, XL Release was focused on helping teams manage releases through a structured system of phases and tasks. However, after merging with other vendors, it transformed into Digital.ai Release, now offering a broader DevSecOps platform with enhanced features. The update brings improvements such as better integrations, analytics, and scalability, as well as stronger security and compliance support. These changes help teams streamline and manage complex release pipelines more effectively, aligning with modern DevOps practices and enterprise requirements. This evolution demonstrates how release orchestration has advanced from basic task management to more comprehensive, governed, and scalable solutions.

1
0
Would love your thoughts, please comment.x
()
x