Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-5386 Automate mongodb-client-encryption release process
  3. NODE-6164

Create new repository for node bindings

XMLWordPrintableJSON

    • Type: Icon: Sub-task Sub-task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • 0
    • Not Needed
    • Hide

      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.

      Show
      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.
    • Not Needed
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      Use Case

      As a Node.js engineer
      I want to move our libmongocrypt bindings to their own repository
      So that we can apply various existing tools that expect our package to be at the top level.

      User Impact

      • None. The next npm release produced will update the "repository" field.

      Dependencies

      • libmongocrypt

      Unknowns

      • None

      Acceptance Criteria

      Implementation Requirements

      • Make a new repository mongodb/mongodb-client-encryption in MANA
      • Add Node.js bindings to new repo while preserving commit history. Something like:
        • git subtree split -P bindings/node -b node-bindings
        • git pull --allow-unrelated-histories path-to/libmongocrypt node-bindings 
      • Copy over driver pull request template and release scripting

      Testing Requirements

      • None

      Documentation Requirements

      • None

      Follow Up Requirements

      • None

            Assignee:
            neal.beeken@mongodb.com Neal Beeken
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: