(Joseph Reynolds): Proposal to enhance the release process so that when a release is frozen (being readied for release) [Release Planning] will ask for advice from community members if that release is ready for release.
Expected activity might be:
The [Security Working Group] validate https and ssh security ciphers, and HTTP headers, etc. are as intended, for example compared with ever-changing industry standards.
The [Test Work Group] running tests against updated security items as well as overall function regression testing.
2.6 Content that didn't make it - Company reps status update
Release notes need a volunteer
Documentation, testing are priority until Feb 4th week, tagged as stable branch
2.7 Release requirements
How long do we maintain a release (back port critical defects)
12/31/18
No meeting (Happy New Year!)
12/17/18
Release freeze - Jan 7th - not a meeting week, do we want to resume weekly meetings in January?
Release validation prior to branch, 3 days to test for major problems, organize? Test team or company representatives check-off? Or "no-news-is-good-news" plan?
Release status - company representatives, please update status for contributed features, vital to test effort after freeze/branch
2.7 Features, initial load before end of 2.6 release
12/3/18
Release freeze - tabled conversation on what to do post freeze: branch/test or test/branch
Release tooling - infrastructure for branches, fixes, CI
Release plan status update:(Joseph for Sivas): The testing workgroup is using the release content spreadsheet to help ensure new features have function tests. We would like to use it to find completed designs and dates when code is available. However, some features have no WG lead listed, and we don't know what the designs are or what the test plans are. Are these features still in the release, or can we get the required information? What is the community practice here?