DAOS-19447 cq: overhaul jira_query.py - #18835
Conversation
|
Ticket title is 'Update JIRA Query GitHub Action to handle current DAOS Versions' |
7ef0385 to
101e7dc
Compare
276b0db to
28d1043
Compare
- Use ArgumentParser for proper argument parsing - Remove "priority" handling since this was incomplete and not easy to determine programatically. - Handle generic DAOS versions by parsing the VERSION file and Jira fields - Set/remove release-* labels on a best-effort basis - Set/remove approved-to-merge labels Doc-only: true Signed-off-by: Dalton Bohning <dalton.bohning@hpe.com>
28d1043 to
2b61723
Compare
|
The jira_query GHA is written in such a way that it runs with the workflow file from the TARGET branch, not the PR branch. So it can't be tested directly. I have a separate commit here where it ran and added the release-3.0.0 label to this PR: Overall, we will have to land this and then watch it to make sure it is behaving as expected. |
| version_minor += 1 | ||
| version_patch = 0 | ||
|
|
||
| # If the minor version is at 10, bump the major version and reset the minor version to 0. |
There was a problem hiding this comment.
Why do we want to do this?
There was a problem hiding this comment.
Because, e.g., version 2.9.x is what will become release 3.0.0
There was a problem hiding this comment.
So
2.9 -> 2.10 -> 3.0
It's a consequence of our complicated versioning system
2 participants
Doc-only: true
Steps for the author:
After all prior steps are complete: