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

Release info added from the features repo #46

Merged
merged 2 commits into from
Dec 18, 2017

Conversation

idvoretskyi
Copy link
Member

@idvoretskyi idvoretskyi commented Dec 18, 2017

Kubernetes 1.3-1.9 releases info moved from the https://github.com/kubernetes/features repo (existing release-1.* directories from the features repo will be removed after this PR will be merged).

FYI @pwittrock @calebamiles @grodrigues3 @spiffxp @jdumars

@idvoretskyi idvoretskyi added sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/release Categorizes an issue or PR as relevant to SIG Release. labels Dec 18, 2017
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Dec 18, 2017
We are starting to collect release notes for the major changes in Kubernetes 1.8.
A [draft](https://github.com/kubernetes/features/blob/master/release-1.8/release_notes_draft.md) [1]
has been prepared in the 1.8 release directory but we need your help to populate the changes by
component which is how we have organized [previous release notes](https://github.com/kubernetes/features/blob/master/release-1.7/release-notes-draft.md) [2].
Copy link
Member

Choose a reason for hiding this comment

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

Broken link (relative needed)

- Feature owners submit docs PR which references issue in features repo by **TODAY!**
- Feature owners prepare release notes by **TODAY!**
- Address etcd upgrade test failures
- Begin adding human curated release notes to [the release notes draft](https://github.com/kubernetes/features/blob/release-notes-draft-1.6/release-1.6/release-notes-draft.md) by Friday, 17 March 2017 **please commit directly to the `release-notes-draft-1.6` branch so we can comment on the [associated PR](https://github.com/kubernetes/features/pull/203) collectively**
Copy link
Member

Choose a reason for hiding this comment

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

Broken link (relative needed)

- Feature owners submit docs PR which references issue in features repo by **TODAY!**
- Feature owners prepare release notes by **TODAY!**
- Address etcd upgrade test failures
- Begin adding human curated release notes to [the release notes draft](https://github.com/kubernetes/features/blob/release-notes-draft-1.6/release-1.6/release-notes-draft.md) by **TODAY** **please commit directly to the `release-notes-draft-1.6` branch so we can comment on the [associated PR](https://github.com/kubernetes/features/pull/203) collectively**
Copy link
Member

Choose a reason for hiding this comment

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

Broken link (relative needed)

- Open issues filed against [`kubernetes/features` in 1.6 milestone](https://github.com/kubernetes/features/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20milestone%3Av1.6): 29 (**unchanged from last report**)
- PRs still needing docs
- https://github.com/kubernetes/features/issues/43
- Human curated release notes still incomplete. Specifically very litte curation of [automatically generated release notes](https://github.com/kubernetes/features/blob/release-notes-draft-1.6/release-1.6/release-notes-draft.md#auto-generated-release-notes)
Copy link
Member

Choose a reason for hiding this comment

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

Broken link (relative needed)

- Feature owners submit docs PR which references issue in features repo by **TODAY!**
- Feature owners prepare release notes by **TODAY!**
- Address etcd upgrade test failures
- Finish adding human curated release notes to [the release notes draft](https://github.com/kubernetes/features/blob/release-notes-draft-1.6/release-1.6/release-notes-draft.md) by **TODAY** **please commit directly to the `release-notes-draft-1.6` branch so we can comment on the [associated PR](https://github.com/kubernetes/features/pull/203) collectively**
Copy link
Member

Choose a reason for hiding this comment

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

Broken link (relative needed)

We would like to have the draft release notes finished by 08 September 2017 which is one week after code freeze.
Once your SIG has filled out their section according to the [guidance](https://github.com/kubernetes/community/issues/484) [3],
provided by Brian Grant, please check off your section in the checklist
[embedded in the draft](https://github.com/kubernetes/features/blob/master/release-1.8/release_notes_draft.md#checklist-for-sigs-and-release-team) [4].
Copy link
Member

Choose a reason for hiding this comment

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

Broken link (relative needed)


Links:

1. https://github.com/kubernetes/features/blob/master/release-1.8/release_notes_draft.md
Copy link
Member

Choose a reason for hiding this comment

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

Broken link (relative needed)

Links:

1. https://github.com/kubernetes/features/blob/master/release-1.8/release_notes_draft.md
2. https://github.com/kubernetes/features/blob/master/release-1.7/release-notes-draft.md
Copy link
Member

Choose a reason for hiding this comment

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

Broken link (relative needed)

1. https://github.com/kubernetes/features/blob/master/release-1.8/release_notes_draft.md
2. https://github.com/kubernetes/features/blob/master/release-1.7/release-notes-draft.md
3. https://github.com/kubernetes/community/issues/484
4. https://github.com/kubernetes/features/blob/master/release-1.8/release_notes_draft.md#checklist-for-sigs-and-release-team
Copy link
Member

Choose a reason for hiding this comment

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

Broken link (relative needed)

link](https://docs.google.com/spreadsheets/d/1AFksRDgAt6BGA3OjRNIiO3IyKmA-GU7CXaxbihy48ns/edit#gid=0)

## Operational Changes
1. For the 1.8 release, the [release team](https://github.com/kubernetes/features/blob/master/release-1.8/release_team.md)
Copy link
Member

Choose a reason for hiding this comment

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

Broken link (relative needed)

@stp-ip
Copy link
Member

stp-ip commented Dec 18, 2017

Problem in general is that yes it's something specific to the release team and sig, but it's also "user" facing information and moving it from the features repo, which is already sorta hard to find, might make this even harder. Considering that we have official release notes, it's just something to take into consideration.

@stp-ip
Copy link
Member

stp-ip commented Dec 18, 2017

Also https://github.com/kubernetes/features/blob/master/EXCEPTIONS.md must be changed to point to the latest release and the correct repo or needs to be removed as it (the link to the release) doesn't seem up to date anyway.

@idvoretskyi
Copy link
Member Author

Also https://github.com/kubernetes/features/blob/master/EXCEPTIONS.md must be changed to point to the latest release and the correct repo or needs to be removed as it (the link to the release) doesn't seem up to date anyway.

Thanks, will update after the new links will be live.

@idvoretskyi
Copy link
Member Author

idvoretskyi commented Dec 18, 2017

Problem in general is that yes it's something specific to the release team and sig, but it's also "user" facing information and moving it from the features repo, which is already sorta hard to find, might make this even harder. Considering that we have official release notes, it's just something to take into consideration.

@stp-ip features repo is not the best place to track and store release-related information as it has to track features efforts only. Since now we have the sig-release repo, it could be a better place to store these artifacts.

Also, some related data was already migrated #42

@stp-ip
Copy link
Member

stp-ip commented Dec 18, 2017

Great. Happy to lgtm, after the comments are addressed with EXCEPTIONS.md being doable in a follow-up PR.

@idvoretskyi
Copy link
Member Author

@stp-ip links updated. Thanks for noticing!

@stp-ip
Copy link
Member

stp-ip commented Dec 18, 2017

Sidenote: relative links would also work within the same repo.

/ok-to-test
/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 18, 2017
@jdumars
Copy link
Member

jdumars commented Dec 18, 2017

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: idvoretskyi, jdumars, stp-ip

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

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 18, 2017
@k8s-ci-robot k8s-ci-robot merged commit 0fad6d6 into kubernetes:master Dec 18, 2017
idvoretskyi added a commit to kubernetes/enhancements that referenced this pull request Dec 18, 2017
idvoretskyi added a commit to kubernetes/enhancements that referenced this pull request Dec 18, 2017
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/release Categorizes an issue or PR as relevant to SIG Release. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants