From Fedora Project Wiki

Fedora Release Engineering Meeting :: Monday 21-MAY-2007


  • f13
  • looks like Bill managed to get pungi to run on it, awesome. We now have installable rawhide.
  • just did a pungi spin using the static-repos and that seems to be going swimmingly
  • latest rawhide should include mdraid fixes
  • wwoods
  • there's some selinux bogons in the current policy that I'm chasing.. notable is the fact that semodule -i seems a bit broken 13:14 < wwoods> which is bad, since that's basically how we tell people to work around *other* selinux problems
  • iwl3945 wireless
  • linville committed some fixes for it and is looking at it more today
  • doesn't blowup machines any more, but needs more testing
  • jeremy plans to look into it a little more

F7 Blocker Status

  • blocker list is down to 45 at the moment
  • wwoods
  • believe that mdraid is higher priority than iwl3945 because it keeps people from being able to install/upgrade, especially people who are using RAID on IDE drives in FC6 - i.e. people who have been with us a while. the hard-core folx we wanna keep.
  • mdraid and dmraid account for.. I think 10 bugs?
  • gaim/pidgin-libnotify is two more bugs
  • bz 212781 the installer-hang-on-lowmem machines will need a release note if there isn't an obvious fix
  • gotta ask chip why this "symlink from /etc/alternatives/emacs to /usr/bin/emacs is not created." bug is on the blocker
  • f13 will look through blocker list
  • nirik
  • bz 240334 ... needs to get fluidsynth-devel
  • due to extras not being built for ppc64 before the merge...
  • fixing 240334 will get 2 bugs off the blocker list
  • kernel update from davej
  • alan posted a bunch of ata patches today that I'm going to suck up this afternoon
  • i'm sitting on a bunch of patches to fix up some more suspend regressions
  • .21.2 still hasn't landed but will soon
  • linville is working on wireless stuff
  • magic 8 ball says "outlook promising" wrt to having a good enough kernel for release by Thu/Fri

Release Notes

  • need to be built; currently building fine from cvs
  • stickster will sync up with f13
  • consider adding release notes to master schedule in the future or merging docs schedule with master schedule

Preparing RC (Release Candidate)

  • fedora-release need to be rebuilt once we have a final name
  • f13 punts naming task to notting
  • release notes need to be built

Plan to reach GA

  • 24-MAY signed package RC1 created
  • 24-MAY RC1 made torrentable
  • 26-MAY RC2 planned respin for any fixes that we've been able to find necessary and make.
  • 26-MAY hand RC2 to Red Hat IS to start syncing for public availability
  • 28-MAY confirm trees are GA worthy (if answer is "NO," GA date slips)
  • 29-MAY begin sync to mirrors (takes 48 hours)
  • 31-MAY GA

Status of Bodhi

  • Per lmacken he's really close.
  • A few unspecified things need help

IRC Transcript

f13 changed the topic of #fedora-meeting to: Fedora Release Team Meeting<a href="#t12:59" class="time">12:59</a>
f13happy Monday all.<a href="#t13:00" class="time">13:00</a>
wwoodswelcome to thunderdome<a href="#t13:01" class="time">13:01</a>
XulChrislol<a href="#t13:01" class="time">13:01</a>
rdietermerry mood monday.<a href="#t13:01" class="time">13:01</a>
ivazquezHooray for the two-four long weekend.<a href="#t13:01" class="time">13:01</a>
mmcgrathhappy monday<a href="#t13:01" class="time">13:01</a>
f13jwb_gone: rdieter: warren: ping<a href="#t13:01" class="time">13:01</a>
warrenhey<a href="#t13:01" class="time">13:01</a>
f13hrm, no notting.<a href="#t13:01" class="time">13:01</a>
rdieterhere<a href="#t13:01" class="time">13:01</a>
rdieterno summon the notting incantation today?<a href="#t13:02" class="time">13:02</a>
f13rdieter: sms sent.<a href="#t13:02" class="time">13:02</a>
rdieterthat works too<a href="#t13:03" class="time">13:03</a>
f13well, I suppose we can start without him.<a href="#t13:05" class="time">13:05</a>
mmcgrath<nod><a href="#t13:09" class="time">13:09</a>
f13First up, Rawhide.  Looks like Bill managed to get pungi to run on it, awesome.  We now have installable rawhide.<a href="#t13:09" class="time">13:09</a>
f13don't look to closely at how it happens, you'll likely need 'air discomfort' bags.<a href="#t13:09" class="time">13:09</a>
f13unfortunately, the latest rawhide has an anaconda bug that is fixed already.<a href="#t13:09" class="time">13:09</a>
f13wwoods: if it _were_ installable, would we be getting automated test results out of it?<a href="#t13:09" class="time">13:09</a>
wwoodsnot automagically, but if I sync a tree somewhere local I can fire some off<a href="#t13:09" class="time">13:09</a>
f13ok.<a href="#t13:09" class="time">13:09</a>
f13your stuff needs gridtrees to get modified in order to have it automagic right?<a href="#t13:09" class="time">13:09</a>
wwoodsunfortunately the old KATE infrastructure is all triggered by brew/distill composes.. yeah<a href="#t13:09" class="time">13:09</a>
f13k.  Something to visit post F7 I think.<a href="#t13:09" class="time">13:09</a>
wwoodsI can manually kick off the stuff that it would do automatically, but I need to make sure the tree is local<a href="#t13:09" class="time">13:09</a>
f13right.<a href="#t13:09" class="time">13:09</a>
wwoodsI'm not sure we have magical syncing of the koji-built rawhide to anywhere in RDU yet<a href="#t13:10" class="time">13:10</a>
wwoodsit's definitely high on my list for post-f7 stuff<a href="#t13:10" class="time">13:10</a>
f13the good news is that I just did a pungi spin using the static-repos and that seems to be going swimmingly<a href="#t13:10" class="time">13:10</a>
f13wwoods: it's in RDU by nature of the netapps.  But it's not on curly<a href="#t13:10" class="time">13:10</a>
f13I'm going to check in my pungi configs to the releng git module<a href="#t13:11" class="time">13:11</a>
f13soon I'll also do another build of pungi with the configs for F7 in it so that folks can repeat what they're doing.<a href="#t13:11" class="time">13:11</a>
f13er we're.<a href="#t13:11" class="time">13:11</a>
wwoodshmm.. where on the netapp?<a href="#t13:11" class="time">13:11</a>
wwoodswe can talk about this later<a href="#t13:12" class="time">13:12</a>
f13wwoods: it's on a different netapp, the Fedora ones.  rsync://<a href="#t13:12" class="time">13:12</a>
f13(only works internally)<a href="#t13:12" class="time">13:12</a>
wwoodscool. I need to sync it somewhere that's doing http/ftp exporting as well, but once that's done I'll get some KATE juju going<a href="#t13:12" class="time">13:12</a>
f13wwoods:<a href="#t13:13" class="time">13:13</a>
f13(has http, not sure about ftp)<a href="#t13:13" class="time">13:13</a>
f13Anywho, tonight's rawhide should be pretty good, unless more breakage is introduced, but since we're watching what gets tagged I think we can be aware.<a href="#t13:14" class="time">13:14</a>
wwoodsthere's some selinux bogons in the current policy that I'm chasing.. notable is the fact that semodule -i seems a bit broken<a href="#t13:14" class="time">13:14</a>
wwoodswhich is bad, since that's basically how we tell people to work around *other* selinux problems<a href="#t13:14" class="time">13:14</a>
jeremywhoops, sorry.  I'm here now<a href="#t13:15" class="time">13:15</a>
f13wwoods: ok, good to know.<a href="#t13:15" class="time">13:15</a>
f13jeremy: any comments on the subject of rawhide?<a href="#t13:15" class="time">13:15</a>
wwoodsAm I right in thinking that tomorrow's rawhide push should include all the mdraid fixes we've been waiting to test?<a href="#t13:16" class="time">13:16</a>
jeremy"whoops" on the fact that it was broken, but should be better now ;)<a href="#t13:16" class="time">13:16</a>
jeremywwoods: hoping so<a href="#t13:16" class="time">13:16</a>
f13hopefully we can get the anaconda build done early enough to do another pungi spin off the hot repo to see if it still works (:<a href="#t13:17" class="time">13:17</a>
jeremywwoods: I'm in the process of testing stuff cobbled together now<a href="#t13:17" class="time">13:17</a>
* f13 sees mkinitrd build finished<a href="#t13:17" class="time">13:17</a>
wwoodsjeremy: awesomesauce<a href="#t13:18" class="time">13:18</a>
jeremyf13: yeah, tag request coming soon.  just testing it with the upgrade I just did from fc6 mdraid on ide<a href="#t13:18" class="time">13:18</a>
f13nod<a href="#t13:18" class="time">13:18</a>
* rdieter needs to start writing down all the words wwoods invents daily...<a href="#t13:18" class="time">13:18</a>
f13Ok, wwoods how about a blocker update?<a href="#t13:18" class="time">13:18</a>
warrenWhat is our F7 release plan for kernel... especially iwl3945<a href="#t13:18" class="time">13:18</a>
rdieter1.  awesomesauce.<a href="#t13:18" class="time">13:18</a>
warrenIs iwl3945 at least no longer dangerous?  (oops, dead keyboard, etc.)<a href="#t13:18" class="time">13:18</a>
wwoodsblockerlist is down to 45 at the moment (keep in mind that includes a couple empty blocker bugs, so.. yeah)<a href="#t13:19" class="time">13:19</a>
wwoodswarren: it doesn't on my hardware, but I'll need to hear some more opinions on that<a href="#t13:19" class="time">13:19</a>
wwoodslinville committed some fixes for that<a href="#t13:19" class="time">13:19</a>
jeremynot fully there, he's working more today<a href="#t13:19" class="time">13:19</a>
jeremymy plan was to spend the day on 3945 prodding, but got suckered into raid stuff instead<a href="#t13:20" class="time">13:20</a>
wwoodseven if it's not rock-solid it shouldn't be blowin' up machines anymore<a href="#t13:20" class="time">13:20</a>
bpepplewarren: I've had good luck with it.<a href="#t13:20" class="time">13:20</a>
wwoodsI'd like to offer the opinion that mdraid is higher priority, just because it keeps people from being able to install/upgrade<a href="#t13:20" class="time">13:20</a>
f13wwoods: anything super scary in those 44?<a href="#t13:20" class="time">13:20</a>
wwoodsespecially people who are using RAID on IDE drives in FC6 - i.e. people who have been with us a while. the hard-core folx we wanna keep.<a href="#t13:21" class="time">13:21</a>
f13people we don't want to regress?<a href="#t13:21" class="time">13:21</a>
jeremywwoods: on the plus side, that's looking close to good now.  so I may be able to get to 3945 in an hour or so<a href="#t13:21" class="time">13:21</a>
wwoodsf13: the super-scary stuff was mdraid / dmraid, and we are bustin' down doors on those right now<a href="#t13:21" class="time">13:21</a>
f13k<a href="#t13:21" class="time">13:21</a>
jeremyand linville is already looking at 3945 today<a href="#t13:21" class="time">13:21</a>
wwoodsmdraid and dmraid account for.. I think 10 bugs?<a href="#t13:22" class="time">13:22</a>
f13maybe once I get updates pushed, pungi configs committed, more packages signed, I'll look through the 44.<a href="#t13:22" class="time">13:22</a>
wwoodssome very large chunk of the list<a href="#t13:22" class="time">13:22</a>
wwoodsI'm not sure what's going on with the ppc64 / dep-rebuild stuff anymore<a href="#t13:22" class="time">13:22</a>
f13I'm through the perl modules in signing, still need to write the signed ones out.<a href="#t13:23" class="time">13:23</a>
nirikthere is only one left I think...<a href="#t13:23" class="time">13:23</a>
f13well, still need to see if koji won't barf on importing all these signatures too.<a href="#t13:23" class="time">13:23</a>
warrennew kernel build with another 3945 change is coming<a href="#t13:23" class="time">13:23</a>
niriklisten needs something thats not in .ppc64<a href="#t13:23" class="time">13:23</a>
f13nirik: only one?  that sounds really really good, almost too good<a href="#t13:23" class="time">13:23</a>
nirik240334 ... needs to get fluidsynth-devel<a href="#t13:24" class="time">13:24</a>
nirikI think notting cleared up almost all of those with importing... if someone could import fluidsynth-devel that would be groovy.<a href="#t13:24" class="time">13:24</a>
warrenis that in fedora-cvs queue?<a href="#t13:25" class="time">13:25</a>
f13no, it may be built on mightor just needs to be imported, not sure.  I'll poke around on mightor<a href="#t13:26" class="time">13:26</a>
nirikwarren: no, this is due to extras not being built for ppc64 before the merge...<a href="#t13:26" class="time">13:26</a>
warrenoh<a href="#t13:27" class="time">13:27</a>
f13nirik: hrm, probably going to have to wait for notting on that one, not sure what's going on with it and I don't see it anywhere obvious on mightor<a href="#t13:28" class="time">13:28</a>
nirikyeah, no worries. That will knock 2 off the blocker list (that listen rebuild bug, and the ppc64 blocker)<a href="#t13:28" class="time">13:28</a>
wwoodsgaim/pidgin-libnotify is two more bugs<a href="#t13:29" class="time">13:29</a>
wwoodsthere's some ancient kernel bugs in NEEDINFO since 2006<a href="#t13:29" class="time">13:29</a>
wwoodsthe installer-hang-on-lowmem machines will need a release note if there isn't an obvious fix<a href="#t13:30" class="time">13:30</a>
wwoods(212781)<a href="#t13:30" class="time">13:30</a>
f13k.<a href="#t13:31" class="time">13:31</a>
wwoodsespecially since the "lowmem" threshold is like.. >256MB?<a href="#t13:31" class="time">13:31</a>
* davej appears<a href="#t13:31" class="time">13:31</a>
f13davej: hey!  want to hook us up with some kernel news?<a href="#t13:31" class="time">13:31</a>
davejit doesn't suck as much as it used to. but it still sucks.<a href="#t13:32" class="time">13:32</a>
jeremypoelcat: can we get that in the minutes? ;-)<a href="#t13:32" class="time">13:32</a>
davejalan posted a bunch of ata patches today that I'm going to suck up this afternoon<a href="#t13:32" class="time">13:32</a>
davejand I'm sitting on a bunch of patches to fix up some more suspend regressions<a href="#t13:32" class="time">13:32</a>
davej.21.2 still hasn't landed but is 'soon' aparently.<a href="#t13:32" class="time">13:32</a>
davejand err, that's about it I think.<a href="#t13:32" class="time">13:32</a>
davejwireless stuff I'm a bit out of the loop on, I've left linville to try to beat sanity into that<a href="#t13:33" class="time">13:33</a>
f13davej: how confident do you feel that we'll have a good enough kernel for release by Thu/Fri?<a href="#t13:33" class="time">13:33</a>
davejmagic 8 ball says "outlook promising"<a href="#t13:33" class="time">13:33</a>
wwoodsI gotta ask chip why this "symlink from /etc/alternatives/emacs to /usr/bin/emacs is not created." bug is on the blocker<a href="#t13:33" class="time">13:33</a>
wwoodswarren: on your system where you reported the 'wmaster0 gets stuck forever' bug - did it actually get stuck *forever*?<a href="#t13:34" class="time">13:34</a>
warrenwwoods, 10 minutes was the longest I let it sit<a href="#t13:35" class="time">13:35</a>
f13wwoods: hard to say that, since forever hasn't come and gone.<a href="#t13:35" class="time">13:35</a>
wwoodstrue! heh<a href="#t13:35" class="time">13:35</a>
jimaf13: yeah, i was thinking that was a pretty hard thing to test for.<a href="#t13:35" class="time">13:35</a>
wwoods10 minutes is sufficiently close to infinity for this case<a href="#t13:35" class="time">13:35</a>
warrenwwoods, I thought notting fixed that in kudzu<a href="#t13:35" class="time">13:35</a>
wwoodswarren: yeah, we shouldn't be ifup'ing wmaster* at all anymore<a href="#t13:36" class="time">13:36</a>
jeremyyeah, kudzu in today's rawhide should have the fix<a href="#t13:36" class="time">13:36</a>
wwoodsbut I wanted to be sure to keep that bug around for later investigation if there was actually some weirdo condition where dhclient would hang indefinitely<a href="#t13:36" class="time">13:36</a>
nirikalthough the ipw3945 (that we don't ship, with the daemon) does use wmaster0 by default.<a href="#t13:36" class="time">13:36</a>
warrenwwoods, if the driver isn't behaving well it is possible<a href="#t13:37" class="time">13:37</a>
poelcatwhat date are we targeting for an RC?<a href="#t13:39" class="time">13:39</a>
wwoodsI don't know how much time we traditionally dedicate to that<a href="#t13:39" class="time">13:39</a>
f13poelcat: THursday<a href="#t13:40" class="time">13:40</a>
jeremypoelcat: I think we're currently in "whack down blockers and compose trees until we're happy" mode really<a href="#t13:40" class="time">13:40</a>
f13yeah<a href="#t13:40" class="time">13:40</a>
f13if we are still somewhat doomed by Monday / Tuesday, we're going to have to slip<a href="#t13:41" class="time">13:41</a>
wwoodsI'd like it if we could have an RC by thursday, where "RC" is defined as "something that probably has fixes for all the blockers"<a href="#t13:41" class="time">13:41</a>
wwoodstwo days to test the heck out of it, respin when we find the inevitable bugs, two more days to test that candidate<a href="#t13:42" class="time">13:42</a>
f13well.<a href="#t13:42" class="time">13:42</a>
wwoodsand if all goes well, that'd give us blessed trees on the 29th. maybe?<a href="#t13:42" class="time">13:42</a>
f13we don't have that many days if we want to be able to GA on the 31st.<a href="#t13:42" class="time">13:42</a>
f13mirrors need 48~ hours or more to sync up<a href="#t13:43" class="time">13:43</a>
f13especially this time around when we're changing the layout on them.<a href="#t13:43" class="time">13:43</a>
poelcatright so it seems we have to have an RC on Thursday or we slip<a href="#t13:43" class="time">13:43</a>
jeremyat which point, we better get mspevack some good armor :-P<a href="#t13:43" class="time">13:43</a>
EvilBoblol<a href="#t13:43" class="time">13:43</a>
f13no kidding.<a href="#t13:44" class="time">13:44</a>
wwoodsf13: I guess I was counting on testing over the weekend<a href="#t13:44" class="time">13:44</a>
wwoodsstupid calendar thingy. color those days where I"m not supposed to work differently!<a href="#t13:44" class="time">13:44</a>
warrenjeremy, how often are live images generated, and where do I find them?<a href="#t13:44" class="time">13:44</a>
f13wwoods: my point was that we have to give something to mirrors by Tuesday or we're slipping<a href="#t13:44" class="time">13:44</a>
nirikQuery: on those python packages that were linked against static libpython, should those be rebuilt? or is that not a blocker?<a href="#t13:44" class="time">13:44</a>
f13Tuesday is cutting it close too.<a href="#t13:44" class="time">13:44</a>
f13nirik: not a blocker.  They can be issued as updates.  I'd rahter not see a bunch of flux at this point<a href="#t13:45" class="time">13:45</a>
jeremywarren: they're generated "when I do them".  and they go up via torrent and I also keep a copy of them on my workstation<a href="#t13:45" class="time">13:45</a>
nirikf13: ok, cool. Someone should reply to that thread about it... one of the maintainers was asking this weekend if they should rebuild now or not.<a href="#t13:45" class="time">13:45</a>
wwoodsf13: right, so I'm saying if we have an RC on the 24th, allocate two days for testing (25-26) then the inevitable respin (26), two more days of testing (27-28), final go-ahead would be on the 29th<a href="#t13:45" class="time">13:45</a>
f13wwoods: "final go ahead" sounds like "hand it to mirrors"<a href="#t13:46" class="time">13:46</a>
f13it would have to be early 29th.<a href="#t13:46" class="time">13:46</a>
wwoodsyeah<a href="#t13:47" class="time">13:47</a>
poelcatthat doesn't seem like enough time to me... overly optimistic :)<a href="#t13:47" class="time">13:47</a>
f13poelcat: welcome to Fedora (:<a href="#t13:47" class="time">13:47</a>
wwoodsso other than "testing all through the long weekend" and "only have time for two release candidates", y'know, maybe that plan could work<a href="#t13:47" class="time">13:47</a>
* poelcat has not had enough kool-aid yet ;-)<a href="#t13:47" class="time">13:47</a>
f13wwoods: personally, I'd rather do the respon on the 26th, hand it to IS to start syncing, and then tell them to 'go' when we think it's good.  pre-sync for the win.<a href="#t13:48" class="time">13:48</a>
wwoodsoh, presync is fine<a href="#t13:48" class="time">13:48</a>
f13wwoods: every rawhide could be considered a RC really<a href="#t13:48" class="time">13:48</a>
wwoodssure, we can call the trees candidates<a href="#t13:48" class="time">13:48</a>
warrenIf we want test exposure of the installable discs, we should make it widely available on the 26th<a href="#t13:49" class="time">13:49</a>
warrenor sooner<a href="#t13:49" class="time">13:49</a>
f13yeah<a href="#t13:49" class="time">13:49</a>
wwoodsyeah, I'd like to have images available for testers by the 25th<a href="#t13:49" class="time">13:49</a>
f13not entirely sure where to stash it, but I'll find a place.<a href="#t13:50" class="time">13:50</a>
wwoodsideally the 24th<a href="#t13:50" class="time">13:50</a>
warrencall it "RC" and possibly final if it turns out to be perfect<a href="#t13:50" class="time">13:50</a>
f13hopefully I can have all packages signed and written out by tomorrow.<a href="#t13:50" class="time">13:50</a>
warren(haha)<a href="#t13:50" class="time">13:50</a>
jeremyf13: bittorrent!<a href="#t13:50" class="time">13:50</a>
wwoodsbittorrent's good for that stuff<a href="#t13:50" class="time">13:50</a>
f13once packages are signed/written, we're much more closer to that mythical 'RC' stage.  Especially since mash will be picking up those signed packages.<a href="#t13:50" class="time">13:50</a>
f13jeremy: yeah, that was my plan<a href="#t13:50" class="time">13:50</a>
f13Ok.  We should wrap up.  I was hoping to get an update from lmacken on bodhi but alas...<a href="#t13:52" class="time">13:52</a>
f13Open floor, any topics?<a href="#t13:52" class="time">13:52</a>
wwoodsdo you think we can get a big signed-package RC by the 24th, with fixes for.. at least *nearly* all of the blockers? is that the plan?<a href="#t13:52" class="time">13:52</a>
jeremywe do need something of an ETA on bodhi being operational<a href="#t13:52" class="time">13:52</a>
poelcatcan someone recap the dates/stages we decided on?<a href="#t13:53" class="time">13:53</a>
f13jeremy: I talked with lmacken, he's really close.  THere is just a last few things that he needs some help with.<a href="#t13:53" class="time">13:53</a>
f13poelcat: signed package RC spun on the 24th, hopefully made torrentable on teh same day.<a href="#t13:53" class="time">13:53</a>
f13poelcat: planned respin on Sunday (wife is gonna kill me) for any fixes that we've been able to find necessary and make.<a href="#t13:54" class="time">13:54</a>
wwoodsif need be, rc2 spun.. 26th? and we (quietly) begin synching to mirrors?<a href="#t13:54" class="time">13:54</a>
wwoodswas that it?<a href="#t13:54" class="time">13:54</a>
f13yea<a href="#t13:54" class="time">13:54</a>
nirikoh, I have one mash question/issue...<a href="#t13:54" class="time">13:54</a>
wwoodsI've been warning the wife that I'd probably end up working over this coming weekend<a href="#t13:54" class="time">13:54</a>
wwoodsI reserve the right to GTFOOT the following weekend though!<a href="#t13:54" class="time">13:54</a>
f13hand off to IS on Sunday/Monday to start syncing content, but not hand it to mirrors yet, give us the chance to find anything Monday, hand to mirrors Monday night or Tuesday<a href="#t13:54" class="time">13:54</a>
f13nirik: shoot<a href="#t13:55" class="time">13:55</a>
nirikwine. extras had it whitelisted so wine*.i386 shipped in x86_64... the current repo only has 3 of the wine subpackages, breaks upgrades for people with the extras wine installed.<a href="#t13:55" class="time">13:55</a>
wwoodsah, forgot the extra IS-sync stage<a href="#t13:55" class="time">13:55</a>
poelcatf13: thanks<a href="#t13:55" class="time">13:55</a>
f13nirik: erm... thats going to be... fun.<a href="#t13:55" class="time">13:55</a>
nirikyeah. ;( Can you whitelist wine*i386 for x86_64 easily?<a href="#t13:55" class="time">13:55</a>
f13not without there being a wine.x86_64 I don't think.<a href="#t13:56" class="time">13:56</a>
warrenwhy?<a href="#t13:56" class="time">13:56</a>
f13We can try adding it to the whitelist and see what happens.<a href="#t13:56" class="time">13:56</a>
f13warren: just due to the logic of the multilib making part of mash<a href="#t13:56" class="time">13:56</a>
f13I"ll have to review it, it may actually work.<a href="#t13:56" class="time">13:56</a>
nirikwine doesn't build on x86_64<a href="#t13:58" class="time">13:58</a>
niriks/on/for/<a href="#t13:58" class="time">13:58</a>
nirikit's got a ExclusiveArch:  %{ix86}<a href="#t13:58" class="time">13:58</a>
f13right<a href="#t13:58" class="time">13:58</a>
f13nirik: if you see notting come online, remind me to talk to him about it<a href="#t13:58" class="time">13:58</a>
nirikok<a href="#t13:59" class="time">13:59</a>
f13alright, anything else before we call this pig done?<a href="#t14:01" class="time">14:01</a>
wwoodswho's buying the beers when we finally get this thing out the door?<a href="#t14:02" class="time">14:02</a>
* warren builds pidgin-libnotify to knock off another blocker<a href="#t14:02" class="time">14:02</a>
bpepplewwoods: no doubts.  It will be really nice once it's released.<a href="#t14:02" class="time">14:02</a>
wwoodsoh! naming?<a href="#t14:03" class="time">14:03</a>
* f13 punts to notting on the naming.<a href="#t14:03" class="time">14:03</a>
wwoodswhat needs to be changed/rebuilt once we have a name, anything?<a href="#t14:03" class="time">14:03</a>
f13fedora-release<a href="#t14:04" class="time">14:04</a>
f13which I need to change at some point for the new yum repos<a href="#t14:04" class="time">14:04</a>
f13fedora-release-notes maybe<a href="#t14:04" class="time">14:04</a>
jeremywe need release notes built in general<a href="#t14:04" class="time">14:04</a>
wwoodsare we going to do a fedora-release rpm with extras-development disabled, or just go straight to the F7 final config at release time?<a href="#t14:04" class="time">14:04</a>
poelcatjeremy: is that part of the docs schedule?<a href="#t14:05" class="time">14:05</a>
* poelcat wonders about combining the docs schedule with the main Fedora schedule<a href="#t14:05" class="time">14:05</a>
jeremypoelcat: I'm not sure where it is on the docs schedule.  in the past, they've had to hand off to jesse.  so this is the first time they could do the build themselves<a href="#t14:06" class="time">14:06</a>
poelcat<a href=""></a><a href="#t14:07" class="time">14:07</a>
poelcatready on 17-May ?<a href="#t14:07" class="time">14:07</a>
EvilBobDocs does not deal with minor slips<a href="#t14:08" class="time">14:08</a>
f13wwoods: I think we're just going straight to the F7 config.<a href="#t14:08" class="time">14:08</a>
EvilBobthe processes are a bit more complex, as a result we do not unfreeze and refreeze and push again to translation<a href="#t14:08" class="time">14:08</a>
wwoodsf13: 'kay<a href="#t14:09" class="time">14:09</a>
EvilBobtranslation gets a bit edgy want we give them to many version changes<a href="#t14:09" class="time">14:09</a>
f13EvilBob: do you know when the next planned build is of the notes?<a href="#t14:09" class="time">14:09</a>
EvilBobs/want/when<a href="#t14:09" class="time">14:09</a>
f13it would be good to get them into the 'hide soon.<a href="#t14:09" class="time">14:09</a>
EvilBobf13: I paul was working on something last night<a href="#t14:10" class="time">14:10</a>
EvilBobf13: I will see what I can do to help get you info there<a href="#t14:10" class="time">14:10</a>
f13ok. neat.  Thanks!<a href="#t14:10" class="time">14:10</a>
coufyeah, relnotes where building fine in cvs<a href="#t14:10" class="time">14:10</a>
coufpaul was gonna catch you sometime iirc<a href="#t14:11" class="time">14:11</a>
f13gotcha<a href="#t14:11" class="time">14:11</a>
f13if there's nothign else I'd like to end this.<a href="#t14:12" class="time">14:12</a>
* warren heading to chirporsctor<a href="#t14:14" class="time">14:14</a>
f13 changed the topic of #fedora-meeting to: <a href=""></a> -- Meetings often get logged -- see schedule in the wiki for next meeting<a href="#t14:15" class="time">14:15</a>
f13Thanks all, I'll be pinging you at various times for various inputs.<a href="#t14:15" class="time">14:15</a>

Generated by 2.3 by Marius Gedminas - find it at!