Skip to content

Fix documentation typos #1323

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dcalhoun merged 3 commits into from
Feb 26, 2021
Merged

Fix documentation typos #1323

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b7c2297
Fix documentation typos
dcalhoun Feb 22, 2021
a4d3e6f
Fix documentation typo
dcalhoun Feb 25, 2021
c915400
Add note about CI check failures and pod publishing
dcalhoun Feb 25, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions Documentation/ReleaseProcess.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Open a PR on github where you target the `trunk` branch with the `release/x.y.z`

### Step 2: Testing the Integration ###

Before going any further, tt's normally good practice to test the Aztec integration into [WordPress-iOS project](https://github.com/wordpress-mobile/WordPress-iOS), to make sure we won’t have to do the release process twice.
Before going any further, it's normally good practice to test the Aztec integration into [WordPress-iOS project](https://github.com/wordpress-mobile/WordPress-iOS), to make sure we won’t have to do the release process twice.

Make sure WordPress-iOS’s podfile specifies the SAME (and latest) commit number for both of these:
```
Expand All @@ -59,13 +59,13 @@ Create a new release on Github targetting the trunk branch and name it `Release

Set a tag with the value `x.y.z` .

On the description field and the content of the changelog for this version
On the description field add the content of the changelog for this version

Press the `Publish release` button

At this moment the CI automation should notice your tag and after some minutes you should get the new pod publish on CocoaPods.

If this for some reason fails chech the manual process bellow
If this for some reason fails check the manual process below. Also note that the CI checks for a merged release PR can sometimes fail if the checks run prior to CocoaPods populating the new version through the CDN. Waiting a little while (e.g. 30-60 minutes) and rerunning the CI checks can sometimes repair the checks.

*Manual Process*

Expand Down