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.

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

Improve pre-release reporting dashboard #2

Closed
3 tasks
david-mcmahon opened this issue Apr 21, 2016 · 5 comments
Closed
3 tasks

Improve pre-release reporting dashboard #2

david-mcmahon opened this issue Apr 21, 2016 · 5 comments
Assignees
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@david-mcmahon
Copy link
Contributor

david-mcmahon commented Apr 21, 2016

relnotes has a mechanism for generating a release preview that is currently used internally at Google, but it would be great to expose this externally so the whole community can keep a regular eye on a release all along the way until it is cut. The report provides the following:

  • Preview of the release notes that will ship with a release
  • Pending PRs on the branch (non-master only)
  • State of the branch based on jenkins builders/testing

An example run looks like this:

$ relnotes --htmlize-md --branch=release-1.6 --preview --markdown-file=/tmp/k8s-release-1.6.md --html-file=/tmp/k8s-release-1.2.html

or

$ relnotes --htmlize-md --branch=master --preview --markdown-file=/tmp/k8s-master.md --html-file=/tmp/k8s-master.html

This issue will track this current list of wants:

  • Expose this externally so that the community can see it
  • Tailor the layout to make it more readable/parsable
  • Based on testing state and the last good git hash that would be chosen for a release, cross out the release notes that would get missed if we released today(now).

cc: @ixdy @dchen1107 @caesarxuchao @kubernetes/release-maintainers @dclaar @javier-b-perez @krzyzacy

@david-mcmahon david-mcmahon self-assigned this Apr 21, 2016
@david-mcmahon david-mcmahon changed the title Improve pre-release reporting Improve pre-release reporting dashboard Jul 9, 2016
@david-mcmahon david-mcmahon added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Dec 19, 2016
@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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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 Dec 26, 2017
@mithrav
Copy link

mithrav commented Jan 13, 2018

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 13, 2018
@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 Apr 13, 2018
@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
/remove-lifecycle stale

@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 May 13, 2018
@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

k8s-ci-robot pushed a commit that referenced this issue Sep 21, 2018
marpaia pushed a commit to marpaia/release that referenced this issue Feb 21, 2019
…s-draft

Release 1.11 release notes document template with proposed tags
k8s-ci-robot pushed a commit that referenced this issue Jul 26, 2019
* releaselib_test.sh: Add boilerplate header

* Use shared test harness

* Fix releaselib tests

* Cannot export a map value

Fixes:

```
Step #2: /workspace/go/src/k8s.io/release/lib/gitlib.sh: line 137: export: `PROGSTEP[gitlib::github_acls]': not a valid identifier
```

* Fix gitlib tests

* Run common_test.sh with bazel

* Adhere to style guide

* Add TODO to make test scripts more strict
@justaugustus justaugustus added sig/release Categorizes an issue or PR as relevant to SIG Release. area/release-eng Issues or PRs related to the Release Engineering subproject labels Dec 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

No branches or pull requests

5 participants