From: "Alan W. Irwin" <irwin@beluga.phys.uvic.ca>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: Updated -next
Date: Sat, 21 Jan 2012 11:45:10 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1201211123140.13131@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <20120121141208.GA3821@phenom.ffwll.local>
On 2012-01-21 15:12+0100 Daniel Vetter wrote:
> drm-intel-testing is drm-intel-next and drm-intel-fixes merged together
> (as the time of when I've pushed things out). Gordon Jin said that he
> prefers to qa one single branch and that qa will take the job of finding
> out whether an issue has been introduced in -fixes or in -next. I agree
> that it makes more sense to test everything together, otherwise you'll
> miss some of the bugfixes in -fixes.
As an Intel graphics user whose number-one concern is stability, I
have to make a comment here. I fully appreciate that the top priority
for qa should be the cutting edge so that Intel developers get quick
feedback on their changes. But that leaves the -fixes branch untested
_on its own_ by qa, and I urge Gordon Jin to rethink that decision.
After all, the -fixes branch is quite important to the end user of
Intel graphics since it generally propagates sooner than
-intel-testing to the users. Also, doing qa for both -intel-testing
and -fixes should not double the burden on the qa group since -fixes
is much less volatile so doesn't have to be tested nearly as often as
-intel-testing.
In sum, my feeling is that if the -fixes branch is to have any
separate meaning at all, it has to go through the same qa process
(although not as often) as drm-intel-testing.
My $0.02.
Alan
__________________________
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________
Linux-powered Science
__________________________
next prev parent reply other threads:[~2012-01-21 19:54 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 10:10 Updated -next Daniel Vetter
2012-01-21 4:15 ` Sun, Yi
2012-01-21 14:12 ` Daniel Vetter
2012-01-21 19:45 ` Alan W. Irwin [this message]
2012-01-31 9:07 ` Jin, Gordon
2012-02-07 22:59 updated -next Daniel Vetter
2012-02-16 17:27 Daniel Vetter
2012-02-17 17:56 ` Jesse Barnes
2012-02-21 7:45 ` Sun, Yi
2012-03-01 20:59 Updated -next Daniel Vetter
2012-03-08 8:10 ` Sun, Yi
2012-03-18 21:20 ` Daniel Vetter
2012-03-23 10:03 Daniel Vetter
2012-03-29 7:38 ` Sun, Yi
2012-04-05 9:45 Daniel Vetter
2012-04-09 16:19 ` Daniel Vetter
2012-04-10 2:09 ` Sun, Yi
2012-04-11 3:20 ` Sun, Yi
2012-04-11 7:54 ` Paul Menzel
2012-04-11 8:24 ` Sun, Yi
2012-04-11 9:45 ` Paul Menzel
2012-04-21 16:40 Daniel Vetter
2012-04-23 7:39 ` Daniel Vetter
2012-04-23 7:40 ` Sun, Yi
2012-04-27 11:45 ` Daniel Vetter
2012-04-27 13:44 ` Daniel Vetter
2012-05-06 19:09 Daniel Vetter
2012-06-04 20:59 Daniel Vetter
2012-06-12 8:37 ` Daniel Vetter
2012-06-21 8:25 Daniel Vetter
2012-07-22 14:33 updated -next Daniel Vetter
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=alpine.DEB.2.00.1201211123140.13131@ybpnyubfg.ybpnyqbznva \
--to=irwin@beluga.phys.uvic.ca \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).