Recap and full IRC transcript found here:
http://fedoraproject.org/wiki/ReleaseEngineering/Meetings/2008-may-12
Please make corrections and clarifications to the wiki page.
== Preparing Fedora 9 ==
* The x86_64 DVD jigdo is busted due to our last minute respins on
Friday--need to hand edit newly created files
* Consider making jigdo tree verification an F10 feature
* Change permissions 40 minutes before release
time--https://fedorahosted.org/rel-eng/ticket/20
* Change the inheritance of ''dist-rawhide'' from ''f9-final'' to
''dist-f10''--https://fedorahosted.org/rel-eng/ticket/21
* Create .ini files for torrent
creator--https://fedorahosted.org/fedora-infrastructure/ticket/526
== Post Fedora 9 ==
* During our short "down" time before F10 alpha f13 would like to get
some things going
1. Better use of our Trac space
* closing out tickets on time
* tracking milestones and tasks
1. Start scoping tasks for summer intern
* Casey Dahlin (he's worked with notting in the past on things
like upstart)
* work on things lik new maintainer containment, tooling around
non-responsive maintainers, Trac gateway, and other potential things
like Kopers (Koji Personal Repos)
1. Tools
* sigul--signing server needs work and connection with koji
* pungi is going to inherit splittree and pkgorder from
anaconda-runtime; need to integrate the functionality of those into
pungi code
* more tooling around releng tasks and tree validation
1. Upgrade releng1 to RHEL5 from FC6
1. What to cover at FUDCon Boston
a. Start conversation about generation SCM (Source Control
Management)
* primary focus on requirements gathering and work flow
possibilities
a. SELinux vs. chroots discussion--see fedora-selinux-list
* f13 is planning to run for Fedora Board and if he secures a position
he would no longer represent Release Engineering on FESCo--would need a
replacement
== IRC Transcript ==
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
