Release Rosters
The Release Roster is maintained on Confluence
Determining Responsibility
Who releases which services is determined based on which services need releasing, which Set they are from, and the order in which the devs are listed in the Roster.
Starting with the first dev of the release date’s roster, assign the first service from Set 1, then follow up with the second dev rostered and the first service from Set 2. Continue assigning all the services in this manner until one set has no more services to be released, then alternate assigning the remaining services - the order the services are listed should be based on the number of tickets in the release.
| Release Set | Service Name | Standard Release Process |
|---|---|---|
| Set 1 | bc-backend | No |
| Set 1 | ordering-svc | No |
| Set 1 | salesforce-svc | Yes |
| Set 1 | telstra-svc | No |
| Set 1 | website-backend | No |
| Set 1 | wholesale-svc | Maybe |
| Set 1 | zendesk-svc | No |
| Set 2 | provisioning-svc | Yes |
| Set 2 | prvidr-svc | Maybe |
| Set 2 | sq-svc | Yes |
| Set 2 | nbn-svc | Yes |
| Set 2 | notification-svc | Yes |
| Set 2 | billing-svc | Yes |
| Set 2 | mobile-svc | Yes |
Assignment Example
The current release roster lists Jason on Set 1 and Kenny on Set 2, and the services to be released are:
- bc-backend with 8 tickets
- salesforce-svc with 1 ticket
- provisioning-svc with 5 tickets
- nbn-svc with 3 tickets
- billing-svc with 2 tickets
- sq-svc with 2 tickets
Steps:
- Jason would be assigned bc-backend, Kenny would be assigned provisioning-svc.
- Next Jason would be assigned salesforce-svc and Kenny would be assigned nbn-svc.
- Now, with no more services from Set 1 Jason would be assigned the next service - billing-svc and Kenny would be assigned sq-svc.
Results:
- Each developer has 3 services to release
- Jason would be releasing 11 tickets across bc-backend, salesforce-svc, and billing-svc
- Kenny would be releasing 10 tickets across provisioning-svc, nbn-svc, and sq-svc