Skip to content

Commit

Permalink
Docs: release.md: miscellaneous fixes (#14083)
Browse files Browse the repository at this point in the history
* Docs: release.md: misc. fixes
  • Loading branch information
mcsf authored and youknowriad committed Mar 6, 2019
1 parent 0df536f commit ec5f282
Showing 1 changed file with 7 additions and 6 deletions.
13 changes: 7 additions & 6 deletions docs/contributors/release.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

This Repository is used to perform several types of releases. This document serves as a checklist for each one of these. It is helpful if you'd like to understand the different workflows.

To release Gutenberg, you need commit access to the [WordPress.org plugin repository]. 🙂
To release Gutenberg, you need commit access to the [WordPress.org plugin repository][plugin repository]. 🙂

## Plugin Releases

Expand Down Expand Up @@ -192,22 +192,23 @@ WordPress Core Updates are based on the `g-minor` branch. Releasing packages in

For major WordPress releases, the last Gutenberg plugin release is merged into `g-minor`. This involves the following steps:

1. Checkout the last published Gutenberg's release branch `git checkout release/x.x`
1. Check out the last published Gutenberg release branch `git checkout release/x.x`
2. Create a Pull Request from this branch into `g-minor`.
3. Merge the branch.

### Minor WordPress Releases

For minor releases, the critical fixes targetted for this WordPress Minor release should be cherry-picked into the `g-minor` branch one by one in their chronological order.
For minor releases, the critical fixes targeted for this WordPress Minor release should be cherry-picked into the `g-minor` branch one by one in their chronological order.

### Releasing the WordPress packages

1. Checkout the `g-minor` branch.
2. Run [the package release process](https://github.com/WordPress/gutenberg/blob/master/CONTRIBUTING.md#releasing-packages)
3. Update the `CHANGELOG` files of the published packages with the new released versions and commit to the `g-minor` branch.
1. Check out the `g-minor` branch.
2. Run the [package release process].
3. Update the `CHANGELOG.md` files of the published packages with the new released versions and commit to the `g-minor` branch.

---------

Ta-da! 🎉

[plugin repository]: https://plugins.trac.wordpress.org/browser/gutenberg/
[package release process]: https://github.com/WordPress/gutenberg/blob/master/packages/README.md#releasing-packages

0 comments on commit ec5f282

Please sign in to comment.