-
Notifications
You must be signed in to change notification settings - Fork 2
Creating a new release
All development should occur in the develop branch. When you're ready to create a new release, follow these instructions starting from the develop branch.
From the develop branch, create a new release branch labeled release/VERSIONNUMBERHERE. An example would be release/2.0.0. Add the new version to package.json, run grunt version, and add a section in CHANGELOG.md describing changes introduced by this release.
The following files should show changes:
- CHANGELOG.md
- package.json
Stage all changes and commit using "Version bump to x.x.x" as the commit message.
You'll need to get a final set of eyes for review before closing the pull request and finalizing the release. Once you do, go ahead and merge.
Head to the releases page (https://github.com/bu-ist/responsive-foundation/releases/). Draft a new release, and add your release number and choose master as the target branch. Describe the release and add items from CHANGELOG.md in the description.
Pull to update main now in Tower. Then, in the left panel under "Branches" checkout the develop branch and then click and drag main on top of develop to merge. Make sure that "Always generate a merge commit" is checked. Push these changes.
The main branch of Responsive Framework should always point to the latest stable tag of Foundation.
Follow the instructions in the Framework wiki to create a new Framework release.
Also be sure to update the Responsive Child Starter theme that new themes always start with the latest version of Foundation. (No special release workflow there; just update package.json to reference the new tag, run npm install, commit and push).
Paste the release link in Slack (#id-product-updates) with a summary of notes (e.g. https://github.com/bu-ist/responsive-foundation/releases/tag/1.0.1).