From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Cruz, Libertad" <libertad.cruz@intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"Eggleton, Paul" <paul.eggleton@intel.com>,
"Jolley, Stephen K" <stephen.k.jolley@intel.com>,
"Zhang, Jessica" <jessica.zhang@intel.com>
Cc: "Cruz Alcaraz, Juan M" <juan.m.cruz.alcaraz@intel.com>
Subject: Re: QA cycle report for 2.4 M2 rc2
Date: Thu, 03 Aug 2017 11:19:20 +0100 [thread overview]
Message-ID: <1501755560.18633.157.camel@linuxfoundation.org> (raw)
In-Reply-To: <58D9E2E50A021A45AD740492365FCDC531ECAA4A@fmsmsx107.amr.corp.intel.com>
On Wed, 2017-08-02 at 17:55 -0700, Cruz, Libertad wrote:
> QA does not approve that the workarounds provided for 2.4 m2 rc2
> were on different commits. Testing was not limited to 2.4 m2 rc2
> commit “8e15e9b6e478f6368034519b2a8fd3c7ea71d23b” it was performed by
> following each commit on the provided workarounds described below.
Thanks Libertad.
The different commits wasn't intentional, there were bugs which were
reported and fixed after rc2 was built. It made sense to resolve those
bugs as fixed in master but obviously they were still present in M2.
Given the high volume of issues and other things that went on with rc2
I've decided to build an rc3. We'll have to take current master as
there are some many fixes it only makes sense to use that rather than
create any special branch. I've set that build away.
Cheers,
Richard
prev parent reply other threads:[~2017-08-03 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 0:55 QA cycle report for 2.4 M2 rc2 Cruz, Libertad
2017-08-03 10:19 ` Richard Purdie [this message]
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=1501755560.18633.157.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jessica.zhang@intel.com \
--cc=juan.m.cruz.alcaraz@intel.com \
--cc=libertad.cruz@intel.com \
--cc=paul.eggleton@intel.com \
--cc=stephen.k.jolley@intel.com \
--cc=yocto@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.