Skip to content

Latest commit

 

History

History
35 lines (26 loc) · 1.1 KB

contributing.md

File metadata and controls

35 lines (26 loc) · 1.1 KB
Raw

Release process

  • Increment version at the top of mason
  • Increment the version in the Readme
  • Update changelog
  • Ensure tests are passing
  • Tag a release:
TAG_NAME=$(cat mason | grep MASON_RELEASED_VERSION= | cut -d '"' -f2)
git tag v${TAG_NAME} -a -m "v${TAG_NAME}" && git push --tags

Creating new packages

Tips for creating patch files

When packages need to be patched a good workflow is:

# try your build
./mason build <your package> <your version>
# if the build fails and needs patched...
cd mason_packages/.build/<your package>/
git init . && git add . && git commit -a -m "add all files"`
# edit some things fixing the build
# then dump the patch file out
git diff > ../../../scripts/<your package>/<your version>/patch.diff
# Then add the patch back to the script.sh so it is run automatically by adding something like:
# patch -N -p1 < ${MASON_DIR}/scripts/${MASON_NAME}/${MASON_VERSION}/patch.diff to your `mason_compile` step