#4140 Installer images needed on 2010-10-07 for QA testing of task#44 - Pre-RC Acceptance Test Plan

Created 6 years ago by jlaska
Modified 4 months ago

NOTE: This ticket must be associated with ''Fedora 14 RC'' milestone, but that milestone does not yet exist in TRAC.

https://fedoraproject.org/wiki/Composing_test_images

According to the [http://poelstra.fedorapeople.org/schedules/f-14/f-14-quality-tasks.html QA schedule], QA will be testing a new anaconda build and running the [https://fedoraproject.org/wiki/QA:Rawhide_Acceptance_Test_Plan rawhide acceptance test plan] against the build. The new installer updates will be available in bodhi ''updates-testing''. In order to test and provide karma feedback, install images using that anaconda will be needed. The results of this testing will be published to test-announce @lists.fedoraproject.org and appropriate bodhi karma will be given to the updates.

This ticket requests creating one-off installer images for the QA team to verify a week prior to RC test compose. Images are needed for testing on Thu 2010-10-07.

Replying to [ticket:4140 jlaska]:

NOTE: This ticket must be associated with ''Fedora 14 RC'' milestone, but that milestone does not yet exist in TRAC.

FWIW, we don't have "create all tickets for Final release" scheduled until 2010-09-30. Maybe we should pull that date in?

Replying to [ticket:4140 jlaska]:

NOTE: This ticket must be associated with ''Fedora 14 RC'' milestone, but that milestone does not yet exist in TRAC.

FWIW, we don't have "create all tickets for Final release" scheduled until 2010-09-30. Maybe we should pull that date in?

In the event that the updated udev doesn't yet have appropriate bodhi stable karma, can bodhi update [https://admin.fedoraproject.org/updates/udev-161-3.fc14 udev-161-3.fc14] be used when creating these test images?

In the event that the updated udev doesn't yet have appropriate bodhi stable karma, can bodhi update [https://admin.fedoraproject.org/updates/udev-161-3.fc14 udev-161-3.fc14] be used when creating these test images?

Taking ticket. Grabbed the listed builds above.

Taking ticket. Grabbed the listed builds above.

Thanks Jesse, I believe we were only expecting boot.iso and pxeimages. But having install ISO's does let us validate several ON_QA blocker bugs.

Any chance you could rename the directory to avoid conflict with next weeks scheduled 'test compose' #1? Maybe TC0 :)

Thanks Jesse, I believe we were only expecting boot.iso and pxeimages. But having install ISO's does let us validate several ON_QA blocker bugs.

Any chance you could rename the directory to avoid conflict with next weeks scheduled 'test compose' #1? Maybe TC0 :)

why not just make next week test compose 2? I got confused as to what things were required for this ticket, and assumed it was test compose 1.

Changing the path might cause a tad bit of confusion and mirror churn right now. Next week, I could call it 14.TC1.1 ? :)

why not just make next week test compose 2? I got confused as to what things were required for this ticket, and assumed it was test compose 1.

Changing the path might cause a tad bit of confusion and mirror churn right now. Next week, I could call it 14.TC1.1 ? :)

Replying to [comment:10 jkeating]:

why not just make next week test compose 2? I got confused as to what things were required for this ticket, and assumed it was test compose 1.

Changing the path might cause a tad bit of confusion and mirror churn right now. Next week, I could call it 14.TC1.1 ? :)

There's only 1 mirror, right (sb1)?

Hrmm, fooy. I think we've already made things confusing. But maybe only I care. This isn't a big issue for now, as we don't yet have production tooling that relies on a particular format.

Replying to [comment:10 jkeating]:

why not just make next week test compose 2? I got confused as to what things were required for this ticket, and assumed it was test compose 1.

Changing the path might cause a tad bit of confusion and mirror churn right now. Next week, I could call it 14.TC1.1 ? :)

There's only 1 mirror, right (sb1)?

Hrmm, fooy. I think we've already made things confusing. But maybe only I care. This isn't a big issue for now, as we don't yet have production tooling that relies on a particular format.

4 months ago

Metadata Update from @jlaska:
- Issue assigned to jkeating
- Issue set to the milestone: Fedora 14 Final

Login to comment on this ticket.

cancel