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

Update third party packaging guide

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Story Points:
      0.2
    • Epic Link:
    • Sprint:
      DRP X16-2
    • Team:
      Data Release Production

      Description

      When packaging ngmix, I sought out answers to the following questions:

      1. Which teams need permissions on it? "DM Externals" sounds plausible, but I'm not sure.
      2. What about the version number? Upstream haven't made a versioned release. I was planning to tag it with git SHA1. Does that work, or does it break assumptions that versions are lexicographically sorted or something like that?

      Answers (courtesy Frossie Economou and Tim Jenness) were:

      1. Yes, DM Externals (& presumably also Overlords).
      2. SHA1 is fine, but version numbers shouldn't start with a letter or EUPS gets confused.

      Please add these helpful answers to the developer docs.

        Attachments

          Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-2253 add third-party package builds for ngmix dependencies

          • Done

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            swinbank John Swinbank added a comment -

            Tim Jenness – is this a fair summary of what you told me on HipChat?

            Show
            swinbank John Swinbank added a comment - Tim Jenness – is this a fair summary of what you told me on HipChat?
            Hide
            Permalink
            tjenness Tim Jenness added a comment -

            Looks okay in general. I have a comment on the PR concerning a bit of text you didn't write and I wonder whether we should be explicit in SHA1 version numbers about using an incrementing prefix integer.

            Show
            tjenness Tim Jenness added a comment - Looks okay in general. I have a comment on the PR concerning a bit of text you didn't write and I wonder whether we should be explicit in SHA1 version numbers about using an incrementing prefix integer.
            Hide
            Permalink
            swinbank John Swinbank added a comment -

            Changes made as suggested & merged to master.

            Show
            swinbank John Swinbank added a comment - Changes made as suggested & merged to master.

              People

              Assignee:
              swinbank John Swinbank
              Reporter:
              swinbank John Swinbank
              Reviewers:
              Tim Jenness
              Watchers:
              Frossie Economou, John Swinbank, 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.