Re: QA Cycle report for build (yocto-3.0.2.rc2)
On 2/20/20 2:44 PM, Richard Purdie wrote:
Works for me.I discussed this quickly in bug triage today with Armin. We agreed that: * The openssh bug is minor and doesn't affect release * Anuj resolved one of the bugs as being execution error so again it doesn't affect release * The bash issue does affect release We're proposing we build and release an rc3 with the bash CVE reverted. This would also include the bitbake memory optimisation during parsing which merged. We wouldn't rerun the manual QA for rc3, just check the automated test results. Does anyone have any objection to that? If not, QA should see an rc3 email but we're just expecting to check the test results if that works for everyone?
Vineela: Not sure how this affects release process, we'll just have to figure that out.
List them as Known issues?