Update out of date content for release doc (#42962)

* Revise management package release process details

Updated release process steps and corrected file references.

* Update mgmt_release.md

Author: ChenxiJiang333

doc/dev/mgmt/mgmt_release.md

@@ -2,16 +2,16 @@
 
 ## General Release Process Overview
 
-Once Swagger PR is merged, SDK automation will create pull request to Azure SDK for Python repository, and here are steps that you need to do in order to release a new package:
+Once Swagger PR is merged and a release plan/request is submitted, here are steps that you need to do in order to release a new package:
 
-- open PR that was merged in swagger repository and find the link to the PR createted in Azure SDK for Python
-- reopen generated SDK PR and make sure the CI passes
+- create SDK pull request with code generation
+- identify and resolve breaking changes
 - verify that generated code was generated correctly, make sure right version was generated with right configuration
+- verify the release notes match actual changes (CHANGELOG.md)
+- verify the version accordingly to changes that were made (_version.py)
+- generate samples and develop tests
+- make sure the CI passes
 - merge the PR if everything looks good
-- create another PR manually in order to add release notest and update version (this is currently not done by automation)
-- generate release notes as described below, verify they match actual changes (HISTORY.rst)
-- update version accordingly to changes that were made (version.py)
-- merge the PR
 - run release pipeline
 
 Once you have a PR that contains accurate with correct tests (or no tests at all, but CI is green), this page explains how to prepare for a release.
@@ -20,8 +20,8 @@ IMPORTANT NOTE: All the commands in this page assumes you have loaded the [dev_s
 
 ## Manual generation
 
-If the automation is not doing its job to create an auto PR, Python has a SwaggerToSdk CLI that can be used to generate a specific Readme. You need
-a virtual environment loaded with at least `eng/tools/azure-sdk-tools` installed.
+If the automation is not doing its job to create an auto PR, Python has a SwaggerToSdk CLI that can be used to generate SDK by a specific Readme. You need
+a virtual environment loaded with at least `eng/tools/azure-sdk-tools` installed. And to manually create a package from Typespec, here's the full direction https://github.com/Azure/azure-sdk-for-python/wiki/Generate-Python-Mgmt-SDK-from-Typespec.
 
 ```shell
 # Using default configuration (this can be a Github raw link)
@@ -43,16 +43,16 @@ If not, you can execute this command (replace the last part by your package name
 python -m packaging_tools --build-conf azure-mgmt-web
 ```
 
-If the file sdk_packaging.toml didn't exist, now one is created with default values. Update this file and update the default values to the one from this service. Once it's done, restart the same script.
+If the file pyproject.toml didn't exist, now one is created with default values. Update this file and update the default values to the one from this service. Once it's done, restart the same script.
 
 Your packaging info are up-to-date
 
 ## Building the ChangeLog
 
-For all packages, you need to update the `HISTORY.rst` file
+For all packages, you need to update the `CHANGELOG.md` file
 
 ```
-/azure-mgmt-myservice/HISTORY.rst
+/azure-mgmt-myservice/CHANGELOG.md
 ```
 
 For all **autorest generated packages**, there is a tool that allows you to auto-build the ChangeLog.
@@ -71,17 +71,17 @@ python -m packaging_tools.code_report --last-pypi azure-mgmt-trafficmanager
 Output will look like this:
 ```shell
 INFO:__main__:Download versions of azure-mgmt-trafficmanager on PyPI
-INFO:__main__:Got ['0.30.0rc5', '0.30.0rc6', '0.30.0', '0.40.0', '0.50.0', '0.51.0']
+INFO:__main__:Got ['0.30.0rc5', '0.30.0rc6', '0.30.0', '0.40.0', '0.50.0', '0.51.0', '1.0.0b1', '1.0.0', '1.1.0b1', '1.1.0']
 INFO:__main__:Only keep last PyPI version
-INFO:__main__:Installing version 0.51.0 of azure-mgmt-trafficmanager in a venv
+INFO:__main__:Installing version 1.1.0 of azure-mgmt-trafficmanager in a venv
 INFO:__main__:Looking for Autorest generated package in azure.mgmt.trafficmanager
 INFO:__main__:Found azure.mgmt.trafficmanager
 INFO:__main__:Working on azure.mgmt.trafficmanager
-INFO:__main__:Report written to sdk/trafficmanager/azure-mgmt-trafficmanager/code_reports/0.51.0/report.json
+INFO:__main__:Report written to sdk\trafficmanager\azure-mgmt-trafficmanager\code_reports\1.1.0\report.json
 ```
 
 Note the output path of the report:
-`sdk/trafficmanager/azure-mgmt-trafficmanager/code_reports/0.51.0/report.json`
+`sdk\trafficmanager\azure-mgmt-trafficmanager\code_reports\1.1.0\report.json`
 
 #### Build the report from the current code.
 
@@ -112,10 +112,10 @@ Note the output path of the report:
 
 You call the changelog tool with these report as input:
 ```shell
-python -m packaging_tools.change_log sdk/trafficmanager/azure-mgmt-trafficmanager/code_reports/0.51.0/report.json sdk/trafficmanager/azure-mgmt-trafficmanager/code_reports/latest/report.json
+python -m packaging_tools.change_log sdk\trafficmanager\azure-mgmt-trafficmanager\code_reports\1.1.0\report.json sdk/trafficmanager/azure-mgmt-trafficmanager/code_reports/latest/report.json
 ```
 
-Output will Markdown syntax that you can copy/paste directly into the HISTORY.txt
+Output will Markdown syntax that you can copy/paste directly into the CHANGELOG.md
 Example:
 ```shell
 **Features**
@@ -145,13 +145,10 @@ You need to check the version in:
 
 Python SDK _strictly_ follows [semver](https://semver.org/). A few notes:
 
-- First release should always use 0.1.0, unless asked explicitly by service team
-- If a version is 0.5.2:
-  - Next breaking / feature version is 0.6.0
-  - Next bug fix is 0.5.3
+- First release should always use 1.0.0b1, unless asked explicitly by service team
 - If a version is 2.1.0:
-  - Next preview breaking is 3.0.0rc1
+  - Next preview breaking is 2.2.0b1
   - Next stable breaking is 3.0.0
-  - Next preview feature is 2.2.0rc1
+  - Next preview feature is 2.2.0b1
   - Next stable feature is 2.2.0
-  - Next patch is  2.1.1
+  - Next patch is 2.1.1