WX-1611 Cromwell 87 release: streamline release WDL, documentation (#7422)

Author: aednichols

processes/release_processes/README.MD

@@ -7,18 +7,12 @@ See our "updating the process" [process](../README.MD)!
 
 ## Core Process: How to Publish and Release Cromwell
 
-Cromwell versions are updated on a weekly cadence automatically. For more information see [here](https://support.terra.bio/hc/en-us/articles/9512163608731-Faster-Cromwell-updates-in-Terra-)
+This process is unrelated to Terra. Both GCP and Azure Terra update automatically. For more information see [here](https://support.terra.bio/hc/en-us/articles/9512163608731-Faster-Cromwell-updates-in-Terra-).
 
 Manually cutting a numeric release is expected to continue being done on a cadence of every ~6 months. If you're the lucky "Release Rotation Engineer" this time, you should do the following four things:
 
-1. Create a Jira ticket for the release (look at previous release tickets if you're not sure how). In the Suggested
-Release Notes field, add "Terra is now running Cromwell <version>" along with any other release notes relevant to Terra
-users.
-1. Check that all most recent executions of Cromwell's Jenkins tests have succeeded, and that all those executions were
-against the most recent commit in "develop" branch. There are 2 groups of Jenkins tests which have to be checked (you
-will need to be on the Broad internal network or VPN to open the following links):
-    1. Tests for various backends supported by Cromwell. Log into Jenkins [here](https://fc-jenkins.dsp-techops.broadinstitute.org), check the tests [here](https://fc-jenkins.dsp-techops.broadinstitute.org/job/cromwell-cron-parent/).
-    1. Tests for Cromwell in Terra environment. Log into Jenkins [here](https://fc-jenkins.dsp-techops.broadinstitute.org), check the tests [here](https://fc-jenkins.dsp-techops.broadinstitute.org/view/Batch/).
+1. Create a Jira ticket for the release (look at previous release tickets if you're not sure how).
+1. Check that Cromwell's [nightly integration](https://github.com/broadinstitute/cromwell/actions?query=event%3Aschedule) testing is passing.
 1. [Run the publish script to create a new version of Cromwell](#how-to-publish-a-new-cromwell-version)
 1. [Run through the "How to Deploy Cromwell in CaaS prod" process](#how-to-deploy-cromwell-in-caas-staging-and-caas-prod)
 
@@ -47,13 +41,10 @@ Make or copy the following files into a temporary `release/` directory outside t
 
 * A copy of the workflow file to run (https://github.com/broadinstitute/cromwell/blob/develop/publish/publish_workflow.wdl)
 * An inputs json like this one.
-  * `publishHomebrew` is `false` due to Homebrew taking on this part themselves. Homebrew remains an active distribution channel.
 
 ```json
 {
   "publish_workflow.githubToken": "<<GITHUB TOKEN VALUE>>",
-  "publish_workflow.majorRelease": true,
-  "publish_workflow.publishHomebrew": false,
   "publish_workflow.publishDocker": "broadinstitute/cromwell-publish:latest",
   "publish_workflow.organization": "broadinstitute"
 }
@@ -87,7 +78,7 @@ The workflow outputs its status to the console.
 * Check that the workflow succeeded.
 * Check that there's now a new Cromwell release listed [here](https://github.com/broadinstitute/cromwell/releases).
 * Let `#dsp-workflows-private` know that it's okay to resume merges to `develop`.
-* Announce release in `#dsp-workflows`, set expectations about when the new version will be available in Terra.
+* Announce release in `#dsp-workflows`, with context that it's for standalone Cromwells (the code is already in Terra).
 * **One business day later,** confirm that [the Homebrew package](https://formulae.brew.sh/formula/cromwell) has the latest version. If it doesn't, start investigation by looking at [Homebrew PR's](https://github.com/Homebrew/homebrew-core/pulls?q=is%3Apr+cromwell).
 
 ### Publish Docker Image
@@ -96,10 +87,11 @@ The workflow outputs its status to the console.
 * Run `sbt -Dproject.isSnapshot=false -Dproject.isRelease=true dockerBuildAndPush` from your local Cromwell directory. 
 * Grab a cup of coffee, and verify that all of the new images were pushed successfully. For example, you should now be able to do `docker pull broadinstitute/cromwell:{new version #}`
   * The list of images is `cromwell`, `cromiam`, `cromwell-drs-localizer`, and `womtool`
+  * Docker Hub links: [Cromwell](https://hub.docker.com/repository/docker/broadinstitute/cromwell/general), [CromIAM](https://hub.docker.com/repository/docker/broadinstitute/cromiam/general), [DRS Localizer](https://hub.docker.com/repository/docker/broadinstitute/cromwell-drs-localizer/general), [Womtool](https://hub.docker.com/repository/docker/broadinstitute/womtool/general)
 
 ### How to Deploy Cromwell in CaaS staging and CaaS prod
 
-CaaS is "Cromwell as a Service". It is used by a couple of Broad teams (Pipelines and Epigenomics), though the long-term plan is for those teams to migrate to using Terra.
+CaaS is "Cromwell as a Service". It is only used by Epigenomics, and will eventually be retired in favor of Terra.
 
 **Note:** If the Cromwell CHANGELOG indicates that the upgrade might take some time (e.g., because of a database migration), checking in with the CaaS users
 to let them know that the upgrade is about to happen is a good idea.
@@ -108,7 +100,7 @@ Deploying to CaaS is detailed in the [Quick CaaS Deployment Guide](https://docs.
 
 ### How to be Sure You're Done
 
-Don't forget to confirm that [the Homebrew package](https://formulae.brew.sh/formula/cromwell) was updated!
+Confirm that [the Homebrew package](https://formulae.brew.sh/formula/cromwell) was updated.
 
 ## Bonus Processes
 

processes/release_processes/firecloud-develop.dot

@@ -1,7 +1,5 @@
 {
   "publish_workflow.githubToken": "<<GITHUB TOKEN VALUE>>",
-  "publish_workflow.majorRelease": true,
-  "publish_workflow.publishHomebrew": false,
   "publish_workflow.publishDocker": "broadinstitute/cromwell-publish:latest",
   "publish_workflow.organization": "broadinstitute"
 }