Skip to content
New issue

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

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

Already on GitHub? # to your account

Add releases.md #1461

Merged
merged 1 commit into from
Oct 11, 2022
Merged

Add releases.md #1461

merged 1 commit into from
Oct 11, 2022

Conversation

afrittoli
Copy link
Member

Changes

The new releases.md includes details about release cadence, supported releases and, in future, EOL ones.

Similarly to what done on pipeline side, I simplified the README.md accordingly and updated the release cheat-sheet to remember to update the new releases.md one new releases are produced.

Signed-off-by: Andrea Frittoli andrea.frittoli@uk.ibm.com

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

  • Includes tests (if functionality changed/added)
  • Includes docs (if user facing)
  • Commit messages follow commit message best practices
  • Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.

Release Notes

NONE

/kind documentation

@tekton-robot tekton-robot added kind/documentation Categorizes issue or PR as related to documentation. release-note-none Denotes a PR that doesnt merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Oct 11, 2022
@afrittoli
Copy link
Member Author

afrittoli commented Oct 11, 2022

@tektoncd/triggers-maintainers FYI

This is part of the requirements for Tekton graduation.

@afrittoli
Copy link
Member Author

For pipeline, we had monthly releases so there are 4 releases which are not EOL yet, but for triggers, since v0.19 is more than 4 months old already, I only kept v0.20 as not EOL. If you prefer to have more releases not-EOL though, I can add v0.19 (and older ones back) in.

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 11, 2022
The new releases.md includes details about release cadence, supported
releases and, in future, EOL ones.

Similarly to what done on pipeline side, I simplified the README.md
accordingly and updated the release cheat-sheet to remember to update
the new releases.md one new releases are produced.

Signed-off-by: Andrea Frittoli <andrea.frittoli@uk.ibm.com>
Copy link
Member

@dibyom dibyom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 11, 2022
@tekton-robot tekton-robot merged commit 4c53195 into tektoncd:main Oct 11, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants