Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-6919

Please rename "afterburners"

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Story Points:
      1
    • Epic Link:
    • Sprint:
      DRP F16-3
    • Team:
      Data Release Production

      Description

      In DM-4887 we introduced a new measurement post-processing system which we called "afterburners".

      The term "afterburner" is overloaded and applied in multiple contexts. To save confusion, please rename this system to something less ambiguous. Best if we can do this soon, before this usage spreads.

        Attachments

          Issue Links

          is triggered by

          RFC - An issue whose primary purpose is to advertise an intent and allow stakeholders to comment. RFC-207 Rename Afterburner plugins to CatalogCalculation plugins

          • Implemented
          is triggering

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-7428 Update pipe_tasks' testTransform to use catalogCalculation rather than afterburner

          • Done
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-4887 Refactor measurement afterburners into a new plugin system

          • Done
          mentioned in

          Page Loading...

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            fred3m Fred Moolekamp added a comment -

            I added a few styling comments in meas_base and pipe_tasks but other than a few nitpicky things it should be ready to merge. Since this is a change in the API, is there anything additional that needs to be done to alert users that their pipelines might need to be slightly modified?

            Show
            fred3m Fred Moolekamp added a comment - I added a few styling comments in meas_base and pipe_tasks but other than a few nitpicky things it should be ready to merge. Since this is a change in the API, is there anything additional that needs to be done to alert users that their pipelines might need to be slightly modified?
            Hide
            Permalink
            nlust Nate Lust added a comment -

            merged

            Show
            nlust Nate Lust added a comment - merged

              People

              Assignee:
              nlust Nate Lust
              Reporter:
              swinbank John Swinbank
              Reviewers:
              Fred Moolekamp
              Watchers:
              Fred Moolekamp, John Swinbank, Nate Lust
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.