Releasing to Beta

In between major releases of the GRNsight Master, there are smaller releases of the beta branch, which is updated once the programmer submits a pull request to have their work pushed to beta after certain checkpoints are reached or goals are accomplished. The following outlines the process for preparing to release a new version of beta:

• Individually, submit a pull request and check that everything on your branch works correctly (to avoid creating bugs in beta that did not previously exist). Use the Pull Request Checklist to ensure that you don't miss key functional points
• Professor Dondi or Professor Dahlquist will review all pull requests intended for Beta and make sure they are approved
• Pull request is merged into beta on the GitHub website
• Resolve any conflicts (see instructions here)
• Once conflicts are resolved and hotfixes are made, git add, git commit, and git push are used to push the updates to beta.
• When the pending beta branch is final, edit package.json to update its version
• Next, the GRNsight server needs to be updated to the latest version (see instructions here)
• Edit gh-pages indicating new version number and revision date
• Comment on our evergreen beta issue so that the group can be notified of the new version