[ACTION REQUIRED] Release notes first draft due tomorrow

[Jaice Singer DuMars]

Hello community,

Tomorrow is the deadline for the initial release notes draft, as seen in the 1.8 release timeline.  We in the release team are working hard to gather these notes sooner in the process so we can focus on quality and applicability to the Kubernetes user community. 

The process is for each SIG with a feature represented in the features repo, or those with user-impacting changes, to file pull requests against the draft, and check off their SIG name on the list when done.  The current applicable policy for release notes is here.  If you are in doubt of a particular feature making it into the release, please wait until we are closer to code freeze to add it.  We want to avoid a situation where the release notes inaccurately represent something that is not in the code.

As a reminder, release notes are not primarily for consumption by contributors.  They are a vital readout for users, administrators, and integrators of Kubernetes.  As such, these notes are fundamental to the bond of trust between the user community and the project.  

If you have questions or need further guidance please let me or anyone else on the release team know.  Remember that in many cases, the one-line feature description you have already written is sufficient so it's a low effort to get this work completed.  Jennifer or Radhika will be following up with SIGs directly in the coming days as well to fill in any gaps.  

Your help in this important matter is greatly appreciated!

All my best,

Jaice, 1.8 Release leader

[David Oppenheimer]

I assume the format we should use should look like was done in 1.7, i.e.

https://github.com/kubernetes/features/blob/master/release-1.7/release-notes-draft.md

?

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/CAJHHSLwCx45ZcVSDr2-HYzAo60RJ5fSO_tSe12Mg%2Bj8SkRmxoQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Jaice Singer DuMars]

Hi David,

 

That is correct.  I will add that we need to improve their overall readability and organization, per feedback from the retrospective.

 

All my best,

Jaice

On Monday, August 14, 2017 at 3:45:37 PM UTC-4, David Oppenheimer wrote:

I assume the format we should use should look like was done in 1.7, i.e.

https://github.com/kubernetes/features/blob/master/release-1.7/release-notes-draft.md

?

On Mon, Aug 14, 2017 at 11:04 AM, Jaice Singer DuMars <jdu...@gmail.com> wrote:

Hello community,

Tomorrow is the deadline for the initial release notes draft, as seen in the 1.8 release timeline.  We in the release team are working hard to gather these notes sooner in the process so we can focus on quality and applicability to the Kubernetes user community. 

The process is for each SIG with a feature represented in the features repo, or those with user-impacting changes, to file pull requests against the draft, and check off their SIG name on the list when done.  The current applicable policy for release notes is here.  If you are in doubt of a particular feature making it into the release, please wait until we are closer to code freeze to add it.  We want to avoid a situation where the release notes inaccurately represent something that is not in the code.

As a reminder, release notes are not primarily for consumption by contributors.  They are a vital readout for users, administrators, and integrators of Kubernetes.  As such, these notes are fundamental to the bond of trust between the user community and the project.  

If you have questions or need further guidance please let me or anyone else on the release team know.  Remember that in many cases, the one-line feature description you have already written is sufficient so it's a low effort to get this work completed.  Jennifer or Radhika will be following up with SIGs directly in the coming days as well to fill in any gaps.  

Your help in this important matter is greatly appreciated!

All my best,

Jaice, 1.8 Release leader

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.

To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.

[lu...@luxaslabs.com]

I thought this would be auto-generated in the first place from the features repo...?

And then we'd change those if something's wrong

But now we're aimed to add all the one-line feature release note lines there by ourselves?

Best Regards,

Lucas

[Jaice Singer DuMars]

Lucas,

Unfortunately the work to automate that has not taken place.  We understand this is a burden, and I'm sorry for that.  Hopefully we can concentrate some effort on finding the balance between early action, automation, and very selective human curation.  

Kindest regards,

Jaice