From: "akuster" <akuster808@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"Tummalapalli, Vineela" <vineela.tummalapalli@intel.com>,
"Jain, Sangeeta" <sangeeta.jain@intel.com>,
"Mittal, Anuj" <anuj.mittal@intel.com>,
akuster808 <akuster808@gmail.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>
Subject: Re: [yocto] QA Cycle report for build (yocto-3.0.2.rc2)
Date: Fri, 21 Feb 2020 10:24:41 -0800 [thread overview]
Message-ID: <85beff10-bb0a-0890-32cd-c7f77fa2e9f5@gmail.com> (raw)
In-Reply-To: <9b875592a194c843343d4a03593be519a87c2072.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
On 2/21/20 9:38 AM, Richard Purdie wrote:
> On Fri, 2020-02-21 at 17:26 +0000, Tummalapalli, Vineela wrote:
>> [Vineela]: So we will have 3.0.2.rc3 as the release candidate and not
>> 3.0.2.rc2 as we see issues with that. Am I correct?
>> If so, in terms of release process I just have to redo the things
>> like staging 3.0.2.rc3 and do the release notes and test report and
>> get it reviewed once I get the test results for 3.0.2.rc3 from QA
>> team.
> Yes, however the QA team aren't going to rerun all the tests, only
> check the issue which regressed is fixed.
>
> A new build did complete but a QA email wasn't sent out. Armin started
> that build so I'm not sure whether that was the plan or not (the build
> wasn't configured to). Armin?
I did't think a full QA round was needed. Bash ptest just needs to be
double checked.
openssh has a fix but will be in the next dot release.
- armin
>
> Cheers,
>
> Richard
>
>
>
[-- Attachment #2: Type: text/html, Size: 1803 bytes --]
next prev parent reply other threads:[~2020-02-21 18:24 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
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 [this message]
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=85beff10-bb0a-0890-32cd-c7f77fa2e9f5@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.