Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-9419

[Docs] Avoid specifying Backstage patch versions in release notes

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Documentation
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Moderate

      As discussed in this Slack thread , it might be good to clarify the Backstage version that we adopt.  Instead of targeting a specific patch version, we can mention the minor version so we have leeway to update to the next minor version for patching if we need to.

      For example in 1.7, instead of mentioning "Backstage 1.39.1", we should say "Backstage 1.39"

       

      Who is your target persona?

      <Role>

      What stage of the user journey are you targeting?

      <User journey>

      Why is this content important?

      <Justification>

      What is the main user goal aka job to be done?

      As a <role>, I want to <goal>

      What high level steps does the user need to take to accomplish the goal?

      1. <User steps to accomplish goal>

      What pain points are the user likely to encounter when accomplishing this goal?

      <Pain points>

      Links to existing content

      • <Add link to content>

      People:

      • SME: <SME>
      • QE: <QE>

      Release Note: Yes/No

      Documentation Outline

      • <Documentation outline>

              rhn-support-kavverma Kavya Verma
              ktsao@redhat.com Kim Tsao
              RHIDP - Documentation
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: