Created Partner Release Process (markdown)

Partner-Release-Process.md

@@ -0,0 +1,9 @@
+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 relevants versions using `eng/scripts/version.py update <old_version> <new_version> <MODULE>`. Ensure the PR branch is off the main repo and not a fork. Use the branch name `<MODULE>_<version>`. Naming the branch in this way allows you to use the `tag` parameter in files before actually creating the tag in Github.
+1. Do a fresh `pod install` of the `AzureSDKSmokeTest` project and verify that it builds without any errors. Set the PODSPEC_BRANCH to the release branch before running `pod install`. You should test installation with the environment variable POD_LINKAGE set to "dynamic" and "staticframework".
+1. Merge the PR and tag the master branch with a release tag in the format `<MODULE>_<version>`. You will likely need to delete the branch with the same name. If releasing multiple package, create one tag per released package.
+1. In each mirror repo, named `SwiftPM_<packageName>`, sync the mirror with the mono-repo using `eng/scripts/sync_repo.py <MODULE>` and tag with `<version>`. This completes the SwiftPM 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).
+1. Draft PR to publish release notes in the AzureSDK repo.