An exercise for learning the git-flow branching model. This exercise will walk your team through a full release cycle for an example application.

The print magazine Flavor has asked your firm to build and maintain an app so they can share recipes with their hungry audience.

The typical development cycle for the project is as follows:

• On the 1st of every month, your team receives a list of each writer's pick for recipe of the month.
• On the 15th of every month, the new version of the app is pushed to a staging server where the magazine's editors can do a final review.
• On the last day of the month, the new version of the app is pushed to production.

Development for this project began in January. It is now the beginning of February and the development cycle for v1.1 of the app has begun.

Your team will be split between Developers and one or more Maintainers. Maintainers will be responsible for cutting new releases and accepting Pull Requests from other team members. Maintainers should have write access to this repository and Developers should have read access.

Please leave this repository open in a browser tab so that you can follow along with the activities without referring to the presenter's screen.

• Application code can be found in the /app/ folder.
• The application contains a file named VERSION that contains the major, minor, and patch numbers for the project.
• Source files are written in markdown and can be identified by the .md file extension.

Next we will walk through the process of creating a GitHub Fork and local clone of this repository.

Go

• 1. Setup
• 2. Feature Branches
• 3. Code Review
• 4. Fetching Latest
• 5. Hotfix
• 6. Release Branch
• 7. Release Bugs
• 8. Completed Release