Skip to content

Commit 603d4f6

Browse files
committed
Merge branch 'master' of https://github.com/Azure/azure-sdk-for-python into add_decorator
2 parents 91d1d25 + 1dd0602 commit 603d4f6

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

doc/dev/release.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,17 @@ Python packages are uploaded to [PyPI](https://pypi.org/). Once you've uploaded
1616

1717
### Production - Deploy with Azure Dev Ops
1818

19-
Go to this Url: https://aka.ms/pysdkrelease
19+
To avoid "accidental" pushes to our target repositories, [approval](https://docs.microsoft.com/en-us/azure/devops/pipelines/release/approvals/approvals?view=azure-devops) will be requested directly prior to the final PyPI publish. Reference this [wiki page](https://aka.ms/python-approval-groups) and click on `Release to PyPI Approvers` to add yourself to the group for PyPI publishing.
20+
21+
After taking care of the above, go to this Url: https://aka.ms/pysdkrelease
2022

2123
- Click on "Run pipeline"
2224
- Change "BuildTargetingString" to the name of your package. Example: azure-mgmt-compute
2325
- Change "CandidateForRelease" value to `True` (it should be defaulted to `False`)
2426

25-
Et voila :). Azure Dev Ops will tests one last time the package, dependencies, and the distributions (sdist/wheel) and push to PyPI using the user [azure-sdk](https://pypi.org/user/azure-sdk/).
27+
Et voila :). Azure Dev Ops will tests one last time the package, dependencies, and the distributions (sdist/wheel) and ask for approval prior to pushing to PyPI using the user [azure-sdk](https://pypi.org/user/azure-sdk/).
28+
29+
Validate artifacts prior to clicking `approve` on the pre-deployment confirmation mail waiting in your inbox. Please allow ~5 minutes for the email to be sent by Azure DevOps
2630

2731
### Production - Deploy manually
2832

0 commit comments

Comments
 (0)