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

Fetch remote JSON release notes for official releases #1815

Merged
merged 1 commit into from
Dec 3, 2020
Merged

Fetch remote JSON release notes for official releases #1815

merged 1 commit into from
Dec 3, 2020

Conversation

saschagrunert
Copy link
Member

What type of PR is this?

/kind feature

What this PR does / why we need it:

In case we try to download the remote release notes draft as markdown,
we also need an equivalent JSON. This patch now assumes that there is a
JSON version side by side to the markdown release notes during official,
non patch release creation.

Which issue(s) this PR fixes:

Refers to #1087

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

Changed release notes fetching for official (non patch) releases to also assume a JSON version side by side to the markdown draft

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority size/M Denotes a PR that changes 30-99 lines, ignoring generated files. area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Dec 3, 2020
@saschagrunert
Copy link
Member Author

@puerco my idea was to change krel release-notes to automatically produce a JSON version of the draft, too. That way we can also include the mappings. Do you think this can be done in an easy way?

I think for v1.20.0 we can just generate the notes manually and put them as JSON side by side to the markdown draft, too.

In case we try to download the remote release notes draft as markdown,
we also need an equivalent JSON. This patch now assumes that there is a
JSON version side by side to the markdown release notes during official,
non patch release creation.

Signed-off-by: Sascha Grunert <sgrunert@suse.com>
Copy link
Member

@xmudrii xmudrii left a comment

Choose a reason for hiding this comment

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

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 3, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: saschagrunert, xmudrii

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

@k8s-ci-robot k8s-ci-robot merged commit 0ce000f into kubernetes:master Dec 3, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.20 milestone Dec 3, 2020
@saschagrunert saschagrunert deleted the remote-json-notes branch December 3, 2020 13:44
@puerco
Copy link
Member

puerco commented Dec 3, 2020

Yes! I'll change it today to PR the json along with the draft

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/release Categorizes an issue or PR as relevant to SIG Release. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants