Back to bug 2219317
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2023-07-03 08:44:58 UTC | Pool ID | sst_system_roles_rhel_9 | |
| Red Hat One Jira (issues.redhat.com) | 2023-07-03 08:45:51 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-161415 | |
| RHEL Program Management | 2023-07-03 08:46:59 UTC | Keywords | Triaged | |
| Sergei Petrosian | 2023-07-03 10:16:18 UTC | Link ID | Github linux-system-roles/auto-maintenance/pull/281 | |
| Sergei Petrosian | 2023-07-03 10:19:00 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | |
| Doc Type | If docs needed, set a value | Release Note | ||
| Sergei Petrosian | 2023-07-03 10:24:34 UTC | Doc Type | Release Note | Enhancement |
| Sergei Petrosian | 2023-07-03 10:28:20 UTC | Doc Type | Enhancement | If docs needed, set a value |
| Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | |||
| Sergei Petrosian | 2023-07-03 10:29:17 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | |
| Doc Type | If docs needed, set a value | Enhancement | ||
| Sergei Petrosian | 2023-07-03 10:29:42 UTC | QA Contact | dyeisley | |
| Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | If this bug requires documentation, please select an appropriate Doc Type value. | ||
| Sergei Petrosian | 2023-07-03 10:30:16 UTC | Doc Text | If this bug requires documentation, please select an appropriate Doc Type value. | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. |
| Sergei Petrosian | 2023-07-03 10:30:42 UTC | Doc Type | Enhancement | If docs needed, set a value |
| Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | |||
| Sergei Petrosian | 2023-07-03 10:31:08 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | |
| Doc Type | If docs needed, set a value | Enhancement | ||
| Sergei Petrosian | 2023-07-03 10:32:33 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. |
| Sergei Petrosian | 2023-07-03 10:38:05 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. |
| Sergei Petrosian | 2023-07-04 06:23:34 UTC | Doc Type | Enhancement | If docs needed, set a value |
| Sergei Petrosian | 2023-07-04 06:25:08 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | |
| Sergei Petrosian | 2023-07-04 06:25:47 UTC | Doc Type | If docs needed, set a value | Enhancement |
| Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. |
|||
| Sergei Petrosian | 2023-07-04 06:26:43 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | Test text |
| Sergei Petrosian | 2023-07-04 06:28:02 UTC | Doc Text | Test text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. |
| Sergei Petrosian | 2023-07-04 06:39:34 UTC | Link ID | Github linux-system-roles/auto-maintenance/pull/280 | |
| Sergei Petrosian | 2023-07-04 15:16:03 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | The podman role has test yml files that should not be processed by lsr_role2collection or report-modules-plugins. The lsr r2c should skip processing any `files/` or `templates/` directories. The `report-modules-plugins.py` should skip checking `files/` files for plugins. Signed-off-by: Rich Megginson <rmeggins@redhat.com> |
| Sergei Petrosian | 2023-07-04 15:18:44 UTC | Doc Text | The podman role has test yml files that should not be processed by lsr_role2collection or report-modules-plugins. The lsr r2c should skip processing any `files/` or `templates/` directories. The `report-modules-plugins.py` should skip checking `files/` files for plugins. Signed-off-by: Rich Megginson <rmeggins@redhat.com> | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. |
| Sergei Petrosian | 2023-07-10 09:05:58 UTC | Link ID | Github linux-system-roles/auto-maintenance/pull/281 | |
| Sergei Petrosian | 2023-07-10 09:06:01 UTC | Link ID | Github linux-system-roles/auto-maintenance/pull/280 | |
| Sergei Petrosian | 2023-07-10 09:35:10 UTC | Link ID | Github linux-system-roles/auto-maintenance/pull/281 | |
| Sergei Petrosian | 2023-07-10 12:33:42 UTC | Doc Type | Enhancement | If docs needed, set a value |
| Sergei Petrosian | 2023-07-10 12:38:10 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | |
| Sergei Petrosian | 2023-07-10 12:53:08 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | |
| Doc Type | If docs needed, set a value | Enhancement | ||
| Sergei Petrosian | 2023-07-10 13:38:02 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. |
| Sergei Petrosian | 2023-07-10 14:13:37 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | Test string Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. |
| Sergei Petrosian | 2023-07-10 14:16:01 UTC | Doc Text | Test string Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. |
| Sergei Petrosian | 2023-07-10 14:17:17 UTC | Link ID | Github linux-system-roles/auto-maintenance/pull/280 | |
| Sergei Petrosian | 2023-07-10 17:36:39 UTC | Doc Type | Enhancement | If docs needed, set a value |
| Sergei Petrosian | 2023-07-10 17:37:13 UTC | Doc Type | If docs needed, set a value | Enhancement |
| Sergei Petrosian | 2023-07-10 18:12:24 UTC | Doc Type | Enhancement | If docs needed, set a value |
| Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | |||
| Sergei Petrosian | 2023-07-10 18:21:18 UTC | Doc Type | If docs needed, set a value | Enhancement |
| Doc Text | The podman role has test yml files that should not be processed by lsr_role2collection or report-modules-plugins. The lsr r2c should skip processing any `files/` or `templates/` directories. The `report-modules-plugins.py` should skip checking `files/` files for plugins. Signed-off-by: Rich Megginson <rmeggins@redhat.com> |
|||
| Sergei Petrosian | 2023-07-11 08:08:01 UTC | Doc Text | The podman role has test yml files that should not be processed by lsr_role2collection or report-modules-plugins. The lsr r2c should skip processing any `files/` or `templates/` directories. The `report-modules-plugins.py` should skip checking `files/` files for plugins. Signed-off-by: Rich Megginson <rmeggins@redhat.com> | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. |
| Sergei Petrosian | 2023-07-11 08:26:40 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | The podman role has test yml files that should not be processed by lsr_role2collection or report-modules-plugins. The lsr r2c should skip processing any `files/` or `templates/` directories. The `report-modules-plugins.py` should skip checking `files/` files for plugins. Signed-off-by: Rich Megginson <rmeggins@redhat.com> |
| Sergei Petrosian | 2023-07-11 08:27:36 UTC | Doc Text | The podman role has test yml files that should not be processed by lsr_role2collection or report-modules-plugins. The lsr r2c should skip processing any `files/` or `templates/` directories. The `report-modules-plugins.py` should skip checking `files/` files for plugins. Signed-off-by: Rich Megginson <rmeggins@redhat.com> | |
| Sergei Petrosian | 2023-07-11 08:27:59 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. |
|
| Sergei Petrosian | 2023-07-11 08:43:36 UTC | Doc Type | Enhancement | If docs needed, set a value |
| Sergei Petrosian | 2023-07-11 08:44:32 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | The podman role has test yml files that should not be processed by lsr_role2collection or report-modules-plugins. The lsr r2c should skip processing any `files/` or `templates/` directories. The `report-modules-plugins.py` should skip checking `files/` files for plugins. Signed-off-by: Rich Megginson <rmeggins@redhat.com> |
| Doc Type | If docs needed, set a value | Enhancement | ||
| Sergei Petrosian | 2023-07-11 08:46:40 UTC | Link ID | Github linux-system-roles/auto-maintenance/pull/280 | |
| Sergei Petrosian | 2023-07-11 08:46:42 UTC | Link ID | Github linux-system-roles/auto-maintenance/pull/281 | |
| Sergei Petrosian | 2023-07-11 09:04:11 UTC | Doc Type | Enhancement | If docs needed, set a value |
| Link ID | Github linux-system-roles/auto-maintenance/pull/281 Github linux-system-roles/auto-maintenance/pull/280 | |||
| Doc Text | The podman role has test yml files that should not be processed by lsr_role2collection or report-modules-plugins. The lsr r2c should skip processing any `files/` or `templates/` directories. The `report-modules-plugins.py` should skip checking `files/` files for plugins. Signed-off-by: Rich Megginson <rmeggins@redhat.com> | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. |
||
| Sergei Petrosian | 2023-07-11 09:18:22 UTC | Doc Text | Now that all PRs in system roles follow the conventional commits format (see https://linux-system-roles.github.io/contribute.html#pr-description-format) we can automate updating doc texts in Bugzilla. This PR expands the bz-manage.sh script with `update_doc_text`. To be run like `ITR=9.3.0 sh ./bz-manage.sh update_doc_text`. When run, the script searches all PRs from the ITM and other filters provided and: 1. If a BZ has required_doc_text flag set to `+` or `-`, the BZ is skipped. + indicates that the doc text has already been verified by a tech writer. - indicates that no release note is required. 2. If a BZ has required_doc_text unset and GH PR set: Automatically add doc text from PR description 3. If a BZ has required_doc_text? set and GitHub PR set: If the existing doc_text is empty, automatically add doc text from PR description. Else, print the current doc text and doc type, print the GH PR info, and ask user if they want to update the doc text. 4. If a BZ has required_doc_text not set to + or - and GitHub PR unset: Print the current doc text and type, and ask user if they want to post a comment asking to attach a GH PR or enter the doc text. | The podman role has test yml files that should not be processed by lsr_role2collection or report-modules-plugins. The lsr r2c should skip processing any `files/` or `templates/` directories. The `report-modules-plugins.py` should skip checking `files/` files for plugins. Signed-off-by: Rich Megginson <rmeggins@redhat.com> |
| Doc Type | If docs needed, set a value | Enhancement | ||
| Sergei Petrosian | 2023-07-21 07:11:42 UTC | Status | NEW | CLOSED |
| Resolution | --- | WONTFIX | ||
| Last Closed | 2023-07-21 07:11:42 UTC |
Back to bug 2219317