Giter VIP home page Giter VIP logo

bammetrics's Introduction

bammetrics's People

Contributors

davycats avatar ffinfo avatar jasperboom avatar rhpvorderman avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

bammetrics's Issues

Release 2.1.0

  • Check outstanding issues on JIRA and Github
  • Update all submodules to latest master with: git submodule foreach "git checkout master;git pull; git submodule foreach --recursive 'git fetch'; git submodule update --init --recursive"
  • check all submodules are tagged correctly with git submodule
  • run tests to confirm to be released version works.
  • Generate inputs overview using wdl-aid:
    wdl-aid --strict -t scripts/docs_template.md.j2 pipeline.wdl > docs/inputs.md
  • Publish documentation (updateDocs.sh) from develop branch
    • Copy docs folder to gh-pages branch
    • Overwrite existing develop folder with docs folder on gh-pages
    • Push changes to gh-pages branch
  • Check latest documentation
    looks fine
  • Change current development version in CHANGELOG.md to stable version.
  • Run the release script release.sh
    • Check all submodules are tagged
    • Merge the develop branch into master
    • Created an annotated tag with the stable version number. Include changes
      from changelog.md.
    • Confirm or set stable version to be used for tagging
    • Push tag to remote.
    • Merge master branch back into develop.
    • Add updated version number to develop
  • Publish documentation (updateDocs.sh) from master branch
    • Copy docs folder to gh-pages branch
    • Rename docs to new stable version on gh-pages
    • Set latest version to new version
    • Push changes to gh-pages branch
  • Create a new release from the pushed tag on github
  • Prepare the repo for packaging by git checkout master && git submodule update --init --recursive
    • Package the wdl files with wdl-packager --reproducible -a LICENSE -a dockerImages.yml <WDL_FILE>
    • Add the package(s) to the github release. Also add the original WDL file
      as <pipeline>_<version>.wdl following the same naming as the package.
      This alllows for usage of wdl and imports zip with cromwell without
      requiring the user to extract the package.

version 2.2.0

  • Check outstanding issues on JIRA and Github.
  • Update all submodules to latest master
    with: git submodule foreach "git checkout master;git pull; git submodule foreach --recursive 'git fetch'; git submodule update --init --recursive".
  • Check all submodules are tagged correctly with git submodule.
  • Run tests to confirm to be released version works.
  • Generate inputs overview using wdl-aid:
    wdl-aid --strict -t scripts/docs_template.md.j2 pipeline.wdl > docs/inputs.md
  • Publish documentation (updateDocs.sh) from develop branch.
    • Copy docs folder to gh-pages branch.
    • Overwrite existing develop folder with docs folder on gh-pages.
    • Push changes to gh-pages branch.
  • Check latest documentation looks fine.
  • Change current development version in CHANGELOG.md to stable version.
  • Run the release script release.sh.
    • Check all submodules are tagged.
    • Merge the develop branch into master.
    • Created an annotated tag with the stable version number.
      Include changes from changelog.md.
    • Confirm or set stable version to be used for tagging.
    • Push tag to remote.
    • Merge master branch back into develop.
    • Add updated version number to develop.
  • Publish documentation (updateDocs.sh) from master branch.
    • Copy docs folder to gh-pages branch.
    • Rename docs to new stable version on gh-pages.
    • Set latest version to new version.
    • Push changes to gh-pages branch.
  • Create a new release from the pushed tag on github.
  • Prepare the repo for packaging
    by git checkout master && git submodule update --init --recursive.
    • Package the wdl files with wdl-packager --reproducible -a LICENSE -a dockerImages.yml <WDL_FILE>.
    • Add the package(s) to the github release. Also add the original WDL
      file as <pipeline>_<version>.wdl following the same naming as the
      package.
      This alllows for usage of wdl and imports zip with cromwell without
      requiring the user to extract the package.

Release 1.1.0

Release checklist

  • Check outstanding issues on JIRA and Github
  • Publish documentation (updateDocs.sh) from develop branch
    • Copy docs folder to gh-pages branch
    • Overwrite existing develop folder with docs folder on gh-pages
    • Push changes to gh-pages branch
  • Check latest documentation
    looks fine
  • Change current development version in CHANGELOG.md to stable version.
  • Run the release script release.sh
    • Check all submodules are tagged
    • Merge the develop branch into master
    • Created an annotated tag with the stable version number. Include changes
      from changelog.md.
    • Confirm or set stable version to be used for tagging
    • Push tag to remote.
    • Merge master branch back into develop.
    • Add updated version number to develop
  • Publish documentation (updateDocs.sh) from master branch
    • Copy docs folder to gh-pages branch
    • Rename docs to new stable version on gh-pages
    • Set latest version to new version
    • Push changes to gh-pages branch
  • Create a new release from the pushed tag on github

Release v2.0.0

Release checklist

  • Check outstanding issues on JIRA and Github
  • Update all submodules to latest master with: git submodule foreach "git checkout master;git pull; git submodule foreach --recursive 'git fetch'; git submodule update --init --recursive"
  • check all submodules are tagged correctly with git submodule
  • run tests to confirm to be released version works.
  • Generate inputs overview using wdl-aid:
    wdl-aid --strict -t scripts/docs_template.md.j2 pipeline.wdl > docs/inputs.md
  • Publish documentation (updateDocs.sh) from develop branch
    • Copy docs folder to gh-pages branch
    • Overwrite existing develop folder with docs folder on gh-pages
    • Push changes to gh-pages branch
  • Check latest documentation
    looks fine
  • Change current development version in CHANGELOG.md to stable version.
  • Run the release script release.sh
    • Check all submodules are tagged
    • Merge the develop branch into master
    • Created an annotated tag with the stable version number. Include changes
      from changelog.md.
    • Confirm or set stable version to be used for tagging
    • Push tag to remote.
    • Merge master branch back into develop.
    • Add updated version number to develop
  • Publish documentation (updateDocs.sh) from master branch
    • Copy docs folder to gh-pages branch
    • Rename docs to new stable version on gh-pages
    • Set latest version to new version
    • Push changes to gh-pages branch
  • Create a new release from the pushed tag on github

Release 1.2.0

Release checklist

  • Check outstanding issues on JIRA and Github
  • Generate inputs overview using wdl-aid:
    wdl-aid --strict -t scripts/docs_template.md.j2 pipeline.wdl > docs/inputs.md
  • Publish documentation (updateDocs.sh) from develop branch
    • Copy docs folder to gh-pages branch
    • Overwrite existing develop folder with docs folder on gh-pages
    • Push changes to gh-pages branch
  • Check latest documentation
    looks fine
  • Update all submodules to latest master with: git submodule foreach "git checkout master;git pull; git submodule foreach --recursive 'git fetch'; git submodule update --init --recursive"
  • check all submodules are tagged correctly with git submodule
  • run tests to confirm to be released version works.
  • Change current development version in CHANGELOG.md to stable version.
  • Run the release script release.sh
    • Check all submodules are tagged
    • Merge the develop branch into master
    • Created an annotated tag with the stable version number. Include changes
      from changelog.md.
    • Confirm or set stable version to be used for tagging
    • Push tag to remote.
    • Merge master branch back into develop.
    • Add updated version number to develop
  • Publish documentation (updateDocs.sh) from master branch
    • Copy docs folder to gh-pages branch
    • Rename docs to new stable version on gh-pages
    • Set latest version to new version
    • Push changes to gh-pages branch
  • Create a new release from the pushed tag on github

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.