Dev process

The following outlines the dev process from creating to releasing features.

On this page:

• 🔄️ Issue lifecycle
• 📋 Triaging issues
• 🔄️ Pull request lifecycle

---

🔄️ Issue lifecycle

1. Author creates new issue

   Assign to reviewer
   ➕ Needs: Triage 🔍
   

2. Reviewer notes issue is a duplicate with #duplicate in a comment

   ➖ Needs: Triage 🔍
   ➕ Resolution: Duplicate
   

   1. If no updates after 7d...

      Close issue
      

3. Reviewer asks author for details with #needs-info in a comment

   Assign to author
   ➖ Needs: Triage 🔍
   ➕ Needs: Information
   

   1. If no updates after 14d...

      ➕ Needs: Attention 👋
      

   2. If no updates after 28d...

      Close issue
      ➕ Resolution: No activity
      

   3. If updated within 35d...

      Reopen issue
      ➖ Needs: Information
      ➖ Needs: Attention 👋
      ➖ Resolution: No activity
      ➕ Needs: Triage 🔍
      

4. Author adds details in comment

   Assign to PM
   ➖ Needs: Information
   ➕ Needs: Triage 🔍
   

5. Reviewer approves with #approved in a comment

   Remove assignee
   ➖ Needs: Triage 🔍
   

6. Reviewer assigned ➕ Status: ✍️ Spec in progress
7. Reviewer creates "Spec review:" PR

   ➖ Status: ✍️ Spec in progress
   ➕ Status: 🔭 Spec review
   

8. "Spec review:" PR closes

   ➖ Status: 🔭 Spec review
   ➕ Status: ▶️ Ready
   

9. Dev assigned

   ➖ Status: ▶️ Ready
   ➕ Status: 🔄️ In progress
   

10. Dev creates PR

    ➖ Status: 🔄️ In progress
    ➕ Status: 🔬 Code review
    

11. PR closes linked issue

    ➖ Status: 🔬 Code review
    ➕ Status: 📦 Pending release
    

12. Issue included in a release

    ➖ Status: 📦 Pending release
    ➕ Status: ✅ Released
    

📋 Triaging issues

The goal of triaging is to ensure issues in the backlog are valid and have the necessary details for someone to start working on them. The following rules apply for triaging all issues:

• Each issue should only have one Type: * label. Do not assign a t ype for simple change requests.
• Add applicable Area: * labels by leaving #ARM, #ADF, and/or #PBI comments.
• Do not assign issues to anyone unless they are actively working on the issue.
• Only assign milestones when proposing work for a near-term release.
  • Use the vNext milestone for stretch work.
• If you do not have enough details to triage the issue, leave a #needs-info comment and message for the author.
• Add the Good first issue label if it's a good task for someone new to the project.
  • Good first issues should only contain one small change that can be contributed independently.
  • If you feel an issue needs more details for a newcomer to pick it up, add the Needs: Information label and assign it to a dev to provide details.
• After triaging, add an #approved comment and thank the author.
• Don't be afraid to say no, or close issues. Just explain why and be polite.
• Don't be afraid to be wrong. Just be flexible when new information appears.
• Explicitly @mention relevant users when you think the issue needs their attention.

🔄️ Pull request lifecycle

1. Author creates new PR against main branch

   Assign to author
   Leave comment about no PRs to main policy
   ➕ Status: ⛔ Blocked
   ➕ Needs: Attention 👋
   

   1. If no updates after 7d...

      Close issue
      

2. Author creates new PR

   Assign to reviewer
   ➕ Needs: Review 👀
   

3. Reviewer requests changes

   Assign to author
   ➕ Needs: Attention 👋
   

   1. If no updates after 28d...

      Leave comment about needing to update
      ➕ Resolution: No activity
      

   2. If no updates after 56d...

      Leave comment about closing due to no activity
      Close issue
      

   3. If updated within 70d...

      Reopen PR
      ➖ Needs: Attention 👋
      ➖ Resolution: No activity
      

4. Author responds with a comment or pushes changes to the PR
   • Can we check to see if there are pending comments?

     Remove author as assignee
     ➖ Needs: Attention 👋
     

   1. If no updates after 28d...

      Leave comment about needing to update
      ➕ Needs: Attention 👋
      ➕ Resolution: No activity
      

   2. If no updates after 56d...

      Leave comment about closing due to no activity
      Close issue
      

   3. If updated within 70d...

      Reopen issue
      ➖ Needs: Attention 👋
      ➖ Resolution: No activity
      

5. Reviewer approves

   Assign to author
   ➕ Status: ▶️ Ready
   ➖ Needs: Attention 👋
   

   1. If no updates after 28d...

      Leave comment about needing to update
      ➕ Resolution: No activity
      

   2. If no updates after 56d...

      Leave comment about closing due to no activity
      Close issue
      

   3. If updated within 70d...

      Reopen issue
      ➖ Needs: Attention 👋
      ➖ Resolution: No activity