From b7c2297cba3ffc86af8ac26c3e3e10eda80b4708 Mon Sep 17 00:00:00 2001 From: David Calhoun Date: Mon, 22 Feb 2021 17:29:01 -0600 Subject: [PATCH 1/3] Fix documentation typos --- Documentation/ReleaseProcess.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/ReleaseProcess.md b/Documentation/ReleaseProcess.md index 38219be81..cfe75a7e9 100644 --- a/Documentation/ReleaseProcess.md +++ b/Documentation/ReleaseProcess.md @@ -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: ``` @@ -65,7 +65,7 @@ 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 *Manual Process* From a4d3e6fa28c27410a8d58156a17c2d84175f1d6c Mon Sep 17 00:00:00 2001 From: David Calhoun Date: Thu, 25 Feb 2021 10:21:09 -0600 Subject: [PATCH 2/3] Fix documentation typo --- Documentation/ReleaseProcess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/ReleaseProcess.md b/Documentation/ReleaseProcess.md index cfe75a7e9..bd74f5260 100644 --- a/Documentation/ReleaseProcess.md +++ b/Documentation/ReleaseProcess.md @@ -59,7 +59,7 @@ 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 From c915400b7116ab0fef76fede70a970c7bc66b0ad Mon Sep 17 00:00:00 2001 From: David Calhoun Date: Thu, 25 Feb 2021 12:21:15 -0600 Subject: [PATCH 3/3] Add note about CI check failures and pod publishing The merge commit for a release can suffer from failed CI checks if the check runs prior to the new version being populated in the CocoaPod CDN. --- Documentation/ReleaseProcess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/ReleaseProcess.md b/Documentation/ReleaseProcess.md index bd74f5260..cb4cf4d8c 100644 --- a/Documentation/ReleaseProcess.md +++ b/Documentation/ReleaseProcess.md @@ -65,7 +65,7 @@ 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 check the manual process below +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*