Update release documentation for DWDS, Webdev and the Dart Debug Extension (#2275)

Author: elliette

dwds/CONTRIBUTING.md

@@ -67,37 +67,31 @@ the example app and connect to DWDS.
 - If DWDS / Webdev was just released, then you will need to update the version
   in the `CHANGELOG`, and the `pubspec.yaml` file as well (eg,
   https://github.com/dart-lang/webdev/pull/1462)
-- For any directories you’ve touched, run `dart run build_runner build` to 
+- For any directories you’ve touched, run `dart run build_runner build` to
   check in any file that should be built. This will make sure the integration
   tests are run against the built files.
 
-## Release steps
-
-### Step 1: Roll DWDS into g3
+## g3 Rolls
 
-> _NOTE: You must be a Googler to do this step. If you are not, please ask
-> someone for help._
+DWDS is rolled automatically into g3 along with the Dart SDK. For more information, or to learn how to handle breaking changes, see go/roll-dwds.
 
-- See directions at: go/roll-dwds
-- Wait a few days after rolling into g3 before continuing to step 2. We do so to
-  have time to catch new bugs internally before publishing externally. Look for
-  any new exceptions at go/ddt-web-dashboard
+## Release steps
 
-## Step 2: Publish DWDS to pub
+## Step 1: Publish DWDS to pub
 
 - From the `/tool` directory in the mono-repo root, run: `dart run release.dart -p dwds`
 - Submit a PR with those changes (example PR: https://github.com/dart-lang/webdev/pull/1456)
 - Once the PR is submitted, go to https://github.com/dart-lang/webdev/releases and create a new
   release, eg https://github.com/dart-lang/webdev/releases/tag/dwds-v12.0.0. This should trigger
   the auto-publisher. Verify that the package is published.
-- From the `/tool` directory in the mono-repo root, run: `dart run release.dart --reset -p dwds`
+- From the `/tool` directory in the mono-repo root, run: `dart run release.dart --reset -p dwds -v <<new version tag>>` where the new version tag is the next minor version postfixed with `-wip` ([example PR](https://github.com/dart-lang/webdev/pull/2267/files))
 - Submit a PR with those changes.
 
 > _Note: To have the right permissions for publishing, you need to be invited to
 > the tools.dart.dev. A member of the Dart team should be able to add you at
 > https://pub.dev/publishers/tools.dart.dev/admin._
 
-## Step 3: Publish Webdev to pub
+## Step 2: Publish Webdev to pub
 
 > _Note: DWDS is a dependency of Webdev, which is why DWDS must be published
 > before Webdev can be published._

dwds/debug_extension_mv3/CONTRIBUTING.md

@@ -1,9 +1,7 @@
 ## Building
 
-> Note: First make the script executable: `chmod +x tool/build_extension.sh`
-
-- For development: `./tool/build_extension.sh`
-- For release: `./tool/build_extension.sh prod`
+- For development: `dart run tool/build_extension.dart`
+- For release: ` dart run tool/build_extension.dart --prod`
 
 The dart2js-compiled extension will be located in the `/compiled` directory.
 
@@ -37,7 +35,7 @@ The dart2js-compiled extension will be located in the `/compiled` directory.
 
 ## Release process
 
-- Update the version in `web/manifest.json`, `pubspec.yaml`, and in the
+- Update the version in `web/manifest_mv2.json`, `web/manifest_mv3.json`, `pubspec.yaml`, and in the
   `CHANGELOG`.
 - Follow the instructions above to build the release version of the extension.
 
@@ -53,20 +51,20 @@ The dart2js-compiled extension will be located in the `/compiled` directory.
 - Rename the zip `version_XX.XX.XX.zip` (eg, `version_1.24.0.zip`) and add it to
   the go/dart-debug-extension-zips folder
 
-> *You must be a Googler to do this. Ask for help if not.*
+> _You must be a Googler to do this. Ask for help if not._
 
 - Go to the
   [Chrome Web Store Developer Dashboard](https://chrome.google.com/webstore/devconsole).
 - At the top-right, under Publisher, select dart-bat.
 
-> *If you don’t see dart-bat as an option, you will need someone on the Dart
-> team to add you to the dart-bat Google group.*
+> _If you don’t see dart-bat as an option, you will need someone on the Dart
+> team to add you to the dart-bat Google group._
 
 - Under Items, select the "Dart Debug Extension".
 - Go to “Package” then select “Upload new package”.
 
-> *The first time you do this, you will be asked to pay a $5 registration fee.
-> The registration fee can be expensed.*
+> _The first time you do this, you will be asked to pay a $5 registration fee.
+> The registration fee can be expensed._
 
 - Upload the zip file you created in step 4.
 - Save as draft, and verify that the new version is correct.
@@ -83,7 +81,7 @@ The dart2js-compiled extension will be located in the `/compiled` directory.
 - Find the previous version you want to rollback to in the
   go/dart-debug-extension-zips folder.
 
-> *You must be a Googler to do this. Ask for help if not.*
+> _You must be a Googler to do this. Ask for help if not._
 
 - Unzip the version you have chosen, and in `manifest.json` edit the version
   number to be the next sequential version after the current "bad" version (eg,

webdev/CONTRIBUTING.md

@@ -9,5 +9,5 @@
 - Once the PR is submitted, go to https://github.com/dart-lang/webdev/releases and create a new
   release, eg https://github.com/dart-lang/webdev/releases/tag/webdev-3.0.0. This should trigger
   the auto-publisher. Verify that the package is published.
-- From the `/tool` directory in the mono-repo root, run: `dart run release.dart --reset -p webdev`
+- From the `/tool` directory in the mono-repo root, run: `dart run release.dart --reset -p webdev -v <<new version of webdev>>`
 - Submit a PR with those changes.