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

Outline L1 Minimum Viable System

    XMLWordPrintable

    Details

    • Story Points:
      3
    • Sprint:
      Alert Production S17 - 6
    • Team:
      Alert Production

      Description

      Outline and prioritize components required for end-to-end testing of L1 alert generation--most immediately to enable verify_ap development (DM-9676 and others).

        Attachments

          Issue Links

            Activity

            ebellm Eric Bellm created issue -
            ebellm Eric Bellm made changes -
            Field Original Value New Value
            Epic Link DM-10775 [ 32741 ]
            ebellm Eric Bellm made changes -
            Status To Do [ 10001 ] In Progress [ 3 ]
            ebellm Eric Bellm made changes -
            Remote Link This issue links to "Page (Confluence)" [ 15226 ]
            Show
            ebellm Eric Bellm added a comment - Draft at https://confluence.lsstcorp.org/display/~ebellm/AP+Minimum+Viable+System
            ebellm Eric Bellm made changes -
            Reviewers Meredith Rawls [ mrawls ]
            Status In Progress [ 3 ] In Review [ 10004 ]
            Hide
            mrawls Meredith Rawls added a comment -

            The document is a great outline! Just a few thoughts.

            • We should make a plan to update it regularly as new tickets are created for different pieces. Maybe add a column explicitly for ticket references?
            • Consider adding links to different stack modules that pertain to the bulk of each section/item's work
            • If you have a distilled set of your/my/others' notes from meetings over the last week that would flesh out more of the MVS details, consider adding this (to the end?) or linking to it
            Show
            mrawls Meredith Rawls added a comment - The document is a great outline! Just a few thoughts. We should make a plan to update it regularly as new tickets are created for different pieces. Maybe add a column explicitly for ticket references? Consider adding links to different stack modules that pertain to the bulk of each section/item's work If you have a distilled set of your/my/others' notes from meetings over the last week that would flesh out more of the MVS details, consider adding this (to the end?) or linking to it
            mrawls Meredith Rawls made changes -
            Status In Review [ 10004 ] Reviewed [ 10101 ]
            swinbank John Swinbank made changes -
            Team Alert Production [ 10300 ]
            mrawls Meredith Rawls made changes -
            Link This issue relates to DM-10088 [ DM-10088 ]
            Hide
            ebellm Eric Bellm added a comment -

            I made the requested changes, although as we discussed I skipped listing the stack modules for now.

            Show
            ebellm Eric Bellm added a comment - I made the requested changes, although as we discussed I skipped listing the stack modules for now.
            ebellm Eric Bellm made changes -
            Resolution Done [ 10000 ]
            Status Reviewed [ 10101 ] Done [ 10002 ]

              People

              Assignee:
              ebellm Eric Bellm
              Reporter:
              ebellm Eric Bellm
              Reviewers:
              Meredith Rawls
              Watchers:
              Eric Bellm, Meredith Rawls
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: