Initial incomplete release notes draft for 1.7

[spiffxp]

I do not have the committed hours to shepherd release notes all the way through but have volunteered to do a quick first cut, mostly based on the features spreadsheet. I have dropped TODO's on places that need filling in. I will send followon PR's as I am able to help with content and wordsmithing.

I started with the release-1.5/release-notes-draft.md file, and removed all content under the existing headings.

I used the following script to start populating the features section

for sig in $(hub issue -M 6 | sed -e 's|.*sig/\([^ ]*\).*|\1|g' | sort | uniq); do
  echo "- **$sig**"
  for stage in alpha beta stable; do 
    hub issue -M 6 -l sig/$sig,stage/$stage -f \
      "  - [$stage] %t ([kubernetes/features%i](%U))%n";
  done
done

I noticed the following sections in the release-1.6/release-notes-draft.md file, but have explicitly left them out here. Please add back in if you feel they're necessary:

• WARNING: etcd backup strongly recommneded
• Changes to API Resources
• Changes to Major Components
• Changes to Cluster Provisioning Scripts
• Changes to Addons

I manually replaced the feature issue titles with one-line release notes from the feature tracking spreadsheet

I manually added the docs PR links using the links provided in the feature tracking spreadsheet

Assigning @dchen1107 as requested /cc @kubernetes/kubernetes-release-managers

[dchen1107]

@spiffxp Thanks for your help. We are going to carry on from here.

[evie404]

not sure if this is the right place, but I committed a new feature in 1.7 that involves a new PodSpec field to populate entries into the pod's hosts file as a way to manage local hostname-ip overrides.

there's no feature issue as the feature was discussed in an issue. but there's a docs PR.

questions:

1. could it be added?
2. do i need a features issue? i can add one retroactively

[calebamiles]

Thanks @spiffxp. Merging and SIGs can fork from there.

[luxas]

@rickypai I'd definitely add a release note item. Thank you for bringing that up!
I guess you can send a PR to this doc...

cc @idvoretskyi @apsinha for deciding on adding a features issue for it retroactively

[idvoretskyi]

@spiffxp thanks for adding this.

[idvoretskyi]

@rickypai as discussed in the thread - this deliverability has not been targeted as a feature and does not classify as a feature - it is unlikely to add it to the "features" section.

I would propose to have it in the release notes under the "notable changes" section or similar. cc @apsinha @luxas

[idvoretskyi]

Replace link with https://github.com/kubernetes/community/blob/master/sig-list.md

[luxas]

I would propose to have it in the release notes under the "notable changes" section or similar. cc @apsinha @luxas

Listing it there SGTM