| Date | Phase |
|---|---|
| February 28th | Release |
It is the last day of the month and no more requests have come in from the, time to push the code to production and merge changes to the release back into the develop branch.
Maintainers
Choose a maintainer to merge release-1.1 into master.
$ git checkout release-1.1
$ git pull
$ git checkout master
$ git pull
$ git merge --no-ff release-1.1
$ git push👮 ✋ - Please wait until everyone has caught up.
🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧
Maintainers
Next we will work to get changes made to the release merged back down into develop, so switch to the release branch and pull down all the latest changes:
$ git checkout release-1.1
$ git checkout develop
$ git merge --no-ff release-1.1
$ git push💡 Always make sure that develop is up to date before merging. There may be some merge conflicts that will need to be addressed at this point.
Choose a maintainer to push the the commit up to the source repository:
$ git push source develop👮 ✋ - Please wait until everyone has caught up.
🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧 🚧
Choose a maintainer to create a Release in GitHub:
- On the source repository page, click the "# releases" link in the stats bar at the top (or append
/releasesto the repo URL). - Click new release.
- Name the release tag v1.1, choose the master branch, and document the changes comprising the release.
The release feature in GitHub is an easy way to keep track of changes associated with each release. Files may also be uploaded and attached to the release, so they can also act as a place to store any additional files related to the release that are not tracked in version control.
You did it! Feel free at this time to navigate around the source repository, yours and others' forks and reflect back on all the hard work that was done to get v1.1 out the door 😎.