Versions Compared

Old Version 2

changes.mady.by.user Andrew Woods

Saved on

compared with

New Version 3

changes.mady.by.user Andrew Woods

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • You have an account with commit access for the vivo-project on github. As a committer, you should already have this level of access.
  • You have an account with edit privileges on the duraspace.org Confluence wiki.
  • You have an oss.sonatype.org account and have requested to be given permission to publish to the org.vivoweb groupId by adding a comment to the VIVO Sonatype Hosting Ticket
  • You have project configuration privileges on JIRA (you'll see an error here if you don't)

  • Your maven settings (~/.m2/settings.xml) includes the following:

    Code Block
    <settings>
  ...
  <servers>
    ...
    <server>
      <id>sonatype-nexus-snapshots</id>
      <username>your-jira-id</username>
      <password>your-jira-pwd</password>
    </server>
    <server>
      <id>sonatype-nexus-staging</id>
      <username>your-jira-id</username>
      <password>your-jira-pwd</password>
    </server>
    <server>
      <id>github</id>
      <username>your-github-id</username>
      <password>your-github-pwd</password>
    </server>
  </servers>
  ...
</settings>


Ensure you have a trusted code signing key

Prepare and distribute test plan

The test plan should also be ready prior to code freeze.