Skip to content

Release Guidelines for Maintainers

These are a set of pre-release checklists used by the VIVA+ maintainers to ensure quality of the releases. These are the checklists used for VIVA+ releases

Checklist for MINOR releases

  • Update version number on the main files (*COMMENT, *TITLE)
  • Ensure CHANGELOG reflects the updates
  • Run Robustness Tests (for all releases)

If the updates are not backwards compatible for the pre-/post-processing, follow the checklist for MAJOR release also.

Robustness Tests (for all releases)

The Robustness Tests are maintained at https://openvt.eu/fem/viva/vivaplus-robustness

Checklist for running robustness tests

  • In the release branch of VIVA+, update *TITLEin the input deck with release candidate status, for example, v1.0.0rc2
  • If you don't have a local copy of the VIVA+ Robustness Repo, clone it from the repo above
  • Update the vivaplus folder with the new version to be tested using git subtree command 
    git subtree pull --prefix vivaplus https://openvt.eu/fem/viva/vivaplus.git release-branch-name --squash
    Change release-branch-name to the branch that needs to be tests
  • If this is a major release, continue with the Validation Evaluations

Checklist for MAJOR releases

  • Verify that the *ELEMENT_SOLID follows LSDYNA R960 format (if the vivaplus_elements.k has been updated)
  • Check header (or ANSA comments) in all include files
  • Re-run validation catalog

Model Validation (evaluated for major releases)

Rerun the model validation loadcases available on the validation catalog repository

Run validations for new version

  • If you don't have a local copy of the VIVA+ Validation Catalog, clone it from the repo above
  • Update the vivaplus folder with the new version to be tested using git subtree command 
    git subtree pull --prefix vivaplus https://openvt.eu/fem/viva/vivaplus.git release-branch-name --squash
    Change release-branch-name to the branch that needs to be tests