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

Create an RFC for change-controlled DM document Git branch and release policy

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Design Documents
    • Labels:
      None
    • Templates:
    • Story Points:
      4.8
    • Team:
      SQuaRE

      Description

      Wil, Frossie, Tim, and I have discussed a new change-controlled document Git repository workflow to replace the current policy (release on master, work on draft).

      The basic features of the new workflow are:

      • Development on master in ticket branches. In general, document development should mirror code development workflows.
      • Release branches (named after the corresponding RFC or LCR) that are never merged back to master.
      • The release manager backports commits on the release branches (amendments requested by a CCB) to the master branch.
      • Tags for docushare upload number and document version.
      • A moving tag for the docushare preferred version.

      These tags are an API for LSST the Docs (lsst.io) and for future DocuShare automation.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jsick Jonathan Sick
                Reporter:
                jsick Jonathan Sick
                Reviewers:
                Tim Jenness
                Watchers:
                Frossie Economou, John Swinbank, Jonathan Sick, Tim Jenness, Wil O'Mullane
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel