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

machine readable release schedule #718

Closed
yastij opened this issue Jul 9, 2019 · 12 comments · Fixed by #1096 or kubernetes/release#1313
Closed

machine readable release schedule #718

yastij opened this issue Jul 9, 2019 · 12 comments · Fixed by #1096 or kubernetes/release#1313
Assignees
@cpanato
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Milestone
v1.19

Comments

@yastij
Copy link
Member

yastij commented Jul 9, 2019

Currently our release planning is published a markdown. this issue tracks the move toward a more machine-friendly format (e.g. yaml) that users can use as release signal

/assign
/area release-eng
/priority important-soon
/kind cleanup
@k8s-ci-robot k8s-ci-robot added area/release-eng Issues or PRs related to the Release Engineering subproject priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels Jul 9, 2019
@yastij
Copy link
Member Author

yastij commented Jul 9, 2019

@justaugustus - should the release handbook be updated too ? If yes, can you point me where ?

Thanks

@justaugustus
Copy link
Member

@yastij -- I'm planning to sweep the Branch Manager and Patch Release Team now that both groups have moved under Release Engineering.

I think it would still be great to have the markdown, in addition to the yaml, to make it easy for people who may not want/need to consume the yaml.

Could we do something similar to the k/community docs generation?

@justaugustus
Copy link
Member

/milestone v1.16
/sig release

@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Jul 10, 2019
@k8s-ci-robot k8s-ci-robot added this to the v1.16 milestone Jul 10, 2019
@justaugustus justaugustus added this to Backlog in SIG Release via automation Jul 10, 2019
@frapposelli
Copy link
Member

any updates on this?

@yastij
Copy link
Member Author

yastij commented Sep 9, 2019

@frapposelli - didn't have time to get to this yet, I'll probably get to it by the end of the week

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 27, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 26, 2020
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

SIG Release automation moved this from Backlog to Done (1.19) Mar 27, 2020
@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@justaugustus justaugustus removed kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels May 20, 2020
@k8s-ci-robot k8s-ci-robot added the needs-kind Indicates a PR lacks a `kind/foo` label and requires one. label May 20, 2020
@justaugustus justaugustus added kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels May 20, 2020
@k8s-ci-robot k8s-ci-robot removed the needs-kind Indicates a PR lacks a `kind/foo` label and requires one. label May 20, 2020
@justaugustus justaugustus modified the milestones: v1.16, v1.19 May 20, 2020
@justaugustus justaugustus reopened this May 20, 2020
SIG Release automation moved this from Done (1.19) to In progress May 20, 2020
@cpanato
Copy link
Member

cpanato commented May 20, 2020

/assign

@cpanato
Copy link
Member

cpanato commented May 21, 2020

/assign

This was referenced May 21, 2020
Merged
Merged
SIG Release automation moved this from In progress to Done (1.19) Jun 7, 2020
@cpanato
Copy link
Member

cpanato commented Jun 8, 2020

/reopen because we still have one PR open

@cpanato cpanato reopened this Jun 8, 2020
SIG Release automation moved this from Done (1.19) to In progress Jun 8, 2020
SIG Release automation moved this from In progress to Done (1.19) Jul 17, 2020
k8s-ci-robot added a commit that referenced this issue Jul 17, 2020
@k8s-ci-robot
Merge pull request #1096 from cpanato/GH-718
a99d60c 
schedule: add release schedule in yaml machine readable format
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cpanato cpanato

Labels
area/release-eng Issues or PRs related to the Release Engineering subproject kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Milestone
v1.19
6 participants
@frapposelli @justaugustus @cpanato @yastij @k8s-ci-robot @fejta-bot