Fedora Release Engineering Meeting Recap 2008-10-13

[John Poelstra]

Recap and full IRC transcript found here:
https://fedoraproject.org/wiki/ReleaseEngineering/Meetings/2008-oct-13

Please make corrections and clarifications to the wiki page.

== F10 Snapshot 1 ==
* regression in installer so no DVDs
** cd-rom media testing fix didn't make it and dhcp was broken again
* 500 tracked downloads of live images
* concerns about torrent performance
* DECISION: f13 will work with dgilmore and nirik to get additional 
seeders in place for the next snapshot release

== F10 Snapshot 2 ==
* Goes out end of this week
* ACTIONS:
*# create F10Snap2 tracker
*# migrage F10Snap1 issues to F10Snap2
*# produce full install tree and get pre-testing on it

== Package Signing ==
* rough sketch of signing appliance:
** Networkless appliance connected via serial/usb/whatever
** Send data to system, it returns signature for data from given key
** Use of multilevel pins, one for admin, one for use of keys
** Upload new firmware via usb/serial, not network.
** Interact with gnupg and one I'm still not quite sure about
** Sign binaries approved to use in automated ways with system for signing
** In essence we need a box that isn't connected to anything else but 
our signing host
* ACTIONS:
*# f13 to document current setup
*# sgrubb to coordinate resources to start scoping out
*# sgrubb to rediscuss at next meeting

== MinGW Repos ==
* reviewed the amount of work necessary to support MinGW built packages 
in their own repo and determine whether it's "worth" the work
* built packages are installable and usable under fedora (with wine, or 
if you're compiling something that BuildRequires them)
** example: 
http://camltastic.blogspot.com/2008/10/mingw-compile-software-for-windows.html 

* CONCLUSION:
** A lot of work to get these packages in their own repo with little 
perceived benefit
** Report back to Fedora Board:
*#Release Engineering believes the return on investment for making a 
separate repo for MinGW built packages is too low and the amount of work 
too high at the present time.
*#Release Engineering believes this issue would be worth revisiting in 
the future if space becomes an issue in the future

== Open Discussion ==
* See IRC Transcript

== IRC Transcript ==