> For the complete documentation index, see [llms.txt](https://atd-dts.gitbook.io/moped-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atd-dts.gitbook.io/moped-documentation/product-management/release-process.md). # Release process Follow these steps to release Moped. You can also review our past [release issues](https://github.com/cityofaustin/atd-data-tech/issues/29398) or see below, which can be used as a template for each release. These can be split up amongst members of the team. Schedule a recurring "release party" for product management + devs to deploy the release to production "live" as a group. * Advise users of downtime using the [email template](https://docs.google.com/document/d/1hpBIx41mttSF6-XgeFuxnJPsK7dfpok97O08oytThnc/edit#heading=h.51j00pz8giuz). If downtime is expected, let users know ahead of time that Moped will be unavailable. There is currently no mechanism to prevent users from using the system during a release window. You just have to ask nicely that people don't use Moped. * Advise Data Science team of changes to database views connected through the Power BI dataflow. **Removing columns that the dataflow expects will break the dataflow** and **column additions require rebuilding the connection** (requires rebuild for the dataflow to know about new column but won't break the dataflow). See [integrations docs](/moped-documentation/product-management/integrations.md) for more information. * Merge open pull requests into the `main` branch * Propose + vote on release names ([in Slack thread](https://austininnovation.slack.com/archives/CNUEPKLB1/p1784129053172749)) * Cut the release candidate branch from `main` that includes the version bump * Add/update tests to a new sheet in the [Moped QA Testing](https://docs.google.com/spreadsheets/d/1n_O6MLh9cwwPf57HUM394Ea-z9uuoEV1-QW4axNZXLE/edit?gid=1099176671#gid=1099176671) spreadsheet and perform QA testing * Polish the [release notes](https://github.com/cityofaustin/atd-moped/releases) * Let users know maintenance is starting * Create a DB snapshot in AWS RDS (just to be safe) * Apply any Hasura GraphQL Engine version bumps, as needed, to the ECS Fargate deployments. We endeavor to keep production at the second-most-recent minor version, with staging and local dev on the most current minor version of Hasura that's available. We now do this through a [GitHub Action workflow](https://github.com/cityofaustin/atd-moped/blob/main/.github/workflows/migrations-metadata-deployment.yml) and [PR the changes](https://github.com/cityofaustin/atd-moped/pull/1896). * Merge the release candidate to `production` branch * Create an issue for the next release * Send release notes to all Moped users highlighting notable features and optionally including screenshots ### Example Release Issue *