Release Notes for DevOps Velocity 2023.12 (5.0.x)

This document includes information about the new features introduced, defects fixed, and known issues identified in this version of IBM® DevOps Velocity (Velocity). You can also find the installation and upgrade instructions along with the contact information of IBM Customer Support.

Current documentation version: 5.0.11

Product description

Velocity automates processes in your release lifecycle and gathers insights into your DevOps processes. It is an enterprise-scale release management service that supports both cloud-native and on-premises deployment tools. For more information about the Velocity, see Overview of DevOps Velocity.

What's New

You can find information about the features introduced, enhancements, or other changes in Velocity. See What's New.

Defect fixes

For the list of defects fixed in this version that include defects submitted by customers and defects found during testing, see Defect fixes.

Product download and installation

If you have purchased the licenses to use the product, you can download the product software packages from IBM Passport Advantage.

For instructions about installing the product software, see Installing DevOps Velocity.

Contacting IBM DevOps Automation Support

  • For contact information and guidelines or reference materials that you might need when you require support, read the IBM Support Guide.
  • For personalized support that includes notifications of significant upgrades, subscribe to Product notification.
  • Before you contact IBM DevOps Automation Support, you must gather the background information that you might need to describe your problem. When you describe a problem to an IBM DevOps Automation Support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
    • What software versions were you running when the problem occurred?
    • Do you have logs, traces, or messages that are related to the problem?
    • Can you reproduce the problem? If so, what steps do you take to reproduce it?
    • Is there a workaround for the problem? If so, be prepared to describe the workaround.