Feature Overview (aka. Goal Summary)

There is confusion today about the timelines/processes for branching, backporting, maintenance, CVEs.

We need concise procedures for:

• how/when to branch (on Feature Freeze day, run https://gitlab.cee.redhat.com/rhidp/rhdh/-/blob/rhdh-1-rhel-9/build/scripts/tagRelease.sh),
• what plugin version bumping needs to happen at that time (see https://docs.google.com/document/d/1royFXscxWRdI8Woh9_1RmO0c1RgSGFWx0abWzeo_skc/edit?tab=t.0#heading=h.e5twoevjoa9r) ,
• how this impacts janus-idp/backstage-plugins as well as rhdh-plugins and BCP repos (see previous doc)
• how to handle features/minor updates in cherrypicks/backports (talk to Release Manager or Product Manager)
• how to articulate which versions of Backstage/RHDH are supported by a given plugin (WIP to declare this in the upstream repos and overlays repo)
  • Need both minimum and maximum values
  • ie., does plugin foo run on BS 1.29.2 / RHDH 1.3 AND on BS 1.32.0 / RHDH 1.4
  • tracked in RHIDP-7357

Also need procedures for doc updates:

• Release Notes (bug fixes) - see https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/blob/main/modules/release-notes/README.adoc
• Dynamic Plugins table updates - see https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/blob/main/modules/dynamic-plugins/rhdh-supported-plugins.sh (deprecated, will be replaced once we move to the dynamic plugin catalog / extensions marketplace)
  • tracked in RHIDP-7524 and RHIDP-7961

See also Plugin versioning scheme proposal

Goals (aka. expected user outcomes)

Doc in https://github.com/redhat-developer/rhdh-team-docs/tree/main/docs

Requirements (aka. Acceptance Criteria):

• define processes
• agree on conventions
• follow them
• script what we can
• document/recommend what we can't automate