Story (Required)

As a developer/customer, I want to mark the old channel in OpenShift Builds catalog as deprecated.

Background (Required)

With the last OpenShift Builds 1.1 release, a new "stable" channel was created and there was change the naming syntax of the the existing channels. Now with the the next release unnecessary "stable" and the existing duplicate channels should be marked as deprecated in the OpenShift Console, for users to start using the right channel.

Out of scope

Approach (Required)

Modify the `Package Manifest` to add "deprecation" key and a "message" for the users.
Ref: https://docs.google.com/document/d/1SLgERsnNwNN7PuABdzysmxYxzD-hiyh7yuJc1m2Hy98/edit?tab=t.0#heading=h.6uwq63r4jj80

Dependencies

Acceptance Criteria (Mandatory)

• Older channels should show deprecated in the console
• A message should be displayed for user to use the corresponding right channel

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met