Updated Release Process (markdown)

Release-Process.md

@@ -1,7 +1,7 @@
 1. Code complete is typically the first Friday of the month. The next week is known as "Release Week".
 1. Prior to release, ensure all relevant code is checked into master and all partner teams have published any binaries they want released.
 1. Create a PR in the `azure-sdk-for-ios` repo that bumps all versions. Ensure the PR branch is off the main repo and not a cloned repo. Ensure the new version is added to the ignore-links.txt.
-1. Do a fresh `pod install` of the `AzureSDKSmokeTest` project and verify that it builds without any errors. The Podfile must target the version bump branch.
+1. Do a fresh `pod install` of the `AzureSDKSmokeTest` project and verify that it builds without any errors. The Podfile must target the version bump branch. You should test installation with the environment variable POD_LINKAGE set to "dynamic" and "staticframework".
 1. Tag the master branch with a release tag. This completes the Swift Package Manager release.
 1. [Release on CocoaPods](https://github.com/Azure/azure-sdk-for-ios/wiki/Publishing-Cocoapods).
 1. [Generate and publish the Jazzy documentation](https://github.com/Azure/azure-sdk-for-ios/wiki/Publishing-Jazzy-Docs-to-GitHub.io).