Jolley, Stephen K
2018-11-14 20:47:46 UTC
We will release YP 2.6 M4 rc1 shortly. Please give feedback if any is required.
Thanks,
Stephen
From: Graydon, Tracy
Sent: Wednesday, November 14, 2018 12:33 PM
To: Jolley, Stephen K <***@intel.com>; Michael Halstead <***@linuxfoundation.org>
Subject: final pass on release notes....and general status of readiness
Ugh, I am not seeing the email I sent with the finalized release notes. I dunno if I sent it or not because I am having a nightmare with Outlook on Mac eating things and generally not working right.
So, by way of sanity check, attached. The only changes were adding the binutils CVES to Known issues:
binutils: fix CVE-2018-18309, CVE-2018-18605, CVE-2018-18606, CVE-2018-18607
And the gitsm known issue:
- gitsm fixes on master-next:
* The submodule name and path were assumed to be the same, which is not necessarily true.
* Submodules refer to a specific commit, not branch, but we erroneously check against the branch specified in SRC_URI. This results in
failure if a submodule commit is not on that branch.
So, nothing major there. Just really a sanity check on the gitsm wording.
Everything is ready to go. Pages are set and just need to be published. Release announcement is ready. So we just need to do the final mirror and tagging magic, and announce.
If the wording on gitsm issue looks reasonable, we are good to go.
-t
Thanks,
Stephen
From: Graydon, Tracy
Sent: Wednesday, November 14, 2018 12:33 PM
To: Jolley, Stephen K <***@intel.com>; Michael Halstead <***@linuxfoundation.org>
Subject: final pass on release notes....and general status of readiness
Ugh, I am not seeing the email I sent with the finalized release notes. I dunno if I sent it or not because I am having a nightmare with Outlook on Mac eating things and generally not working right.
So, by way of sanity check, attached. The only changes were adding the binutils CVES to Known issues:
binutils: fix CVE-2018-18309, CVE-2018-18605, CVE-2018-18606, CVE-2018-18607
And the gitsm known issue:
- gitsm fixes on master-next:
* The submodule name and path were assumed to be the same, which is not necessarily true.
* Submodules refer to a specific commit, not branch, but we erroneously check against the branch specified in SRC_URI. This results in
failure if a submodule commit is not on that branch.
So, nothing major there. Just really a sanity check on the gitsm wording.
Everything is ready to go. Pages are set and just need to be published. Release announcement is ready. So we just need to do the final mirror and tagging magic, and announce.
If the wording on gitsm issue looks reasonable, we are good to go.
-t