Continuous Delivery Strategy

Describes the Broadcom mainframe division Continuous Delivery strategy.
cmcm10
We are pleased to announce that the
Broadcom
Mainframe Division release strategy is evolving to Continuous Delivery (CD). Continuous Delivery releases are generally available, and customers are fully supported when running on the CD release.
Broadcom
product teams provide new enhancements throughout the CD releases to enable customers to deploy and take advantage of new capabilities immediately. CD aligns with industry standard naming convention and describes how we are delivering value to our customers.
Focus on Delivering Value
  • Releases are generally available and fully supported through the lifecycle of the CD release, as the requirement to be on the latest "increment" has been removed.
  • Broadcom
    product teams provide new enhancements on the CD releases to enable customers to deploy and take advantage of new capabilities immediately. The CD model avoids the major release deployment and adoption hurdle where large amounts of change are deployed at one time.
  • Broadcom
    product teams continue to test the new features and capabilities before making them generally available. In addition, customers can often participate in the validation program to also test features and capabilities before general availability. Customers wishing to participate can register here: validate.broadcom.com.
  • Enhancements are delivered as disabled where logical to do so on the CD release. There may be cases where shipping enhancements as disabled is not desirable or feasible, such as UI changes or performance improvements.
  • When new features are disabled upon delivery, customers must take an explicit action to activate or must take advantage of the features. Activation mechanisms may include, but are not limited to:
    • A parmlib member setting
    • A command with a new option that is required to take action or to display additional information
  • The shipping of disabled features provides customers greater and more granular control of when new changes are activated.
  • While rare, there may be situations where a new feature requires a previously disabled feature to be enabled. If a product enables a previously disabled feature through a PTF, the HOLDDATA reflects the action.
  • Announcement letters, PTF HOLDDATA, Release Notes, and product documentation contain details for each feature.
We understand the CD release may not be suited for every customer. Customers who favor maintenance only, with no new enhancements, are encouraged to run on the supported GA-1 release where offered. Compatibility and toleration for new zSystem boxes and new z/OS releases is provided for all generally available releases as feasible.
Product Transition to Continuous Delivery
  • Products participating in CD can be found here.
  • Some products transition to CD on their current generally available release while other products start a new release to commence CD.
  • Product areas issue announcements when they transition to the CD release model or start CD.
  • We anticipate running on a given CD release for an extended timeframe. Should an incompatible architecture change or similar driving factor be a catalyst for a new release, the products commence delivery on a new CD release.
Strategic Initiatives to Support Continuous Delivery
  • Announcement letters are sent to customers by the product teams when new features and capabilities become generally available.
  • PTF HOLDDATA, Release Notes, and documentation to articulate the use case, value of the deliverable, how to enable and how to use.
Maintenance
The CD release strategy uses existing maintenance best practice recommendations.