Maintainer's Guide

Creating a Release

1. create a github issue documenting significant release changes; review the commit log and closed issues to find them

This issue is to document functionality and features added to PUMI since the #.#.# release (SHA1):

 - <feature> (SHA1,issueNumber)
 - <otherfeature> (SHA1,issueNumber)

2. apply the issue/PR tag 'v#.#.#' to significant issues and PR that are part of the release
3. increase the pumi version # in CMakeLists.txt in the develop branch
4. commit; include the issue # in the commit message
5. push
6. create the tag git tag -a v#.#.# -m "PUMI version #.#.#"
7. push the tag git push origin v#.#.#

Updating the spack version

1. Create a branch of spack develop

git checkout develop
git checkout -b pumi#### 

2. Edit pumi/package.py and be sure to change both the

• version number and
• commit hash

3. As of spack 0.15.4 the following script will build and install pumi:

#!/bin/bash -x
date=`date +%F-%H-%M`
pumiSpackDir=$HOME/pumiSpack_${date}
mkdir -p $pumiSpackDir
cd $pumiSpackDir
git clone -b pumi224 https://github.com/SCOREC/spack.git
cd spack
export SPACK_ROOT=$PWD
source $SPACK_ROOT/share/spack/setup-env.sh
which spack # sanity check

#yaml files
spack external find --not-buildable --scope site

# setup scratch space for spack
spackScratch=$pumiSpackDir/spack_scratch
mkdir -p $spackScratch
(
cat <<APPEND_HEREDOC
config:
  build_stage:
   - \$tempdir/\$user/spack-stage
   - $spackScratch
   - ~/.spack/stage
APPEND_HEREDOC
) >> $SPACK_ROOT/etc/spack/config.yaml

spec="pumi" 
spack spec -I $spec
spack install $spec

4. Push the branch to SCOREC/spack and create a PR to Spack develop.