-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'eclipse-pass:main' into prune-infra-docs-sm
- Loading branch information
Showing
12 changed files
with
325 additions
and
41 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,50 @@ | ||
| --- | ||
| 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: 'bug' | ||
| assignees: '' | ||
|
|
||
| --- | ||
|
|
||
| # Prerequisites | ||
|
|
||
| Please answer the following questions for yourself before submitting a Bug Report issue: | ||
| * Is the title clear and understandable at a glance? | ||
| * 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. | ||
|
|
||
| **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? 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? | ||
|
|
||
| # 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). | ||
|
|
||
| # Estimated Severity | ||
|
|
||
| If possible, provide an initial severity estimate of the issue. This of course can be adjusted after submission. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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: 'Improvement' | ||
| assignees: '' | ||
|
|
||
| --- | ||
|
|
||
| # Prerequisites | ||
|
|
||
| Please answer the following questions for yourself before submitting an Enhancement Request issue: | ||
| * Is the title clear and understandable at a glance? | ||
| * 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. | ||
|
|
||
| **YOU SHOULD DELETE THE PREREQUISITES SECTION.** | ||
|
|
||
| # Description | ||
|
|
||
| A description of the enhancement. What are the new features/improvements to this enhancement change? | ||
|
|
||
| # 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? |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| name: Update package version for release | ||
| description: | | ||
| Updates package version which automatically does a commit and this action tags | ||
| inputs: | ||
| repository_dir: | ||
| description: 'Directory of repository to update' | ||
| required: true | ||
| skip_tag: | ||
| description: 'Skip git tag' | ||
| required: false | ||
| default: "false" | ||
|
|
||
| runs: | ||
| using: composite | ||
| steps: | ||
| - name: Install pnpm | ||
| uses: pnpm/action-setup@v4 | ||
| with: | ||
| version: 9 | ||
| - name: Update version and tag | ||
| shell: bash | ||
| working-directory: ${{ inputs.repository_dir }} | ||
| env: | ||
| SKIP_TAG: ${{ inputs.skip_tag }} | ||
| run: | | ||
| pnpm install --frozen-lockfile | ||
| pnpm version --git-tag-version false --new-version $RELEASE | ||
| git commit --allow-empty -am "Update version to $RELEASE" | ||
| if [ "$SKIP_TAG" == "false" ]; then | ||
| echo "Tagging version $RELEASE" | ||
| git tag $RELEASE | ||
| fi |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -27,4 +27,4 @@ runs: | |
| if [ "$SKIP_TAG" == "false" ]; then | ||
| echo "Tagging yarn version $RELEASE" | ||
| git tag $RELEASE | ||
| fi | ||
| fi | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| # Release Manager Actions Checklist Template | ||
|
|
||
| - Release tracked in GitHub issue: https://github.com/eclipse-pass/main/issues/1039 |
Oops, something went wrong.