On 12/02/2009 06:01 PM, Jesse Keating wrote:
On Wed, 2009-12-02 at 11:01 -0500, James Laska wrote:
> QA requires a bit more clarity on the process by which images will be
> requested and built ... and we'll then need to update the schedule to
> reflect these changes. I'm not comfortable hand-waving this process
> until later.
Currently the Installer team knows to ask me (email, irc, bat signal) to
produce images when they are ready for test. Many of that team know how
to produce images on their own for local testing, and thus far I have
only been contacted once, and that was for semi-private testing, not
wide scale testing.
Cant we use a "known to work" anaconda version to distribute with the
nightly-created live images or are we going to have to schedule test
day's around anaconda working that day or not?
Going forward, I would propose that we use the existing Test Day
framework to schedule and deliver images. Of course, test day is mostly
geared around live images, but our deliverable would be even smaller,
boot.iso. Hypothetically we can store this test day image in a path
that can remain live for a period of time, and be a reference for the
latest install images produced.
I propose we keep producing nightly-composes live iso and just use a
working anaconda installer or remove the option to install out of those
images then just install or the switch out that installer if the
anaconda team wants some install testing done...
Reducing the number of test days or having the ability for each SIG
pointing to a live iso to conduct some testing on their own is not the
way to go and certainly not making test days depended on the "installer"
working or not.
These images serve more purpose then just to check or test the