Develop New Issue Templates

.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 the environment and may 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? Describe what is currently happening in detail.
+
+# Steps 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 log files (scrubbed of sensitive information).
+
+# Estimated Severity
+
+If possible, provide an initial severity estimate of the issue. This of course can be adjusted after submission. 
+

.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?

.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.