development-process.md

May 3, 2024 ยท View on GitHub

Development Guidelines - Process

For cross-functional teams working on building a template, the following guidelines are recommended.

  • Create labels that reflect the different dimensions for features and operations. For example:
Label NameDescription
AIAI implementation and implementation
Infra AZDAZD related
Infra BicepInfra issues related to Bicep bugs or support
Infra TerraformInfra issues related to Terraform bugs or support
backendApplication feature backend
frontendApplication feature frontend
DocsRepo docs, guidelines, promo videos
Managed IdentitySecurity and auth
BlockedMark a task as blocked and establish dependency
DependencyEstablishes a dependency requirement

These labels can be used in addition to default labels for bug, enhancement, etc

Issues

Once the labels are in place, create issues that can be distributed and tracked to provide concise and concrete overview of progress, blockers, requests for help, etc

Assign the task to the current owner, so they can be contacted.

Use the comments in the issue to initiate a conversation, request dependecies resolution, ask for help, request clarification, etc

When applicable, use the GitHub Projects feature to track project completion.

Create relevant milestones

Create milestones that issues can be assigned to so ETA can be better established and completion progress assessed.

Collaborators

Note

For Microsoft authored samples only: collaborators should be added to a team with write access under the Azure-Samples Org