Uploaded image for project: 'Service Binding'
  1. Service Binding
  2. APPSVC-665

Define SLA for RedHat Helm Chart Repo PRs

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Helm
    • None
    • 3
    • Sprint 188

      During our regular weekly Helm meeting with IBM folks, Nancy Heinz
      asked me if RedHat has any SLA on merging PRs, in this particular
      case on redhat-developer/redhat-helm-charts repo. They would like to have a way to signal us if a PR is an emergency, so that we could merge it fast. Also, they would like to know what would our standard SLA (the max number of days we need to react on a PR).

      The following actions list came out of the discussion with shbose, pradeeptob and ssadeghi:

      1. Let's have a mailing list helm-catalog-support@redhat.com monitored by the app services team.
      2. Publish a note on the Github Repo that PR submitters must send an email to it explaining the criticality of a PR if there's a need for a PR to have special attention. Otherwise, we shall have a team member take a look at it within the next working day.

        1. github-action.png
          25 kB
          Predrag Knezevic
        2. image-2020-08-26-18-50-57-167.png
          25 kB
          Predrag Knezevic

              pedjak@gmail.com Predrag Knezevic (Inactive)
              pedjak@gmail.com Predrag Knezevic (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: