Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

(chore) Update GOVERNANCE.md for release process & triage time #3035

Merged
merged 2 commits into from
Mar 28, 2024
Merged

(chore) Update GOVERNANCE.md for release process & triage time #3035

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
197627e
(chore) Update GOVERNANCE.md for release process & triage time
schristoff Mar 25, 2024
0517655
Merge branch 'main' into schristoff-patch-2
schristoff Mar 28, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions GOVERNANCE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,17 @@ The [OWNERS.md] file defines the maintainers of the project.
## Release Process

Maintainers create the next release when the main branch is stable and related
groupings of work is complete. We do not have a fixed cadence and prefer to release
smaller batches of work more often.
groupings of work is complete. We have a loose cadence, and strive to hit a release
every three (3) months.

Releases are done by creating a [new release](https://github.com/getporter/porter/releases/new)
This will trigger the Github Action Pipelines to build and publish the new release to Github and
the Website. After this is done, we update the [CNCF Slack Channel](https://cloud-native.slack.com/) (#porter) & [Mailing List](https://groups.io/g/porter).

## Issue Response Timeline

Porter is taken care of by maintainers and contributors who volunteer their time.
We aim to **respond** to issues within five (5) business days.

## Roadmap

Expand Down
Loading