AWS: Pull Request Priorities

This page shows which tickets should be prioritized by the Ansible AWS Working Group. See the end of the list for an explanation of how issues should be prioritized

0) Manual high priority issues

No more than 3 high priority tasks wo are working on as an agreed primary goal for the AWS Working Group. N.B. we might group together multiple pull requests as one priority task if they area all needed together.

1) Top Priority:Need Merge List

PR has gone green on CI PR has positively been reviewed and approved

2) Priority - bug fixes ready to review

3) Priority - tickets ready for community review

these tickets are a good place to start for community members since they can directly get code improvements in quickly.

Low priority - excluded from above tickets

These are generally tickets which are excluded from the above reports because their authors need to act. We need to work out how to follow these up to get author interest early in the processes.

If your ticket in this list then generally, by reading the comments in the ticket you should be able to resolve the problem and bring it back into the higher priority lists.

All tickets with Needs revision: -

Information on prioritization

Prioritisation principles

These are our current principles for prioritisation of tickets. Since we are always thin on volunteers work

work that is further into the process should get higher priority
bug fixes should get higher priority over new features
pull requests which deliver full test cases will be prioritized
pull requests without test cases will typically not be prioritized. To accelerate write test cases.
test cases come in at very high priority
features which have a clear maintainer / active engagement should get high priority.