DP-9485 Mayflower release process v2 (#47)

* changes per a release yesterday

* added DP-9017 to 5.29.0 release notes

* removed the DP-9017.txt from the following path

patternlab/styleguide/source/_patterns/03-organisms/by-template/DP-9017.txt

* add link to document

* minor changes

CHANGELOG.md

@@ -34,6 +34,7 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
 
 ### Added
 - DP-9146/DP-8825: Adds teaser listing group organism to apply accordion behavior to multiple teaser listings at once.
+- DP-9017: Image placement on Guide pages using focal point.
 
 ### Changed
 - DP-9243: MF fix info details to show contact and related in sidebar as well as bottom on desktop.

patternlab/docs/release.md

@@ -11,20 +11,20 @@ Mayflower release managers with the necessary repo permissions can follow these
     1. `git checkout develop`
     1. Pull the latest from upstream `git pull <remote> develop`.
     1. Run `npm install`
-1. Create a release branch
+1. Create a release branch (at Noontime every Wednesday)
     1. `git checkout -b release-#.#.#` where `#.#.#` is the next version (i.e. `5.0.0`).  Read more about [Mayflower and semantic versioning](/docs/for-developers/versioning.md) to ensure that your are creating the right type of version.
     1. Add [change logs](https://github.com/massgov/mayflower/tree/develop/changelogs) to the top of [CHANGELOG.md](../CHANGELOG.md) based on the "changelog.txt" files, remove all the "changelog.txt" files and then commit these changes.
     1. Run `npm install` in case the release includes new packages.
-    1. Update the version of the npm package by editing the `version` field in the `package.json` with `#.#.#` for the release.
+    1. Update the version of the npm package by editing the `"version":` field in the following path `patternlab/styleguide/package.json` with `#.#.#` for the release.
     1. Commit your version change from `package.json`.
     1. Push release branch to `massgov/mayflower` (i.e. `git push <remote> release-#.#.#`).
 
 ## Deployment  
 1. Wait for [the circle build](https://circleci.com/gh/massgov/mayflower) to pass, which will deploy your release branch to staging automagically :).
 1. Verify release notes against the site rendered at: `https://mayflower.digital.mass.gov/b/<your-release-branch>/index.html`.
 1. Smoke test Mayflower (a quick way to do this is to browse around to some of the different pages in the "pages" menu and do a quick gut check)
-1. Open a Github Pull Request to merge (no squash!) the release branch into the `master` branch.
-    1. Add the relevant release notes to the PR notes.
+1. Open a Github Pull Request to merge (no squash!) the release branch into the `master` branch. To merge the release branch into `master` branch you will need a peer to review and approve the Pull Request. 
+    1. Add the [CHANGELOG.md](../CHANGELOG.md) to the Pull Request.
     1. This is a great time to verify one more time that your release [is following semantic versioning](/docs/for-developers/versioning.md) properly (i.e. not pushing out breaking changes in a minor release).
 
 ## Create a tag
@@ -38,10 +38,10 @@ Mayflower release managers with the necessary repo permissions can follow these
     - Make sure the home page reflects the date and version
 
 ## Post Deployment
-1. Open a GitHub Pull Request to merge `master` into `develop` (this should only bring an updated `CHANGLOG.md`, `package.json`). If a feature was reverted on the release branch, have a peer do the merge after a review.
+1. Open a GitHub Pull Request to merge `master` into `develop` (this should only bring an updated `CHANGLOG.md`, `package.json`). You will need to have a peer review the Pull Request before merge (no squash!) into the `develop` branch.
 1. In JIRA Go to the [DP project](https://jira.mass.gov/projects/DP/).
     1. Click on the Releases icon on the left side (it looks like a boat/ship).
     1. Add a new release version with today's date.
     1. Go to each shipped JIRA issue and update the Fix Version/s field.
-    1. Go to the list of issues contained within the release version and copy the URL (link to this issue from release notes).
+1. Next steps in pulling the Mayflower tag into the Mass repository is documented within the [Updating the Mayflower Version](https://github.com/massgov/mass/wiki/Updating-the-Mayflower-Version).
 1. Celebrate!!