f13 informed the team about the upcoming rawhide rebuild to accomodate:

f13 informed the team about the upcoming rawhide rebuild to accomodate:

−

* New i686 architecture

+

* New i686 architecture

−

* New compression - see [[Features/XZRpmPayloads]]

+

* New compression - see [[Features/XZRpmPayloads]]

−

* New glibc and gcc

+

* New glibc and gcc

This change introduces a upgrade problem for testers already on rawhide -- see {{bz|513937}}. The team discussed how to document upgrading for current rawhide testers and concluded posting a guide to the http://rawhidewatch.wordpress.com blog was the best avenue. The current recommended upgrade procedure for testers already on rawhide is:

This change introduces a upgrade problem for testers already on rawhide -- see {{bz|513937}}. The team discussed how to document upgrading for current rawhide testers and concluded posting a guide to the http://rawhidewatch.wordpress.com blog was the best avenue. The current recommended upgrade procedure for testers already on rawhide is:

−

* Install ''rpm'' package from f11-updates repo

+

* Install ''rpm'' package from f11-updates repo

Jlaska took an action item to discuss with Warren.

Jlaska took an action item to discuss with Warren.

Line 109:

Line 109:

Viking_ice informed the team that no progress has been made on his fedora-infrastructure request for a QA blog. Viking_ice asked the team how they plan to inform people of QA activities.

Viking_ice informed the team that no progress has been made on his fedora-infrastructure request for a QA blog. Viking_ice asked the team how they plan to inform people of QA activities.

−

Adamw responded that currently, he, wwoods and jlaska have blogs that are aggregated on fedora planet and they blog about QA significant events. Viking_ice indicated a strong preference for an official QA blog.

+

Adamw responded that currently, he, wwoods and jlaska have blogs that are aggregated on fedora planet and they blog about QA significant events. Viking_ice indicated a strong preference for an official QA blog. Some discussion followed as to whether a dedicated QA wordpress instance, or an aggregated fedora planet QA feed would be the best solution in the short term.

−

Some discussion followed as to whether a dedicated QA wordpress instance, or an aggregated fedora planet QA feed would be the best solution in the short term.

Agenda

Previous meeting follow-up

[jlaska] - discuss ideas with fedora-infrastructure for getting test candidates out to testers

Jlaska spoke to mmcgrath about potential bandwith/performance problems. Mmcgrath indicated the system has been newly updated and he was not aware of any previous performance bottlenecks. Recommended continuing as planned with announcing the test images to fedora-test-list, and the infrastructure team will monitor alt.fedoraproject.org for any issues.

Alpha blocker bug day#3

In preparation for this Friday's blocker bug day#3, jlaska asked the group for volunteers to help announce and summarize the event (in accordance with the draft SOP [1]).

Whose got the ball(s)?

Poelcat agreed to send out a blocker bug meeting announcement

Adamw agreed to follow-up the meeting with a summary of actions

Jlaska challenged someone to bring some fun ascii art to the meeting, dpravec accepted the challenge

AutoQA update

Wwoods informed the team that 7 of 12 tests from the QA:Rawhide_Acceptance_Test_Plan are now automated. Will plans to announce recent changes through a combination of wiki documentation and blog posts. Wwoods was also debating enabling test results by email to increase visibility of test results until a production server is available.

Dpravec updated the group on testing status of the autotest package. The latest version appears to be missing a file which results in a failure. More infomation posted to https://fedorahosted.org/autoqa/ticket/9#comment:32. F13 plans to investigate the packaging failure soon.

Open discussion

Mass rebuild

f13 informed the team about the upcoming rawhide rebuild to accomodate:

This change introduces a upgrade problem for testers already on rawhide -- see RHBZ #513937. The team discussed how to document upgrading for current rawhide testers and concluded posting a guide to the http://rawhidewatch.wordpress.com blog was the best avenue. The current recommended upgrade procedure for testers already on rawhide is:

Install rpm package from f11-updates repo

Jlaska took an action item to discuss with Warren.

Test Day Live image script

Kparal notified the team that the current Test Day creation script (see QA/Test_Days/Live_Image) incorrectly uses Fedora 11 as a base repo. Jlaska indicated he has been secretly using a slightly modified version of the script for building test day images. Kparal was investigating updates to the recommended procedure to cleanly recommend using the rawhide package repo.

QA blogs request?

Viking_ice informed the team that no progress has been made on his fedora-infrastructure request for a QA blog. Viking_ice asked the team how they plan to inform people of QA activities.

Adamw responded that currently, he, wwoods and jlaska have blogs that are aggregated on fedora planet and they blog about QA significant events. Viking_ice indicated a strong preference for an official QA blog. Some discussion followed as to whether a dedicated QA wordpress instance, or an aggregated fedora planet QA feed would be the best solution in the short term.

| it's just a short note. those people building live images according to that script are in fact building images based on F11. Therefore I'm working on a best way how to modify it so that it is based on Rawhide

--- | zodbot has changed the topic to: Channel is used by various Fedora groups and committees for their regular meetings | Note that meetings often get logged | For questions about using Fedora please ask in #fedora | See http://fedoraproject.org/wiki/Meeting_channel for meeting schedule

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, and JBoss are trademarks or registered trademarks of
Red Hat, Inc. or its subsidiaries in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community
maintained site. Red Hat is not responsible for content.