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

Mention self-merge for repos.yaml in documents

    XMLWordPrintable

Details

    Description

      The conclusion of RFC-75 asks for the process to be documented in https://confluence.lsstcorp.org/display/LDMDG/Adding+a+new+package+to+the+build. Please do so.

      Attachments

        Issue Links

          Activity

            Before I found this issue, I added a brief note to Confluence myself. jhoblitt may wish to expand, correct or replace what I've written.

            swinbank John Swinbank added a comment - Before I found this issue, I added a brief note to Confluence myself. jhoblitt may wish to expand, correct or replace what I've written.

            I swear added a blurb to developer guide long ago but it appears to have been lost...

            jhoblitt Joshua Hoblitt added a comment - I swear added a blurb to developer guide long ago but it appears to have been lost...

            Looks like my blurb has been lost to the either. swinbank thanks for putting those notes together – I don't think I can add much to that.

            jsick Do you want to sit down at some point to go over what swinbank posted?

            jhoblitt Joshua Hoblitt added a comment - Looks like my blurb has been lost to the either. swinbank thanks for putting those notes together – I don't think I can add much to that. jsick Do you want to sit down at some point to go over what swinbank posted?

            I'd prefer to have the policy/procedure documents be self-contained rather than referring to RFCs (except perhaps for reasoning or background), so I think swinbank's modification still needs to be expanded a bit.

            ktl Kian-Tat Lim added a comment - I'd prefer to have the policy/procedure documents be self-contained rather than referring to RFCs (except perhaps for reasoning or background), so I think swinbank 's modification still needs to be expanded a bit.
            jsick Jonathan Sick added a comment - - edited

            Sorry, I just found this ticket. Yes, the self-merge policy is technically documented in https://developer.lsst.io/build-ci/new_package.html :

            The new package must be added to the etc/repos.yaml file in the lsstsw package along with its corresponding GitHub URL. This file is governed by a “self-merge” policy: upon opening a pull request, it will be checked by the Travis CI system, and developers may merge without further review on success. Refer to RFC-75 for background.

            But I think I can restructure that page a bit to make the process easier to follow and have policies more clearly defined. I'll take the ticket on.

            jsick Jonathan Sick added a comment - - edited Sorry, I just found this ticket. Yes, the self-merge policy is technically documented in https://developer.lsst.io/build-ci/new_package.html : The new package must be added to the etc/repos.yaml file in the lsstsw package along with its corresponding GitHub URL. This file is governed by a “self-merge” policy: upon opening a pull request, it will be checked by the Travis CI system, and developers may merge without further review on success. Refer to RFC-75 for background. But I think I can restructure that page a bit to make the process easier to follow and have policies more clearly defined. I'll take the ticket on.
            jhoblitt Joshua Hoblitt added a comment - Is this issue resolved by https://developer.lsst.io/build-ci/new_package.html#adding-a-new-package-to-the-build  ?
            tjenness Tim Jenness added a comment - This has been done already: see https://developer.lsst.io/stack/adding-a-new-package.html

            People

              jsick Jonathan Sick
              ktl Kian-Tat Lim
              Jonathan Sick, Joshua Hoblitt, Kian-Tat Lim, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jenkins

                  No builds found.