From 3e848b87bd30fe2ae4241213db5556623f837091 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Thu, 12 Sep 2024 16:53:40 -0400 Subject: [PATCH 1/9] Add bug-fix-issue.md --- .github/ISSUE_TEMPLATE/bug-fix-issue.md | 47 +++++++++++++++++++++++++ 1 file changed, 47 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/bug-fix-issue.md diff --git a/.github/ISSUE_TEMPLATE/bug-fix-issue.md b/.github/ISSUE_TEMPLATE/bug-fix-issue.md new file mode 100644 index 0000000..b9b7a39 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug-fix-issue.md @@ -0,0 +1,47 @@ +--- +name: Bug Fix Issue +about: A standard Bug Fix template and the types of information that should be captured in a Bug Fix issue. +title: '' +labels: '' +assignees: '' + +--- + +# Prerequisites + +Please answer the following questions for yourself before submitting a Bug Fix issue: +* Is the title clear and understandable at a glance? +* Is a label present if appropriate? + +Labels are not required for all tickets, but they are helpful for prioritization. Please check the labels drop-down to see if any of the pre-set labels work for your ticket. + +**YOU SHOULD DELETE THE PREREQUISITES SECTION.** + +# Environment + +Indicate the environment that the bug was realized. This can also be more than environment. Can include the following: OS, browser, local/dev/staging/prod etc. + +# Date/time occurred + +Indicate the date/time the bug was realized. + +# Description + +What is the problem? What are the results? + +# Step to Reproduce + +What are the steps performed to reproduce this bug? + +# Expected Results + +What are the expected results? What is the expected behavior? + +# Evidence + +Please provide screenshots/screen capture or other evidence such as a log files (scrubbed of sensitive information). + +# Estimated Severity + +If possible, provide an initial estimate the severity of the issue. This of course can be adjusted after submission. + From 154cfb9f09bf5da15c4fe8c00b7f1c65b7de0a67 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Thu, 12 Sep 2024 16:58:43 -0400 Subject: [PATCH 2/9] Update Description section --- .github/ISSUE_TEMPLATE/bug-fix-issue.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/bug-fix-issue.md b/.github/ISSUE_TEMPLATE/bug-fix-issue.md index b9b7a39..601e48a 100644 --- a/.github/ISSUE_TEMPLATE/bug-fix-issue.md +++ b/.github/ISSUE_TEMPLATE/bug-fix-issue.md @@ -27,7 +27,7 @@ Indicate the date/time the bug was realized. # Description -What is the problem? What are the results? +What is the problem? What are the results? Describe what is currently happening in detail. # Step to Reproduce From 9e16a2bf07854ba63d0c446ffbb2acabadacf80d Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Fri, 13 Sep 2024 16:42:38 -0400 Subject: [PATCH 3/9] Fix language --- .github/ISSUE_TEMPLATE/bug-fix-issue.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug-fix-issue.md b/.github/ISSUE_TEMPLATE/bug-fix-issue.md index 601e48a..c47a3d5 100644 --- a/.github/ISSUE_TEMPLATE/bug-fix-issue.md +++ b/.github/ISSUE_TEMPLATE/bug-fix-issue.md @@ -19,7 +19,7 @@ Labels are not required for all tickets, but they are helpful for prioritization # Environment -Indicate the environment that the bug was realized. This can also be more than environment. Can include the following: OS, browser, local/dev/staging/prod etc. +Indicate the environment that the bug was realized. This can also be more than environment and may include the following: OS, browser, local/dev/staging/prod etc. # Date/time occurred @@ -29,7 +29,7 @@ Indicate the date/time the bug was realized. What is the problem? What are the results? Describe what is currently happening in detail. -# Step to Reproduce +# Steps to Reproduce What are the steps performed to reproduce this bug? @@ -39,9 +39,9 @@ What are the expected results? What is the expected behavior? # Evidence -Please provide screenshots/screen capture or other evidence such as a log files (scrubbed of sensitive information). +Please provide screenshots/screen capture or other evidence such as log files (scrubbed of sensitive information). # Estimated Severity -If possible, provide an initial estimate the severity of the issue. This of course can be adjusted after submission. +If possible, provide an initial severity estimate of the issue. This of course can be adjusted after submission. From 0b6adba902de756bed655f1b466b6f5fe8678ec2 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Fri, 13 Sep 2024 17:01:59 -0400 Subject: [PATCH 4/9] Add enhancement-request-issue.md --- .../enhancement-request-issue.md | 42 +++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/enhancement-request-issue.md diff --git a/.github/ISSUE_TEMPLATE/enhancement-request-issue.md b/.github/ISSUE_TEMPLATE/enhancement-request-issue.md new file mode 100644 index 0000000..63ceaec --- /dev/null +++ b/.github/ISSUE_TEMPLATE/enhancement-request-issue.md @@ -0,0 +1,42 @@ +--- +name: Enhancement Request Issue +about: A standard Enhancement Request template and the types of information that should be captured in a Enhancement Request issue. +title: '' +labels: '' +assignees: '' + +--- + +# Prerequisites + +Please answer the following questions for yourself before submitting a Bug Fix issue: +* Is the title clear and understandable at a glance? +* Is a label present if appropriate? + +Labels are not required for all tickets, but they are helpful for prioritization. Please check the labels drop-down to see if any of the pre-set labels work for your ticket. + +**YOU SHOULD DELETE THE PREREQUISITES SECTION.** + +# Description + +A description of the enhancement. + +# Value + +Why is this enhancement important/valuable? + +# Users/Target Audience + +Who would benefit from this enhancement? + +# Requirements + +If known, what are the dependencies and infrastructure required for this enhancement? + +# Examples + +Are there any current examples of this feature somewhere else? Please provide screenshots or URLs of this enhancement. + +# Risks + +Are there any risks that may be associated with this enhancement? For example, cost, time, performance impact or increased complexity? \ No newline at end of file From 5e1fbf8207247b915ea0c1b3ac74819edfa4b151 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Fri, 13 Sep 2024 17:09:36 -0400 Subject: [PATCH 5/9] Add release-checklist-issue.md --- .../ISSUE_TEMPLATE/release-checklist-issue.md | 47 +++++++++++++++++++ 1 file changed, 47 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/release-checklist-issue.md diff --git a/.github/ISSUE_TEMPLATE/release-checklist-issue.md b/.github/ISSUE_TEMPLATE/release-checklist-issue.md new file mode 100644 index 0000000..fab3fba --- /dev/null +++ b/.github/ISSUE_TEMPLATE/release-checklist-issue.md @@ -0,0 +1,47 @@ +--- +name: Release Checklist Issue +about: PASS Release Checklist includes all the necessary steps required to successfully release the next version of PASS. +title: 'Release MAJOR.MINOR.PATCH' +labels: 'Release' +assignees: '' + +--- + +# Release Manager Actions Checklist + +| | | +| --- |-----------------| +| Release version | MAJOR.MINOR.PATCH | +| Next dev version | MAJOR.MINOR.PATCH-SNAPSHOT | + +## Release Process Overview +This is the full detailed release process, including the steps that are performed by the GitHub automation: [Release](https://github.com/eclipse-pass/main/blob/main/docs/dev/release.md) + +## Pre-release + +- [] Identify the version to be utilized for the release. +- [] Ensure all code commits and PRs intended for the release have been merged. +- [] Issue a code freeze statement on the Eclipse PASS slack #pass-dev channel to notify all developers that a release is imminent. + +[Release Steps with Automations](https://github.com/eclipse-pass/main/blob/main/docs/dev/release-steps-with-automations.md) + +## Release Projects + +[Release All Modules Workflow](https://github.com/eclipse-pass/main/actions/workflows/pass-complete-release.yml) + +- [] Release Main +- [] Release Pass-Core +- [] Release Pass Support +- [] Release Pass UI +- [] Release Pass Acceptance Testing +- [] Release Pass Docker + +## Post-release + +- [] Test the release by using the [acceptance test workflow](https://github.com/eclipse-pass/pass-acceptance-testing/actions/workflows/test.yml). Enter the release number into the Ref field. +- [] Check that correct tickets are in the release milestone. [GitHub Ticket Update](https://github.com/eclipse-pass/main/blob/main/docs/dev/release.md#update-release-notes) +- [] Write release notes in the [Release Notes doc](https://github.com/eclipse-pass/main/blob/main/docs/release-notes.md), submit a PR for the changes, and ensure the PR is merged. Release Notes should be written to be understandable by community members who are not technical. +- [] Draft release message and have technical & community lead provide feedback. Ensure that a link to the release notes is included in the release message. +- [] Post a message about the release to the PASS Google Group. [Notes about the PASS Google Group](https://github.com/eclipse-pass/main/blob/main/docs/dev/release.md#process) +- [] Update [Pass Demo](https://demo.eclipse-pass.org) to new release - [Publish to SNS Topic action](https://github.com/eclipse-pass/main/actions/workflows/deployToAWS.yml) using `Environment: demo` +- [] Send message to Eclipse PASS slack #pass-dev channel that the release is complete. \ No newline at end of file From ce1ff47c06ea3ec7cdde099dca2bbe85ad70ce82 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Tue, 17 Sep 2024 09:26:44 -0400 Subject: [PATCH 6/9] Clean language --- .github/ISSUE_TEMPLATE/bug-fix-issue.md | 2 +- .github/ISSUE_TEMPLATE/release-checklist-issue.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug-fix-issue.md b/.github/ISSUE_TEMPLATE/bug-fix-issue.md index c47a3d5..aa53712 100644 --- a/.github/ISSUE_TEMPLATE/bug-fix-issue.md +++ b/.github/ISSUE_TEMPLATE/bug-fix-issue.md @@ -19,7 +19,7 @@ Labels are not required for all tickets, but they are helpful for prioritization # Environment -Indicate the environment that the bug was realized. This can also be more than environment and may include the following: OS, browser, local/dev/staging/prod etc. +Indicate the environment that the bug was realized. This can also be more than the environment and may include the following: OS, browser, local/dev/staging/prod etc. # Date/time occurred diff --git a/.github/ISSUE_TEMPLATE/release-checklist-issue.md b/.github/ISSUE_TEMPLATE/release-checklist-issue.md index fab3fba..87b9092 100644 --- a/.github/ISSUE_TEMPLATE/release-checklist-issue.md +++ b/.github/ISSUE_TEMPLATE/release-checklist-issue.md @@ -9,9 +9,9 @@ assignees: '' # Release Manager Actions Checklist -| | | -| --- |-----------------| -| Release version | MAJOR.MINOR.PATCH | +| | | +|------------------|----------------------------| +| Release version | MAJOR.MINOR.PATCH | | Next dev version | MAJOR.MINOR.PATCH-SNAPSHOT | ## Release Process Overview From af88381a797f3b67437dd37937ff98d91cf445b1 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Tue, 17 Sep 2024 14:14:15 -0400 Subject: [PATCH 7/9] Update to language - Changes from the PASS Weekly meeting. --- .github/ISSUE_TEMPLATE/bug-fix-issue.md | 16 ++++++++++------ .../ISSUE_TEMPLATE/enhancement-request-issue.md | 8 ++++---- 2 files changed, 14 insertions(+), 10 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug-fix-issue.md b/.github/ISSUE_TEMPLATE/bug-fix-issue.md index aa53712..1da899d 100644 --- a/.github/ISSUE_TEMPLATE/bug-fix-issue.md +++ b/.github/ISSUE_TEMPLATE/bug-fix-issue.md @@ -1,17 +1,17 @@ --- -name: Bug Fix Issue -about: A standard Bug Fix template and the types of information that should be captured in a Bug Fix issue. +name: Bug Report Issue +about: A standard Bug Report template and the types of information that should be captured in a Bug Report issue. title: '' -labels: '' +labels: 'bug' assignees: '' --- # Prerequisites -Please answer the following questions for yourself before submitting a Bug Fix issue: +Please answer the following questions for yourself before submitting a Bug Report issue: * Is the title clear and understandable at a glance? -* Is a label present if appropriate? +* Should any other labels be added to this issue? Labels are not required for all tickets, but they are helpful for prioritization. Please check the labels drop-down to see if any of the pre-set labels work for your ticket. @@ -27,7 +27,7 @@ Indicate the date/time the bug was realized. # Description -What is the problem? What are the results? Describe what is currently happening in detail. +What is the problem? Describe what is currently happening in detail. # Steps to Reproduce @@ -37,6 +37,10 @@ What are the steps performed to reproduce this bug? What are the expected results? What is the expected behavior? +# Actual Results + +What are the actual results and provide any evidence of the actual results below. + # Evidence Please provide screenshots/screen capture or other evidence such as log files (scrubbed of sensitive information). diff --git a/.github/ISSUE_TEMPLATE/enhancement-request-issue.md b/.github/ISSUE_TEMPLATE/enhancement-request-issue.md index 63ceaec..4be3137 100644 --- a/.github/ISSUE_TEMPLATE/enhancement-request-issue.md +++ b/.github/ISSUE_TEMPLATE/enhancement-request-issue.md @@ -2,16 +2,16 @@ name: Enhancement Request Issue about: A standard Enhancement Request template and the types of information that should be captured in a Enhancement Request issue. title: '' -labels: '' +labels: 'Improvement' assignees: '' --- # Prerequisites -Please answer the following questions for yourself before submitting a Bug Fix issue: +Please answer the following questions for yourself before submitting an Enhancement Request issue: * Is the title clear and understandable at a glance? -* Is a label present if appropriate? +* Should any other labels be added to this issue? Labels are not required for all tickets, but they are helpful for prioritization. Please check the labels drop-down to see if any of the pre-set labels work for your ticket. @@ -19,7 +19,7 @@ Labels are not required for all tickets, but they are helpful for prioritization # Description -A description of the enhancement. +A description of the enhancement. What are the new features/improvements to this enhancement change? # Value From a560dd2e48f191c2b0bcf5fb64c70db49992a507 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Tue, 17 Sep 2024 14:18:48 -0400 Subject: [PATCH 8/9] Update filename --- .github/ISSUE_TEMPLATE/{bug-fix-issue.md => bug-report-issue.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename .github/ISSUE_TEMPLATE/{bug-fix-issue.md => bug-report-issue.md} (100%) diff --git a/.github/ISSUE_TEMPLATE/bug-fix-issue.md b/.github/ISSUE_TEMPLATE/bug-report-issue.md similarity index 100% rename from .github/ISSUE_TEMPLATE/bug-fix-issue.md rename to .github/ISSUE_TEMPLATE/bug-report-issue.md From d61e716d097ccf0d11c045d58ffa46042c9967f2 Mon Sep 17 00:00:00 2001 From: Timothy Sanders Date: Tue, 17 Sep 2024 14:25:28 -0400 Subject: [PATCH 9/9] Remove lines --- .github/ISSUE_TEMPLATE/bug-report-issue.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug-report-issue.md b/.github/ISSUE_TEMPLATE/bug-report-issue.md index 1da899d..1be5ec0 100644 --- a/.github/ISSUE_TEMPLATE/bug-report-issue.md +++ b/.github/ISSUE_TEMPLATE/bug-report-issue.md @@ -47,5 +47,4 @@ Please provide screenshots/screen capture or other evidence such as log files (s # Estimated Severity -If possible, provide an initial severity estimate of the issue. This of course can be adjusted after submission. - +If possible, provide an initial severity estimate of the issue. This of course can be adjusted after submission. \ No newline at end of file