💻
ATD Data & Technology Services Wiki
  • About
  • Essential Resources & Wikis
  • DTS Offices
    • Where to Eat Near Cameron Rd
  • Basics
    • Working at DTS Basics
    • Network Access
    • Document Storage
      • Using Google as a City Employee
    • Working Remotely from a Mac
      • Resetting Your Network Password from a Mac
      • Troubleshooting AnyConnect for macOS Catalina
    • Slack
  • Onboarding
    • Team Lead Checklist for New Employees
    • Welcome to DTS
  • Working at DTS
  • Off boarding
    • Your Last Day
    • Offboarding Checklist
  • Product Ops
    • Agile Project Management with GitHub + Zenhub
    • Project Delivery Workflow
    • Index Issue Specifications
    • DTS Website Management
    • Release Process
    • Product Manager Assignments
  • Developer
    • Dockless-Mobility
    • Docker
    • PostgREST
      • Pypgrest (Python Client)
      • Jobs-API
    • Python
    • Server Operation
  • APPLICATIONS
    • Application Management
  • Product Manager Portfolios
Powered by GitBook
On this page
Export as PDF
  1. Product Ops

Release Process

PreviousDTS Website ManagementNextDockless-Mobility

Last updated 1 year ago

This is the general process we use to release new code to one of our custom applications. The Apps team has defined a separate, specialized .

  • The Product Manager & Dev Lead collaboratively plan what issues will be included in the release

  • The Dev Lead ensures that all issues are assigned, completed, and tested before the release

  • After a pull request is reviewed by several devs, the PM reviews and adds any new functionality to the QA test script

  • The Dev Lead creates a single pull request that includes the scope of the release Example:

  • The Dev Lead cleans up release notes Example:

  • The release branch is deployed to Staging and the PM performs QA testing

  • The PM notifies users of scheduled downtime

  • Release party 🎉

    • PM merges pull request

    • Dev Lead notifies #atd-dev that the pull request has been tested, approved, and merged

    • PM sends release notes to stakeholders and users

    • Team debriefs on the process and updates the steps as needed

    • Dev Lead creates an issue for the next release

Application-specific versions of this process are written as issues so they can be tracked collaboratively for each release. Example:

process for deploying custom code in Knack
https://github.com/cityofaustin/atd-vz-data/pull/496
https://github.com/cityofaustin/atd-vz-data/releases
https://github.com/cityofaustin/atd-data-tech/issues/16094