Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Epic: Change appropriate references to ready for dev lead label to ready for merge team #6784

Open
1 of 3 tasks
ExperimentsInHonesty opened this issue Apr 29, 2024 · 0 comments
Open
1 of 3 tasks

Epic: Change appropriate references to ready for dev lead label to ready for merge team #6784

ExperimentsInHonesty opened this issue Apr 29, 2024 · 0 comments
Labels
Complexity: Large Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Dependency An issue is blocking the completion or starting of another issue Draft Issue is still in the process of being created epic Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms good first issue Good for newcomers Issue Making: Level 4 Make a Rollout Plan that has >1 epics to achieve and timelines for interdependencies role: dev leads Tasks for technical leads and/or merge team members role: product Product Management size: 1pt Can be done in 4-6 hours time sensitive Needs to be worked on by a particular timeframe
Projects
Project Board
Milestone
08. Team workflow

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Apr 29, 2024 •
edited

Dependency

Overview

We need to have two ready for labels. One for the merge team and one for dev leads so that merge team can take on more work, and the lead only gets the issues they absolutely need to see.

Action Items

  • Create a ready for merge team label
  • Evaluate each item could be handled by the merge team (it's procedural, not unique, e.g., issues that have been created from a template and need to have the ready for prioritization label added, etc.. If you don't know, use the discuss value) (TRUE / FALSE, discuss)
  • Create a roll-out plan to determine in what order items need to change

Resources/Instructions
@ExperimentsInHonesty ExperimentsInHonesty added Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Apr 29, 2024
@HackforLABot HackforLABot added this to New Issue Approval in Project Board Apr 29, 2024
Closed
7 tasks
@ExperimentsInHonesty ExperimentsInHonesty added role: product Product Management Complexity: Large Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms size: 1pt Can be done in 4-6 hours role: dev leads Tasks for technical leads and/or merge team members Draft Issue is still in the process of being created Dependency An issue is blocking the completion or starting of another issue good first issue Good for newcomers epic Issue Making: Level 4 Make a Rollout Plan that has >1 epics to achieve and timelines for interdependencies Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level and removed Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing role missing Complexity: Missing labels Apr 30, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from New Issue Approval to ERs and epics that are ready to be turned into issues in Project Board Apr 30, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the time sensitive Needs to be worked on by a particular timeframe label Apr 30, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from ERs and epics that are ready to be turned into issues to Ice box in Project Board Apr 30, 2024
@ExperimentsInHonesty ExperimentsInHonesty changed the title Change label Epic: Change appropriate references to ready for dev lead label to ready for merge team Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Complexity: Large Complexity: See issue making label See the Issue Making label to understand the issue writing difficulty level Dependency An issue is blocking the completion or starting of another issue Draft Issue is still in the process of being created epic Feature: Board/GitHub Maintenance Project board maintenance that we have to do repeatedly Feature: Refactor GHA Refactoring GitHub actions to fit latest architectural norms good first issue Good for newcomers Issue Making: Level 4 Make a Rollout Plan that has >1 epics to achieve and timelines for interdependencies role: dev leads Tasks for technical leads and/or merge team members role: product Product Management size: 1pt Can be done in 4-6 hours time sensitive Needs to be worked on by a particular timeframe
Projects
Project Board
  
Ice box
Milestone
08. Team workflow
Development

No branches or pull requests
1 participant
@ExperimentsInHonesty