From: "akuster" <akuster808@gmail.com>
To: "Jain, Sangeeta" <sangeeta.jain@intel.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
"Mittal, Anuj" <anuj.mittal@intel.com>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Cc: "otavio@ossystems.com.br" <otavio@ossystems.com.br>,
"yi.zhao@windriver.com" <yi.zhao@windriver.com>,
"Sangal, Apoorv" <apoorv.sangal@intel.com>,
"Yeoh, Ee Peng" <ee.peng.yeoh@intel.com>,
"Chan, Aaron Chun Yew" <aaron.chun.yew.chan@intel.com>,
"sjolley.yp.pm@gmail.com" <sjolley.yp.pm@gmail.com>,
"Tummalapalli, Vineela" <vineela.tummalapalli@intel.com>
Subject: Re: [yocto] QA Cycle report for build (yocto-3.0.2.rc2)
Date: Fri, 21 Feb 2020 07:37:39 -0800 [thread overview]
Message-ID: <319e2791-cbe7-e933-69f3-ec24d55211a3@gmail.com> (raw)
In-Reply-To: <CY4PR11MB1879171E8B31BE73AEE8CEE2E3120@CY4PR11MB1879.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2268 bytes --]
Jain,
On 2/20/20 5:57 PM, Jain, Sangeeta wrote:
>
>
>
>
>
> *From:*akuster <akuster@mvista.com>
> *Sent:* Friday, 21 February, 2020 7:01 AM
> *To:* Richard Purdie <richard.purdie@linuxfoundation.org>; Jain,
> Sangeeta <sangeeta.jain@intel.com>; Mittal, Anuj
> <anuj.mittal@intel.com>; akuster808 <akuster808@gmail.com>;
> yocto@lists.yoctoproject.org
> *Cc:* otavio@ossystems.com.br; yi.zhao@windriver.com; Sangal, Apoorv
> <apoorv.sangal@intel.com>; Yeoh, Ee Peng <ee.peng.yeoh@intel.com>;
> Chan, Aaron Chun Yew <aaron.chun.yew.chan@intel.com>;
> sjolley.yp.pm@gmail.com; Tummalapalli, Vineela
> <vineela.tummalapalli@intel.com>
> *Subject:* Re: [yocto] QA Cycle report for build (yocto-3.0.2.rc2)
>
>
>
>
>
> On 2/20/20 2:44 PM, Richard Purdie wrote:
>
> 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?
>
> Works for me.
>
> Sound good from QA perspective. Verifying automated test results and
> ptest results should be good.
Zeus-rc3 finished. the QA email failed to send.
- armin
>
>
>
>
>
>
>
> Vineela: Not sure how this affects release process, we'll just have to
>
> figure that out.
>
>
> List them as Known issues?
>
> Release should be done on rc3. Status of bugs can be updated in
> ‘header-intel.txt’. Just my thoughts!
>
>
>
> - armin
>
>
>
>
>
> Cheers,
>
>
>
> Richard
>
>
>
>
>
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 8899 bytes --]
next prev parent reply other threads:[~2020-02-21 15:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 7:33 QA Cycle report for build (yocto-3.0.2.rc2) Sangeeta Jain
2020-02-19 22:41 ` akuster
2020-02-19 22:42 ` Richard Purdie
2020-02-19 22:58 ` [yocto] " Khem Raj
2020-02-20 3:34 ` Anuj Mittal
2020-02-20 6:28 ` Sangeeta Jain
2020-02-20 22:44 ` Richard Purdie
2020-02-20 23:01 ` Armin Kuster
2020-02-21 1:57 ` Sangeeta Jain
2020-02-21 15:37 ` akuster [this message]
2020-02-24 2:10 ` Sangeeta Jain
2020-02-21 8:03 ` Adrian Bunk
2020-02-21 13:18 ` Richard Purdie
2020-02-21 17:26 ` Vineela
2020-02-21 17:38 ` Richard Purdie
2020-02-21 18:24 ` akuster
2020-02-24 2:13 ` Sangeeta Jain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=319e2791-cbe7-e933-69f3-ec24d55211a3@gmail.com \
--to=akuster808@gmail.com \
--cc=aaron.chun.yew.chan@intel.com \
--cc=anuj.mittal@intel.com \
--cc=apoorv.sangal@intel.com \
--cc=ee.peng.yeoh@intel.com \
--cc=otavio@ossystems.com.br \
--cc=richard.purdie@linuxfoundation.org \
--cc=sangeeta.jain@intel.com \
--cc=sjolley.yp.pm@gmail.com \
--cc=vineela.tummalapalli@intel.com \
--cc=yi.zhao@windriver.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.