ReleaseEngineering/Meetings/2007-jul-23

Fedora Release Engineering Meeting :: Monday 2007-07-23

F8 Test1 Freeze coming up

• builds from devel/ continue to get auto-tagged with 'dist-f8'. To get them into the test release they are manually tagged with 'f8-test1'. 'dist-rawhide' is pointed at 'f8-test1' during the freeze. Post-freeze 'dist-rawhide' is redirected to 'dist-f8' and life continues.
• Freeze starts tomorrow (2007-07-24)
• The typical workings that releng does during a freeze is thus:

1. tag build(s) for freeze tag (f8-test1) 1. sign build(s) 1. mash freeze tag 1. pungi / livecd-tools runs 1. test 1. wash, rinse, repeat

• status of things with KDE4
• on hold, looks like kde4 release schedule will be delayed, at least month, so we'll likely miss f8
• How many of the F8 features are actually read to test in test1?
• poelcat will:

1. create list of features that are close to 100% completion 1. ping feature owners to see if there are special testing needs for F8Test1

• wwoods created a f8test1 tracker bug--alias is "F8Test1"
• bugs for F8 Test1 will have a separate entry in bugzilla
• f13 will get it created

Next status meeting

• Thursday (2007-07-26) after FESCo meeting ~ 2 PM to 3 PM EDT

IRC Transcript

* warren here		<a href="#t12:57" class="time">12:57</a>
f13 changed the topic of #fedora-meeting to: RELENG-Meeting - roll call		<a href="#t13:01" class="time">13:01</a>
f13	spot: notting: jeremy: rdieter: wwoods: warren: ping	<a href="#t13:01" class="time">13:01</a>
* wwoods here		<a href="#t13:01" class="time">13:01</a>
f13	jwb will not be making it.	<a href="#t13:01" class="time">13:01</a>
f13	spot is most likely busy with moving trucks	<a href="#t13:01" class="time">13:01</a>
jwb	no, i'm here	<a href="#t13:01" class="time">13:01</a>
jwb	i won't make FESCo	<a href="#t13:01" class="time">13:01</a>
* notting is here		<a href="#t13:01" class="time">13:01</a>
* jeremy is here		<a href="#t13:02" class="time">13:02</a>
* jwb is here		<a href="#t13:02" class="time">13:02</a>
rdieter	1/2 here (@home w/kids, making lunch atm)	<a href="#t13:02" class="time">13:02</a>
f13	wait.	<a href="#t13:02" class="time">13:02</a>
* f13 reads email and gets a clue.		<a href="#t13:02" class="time">13:02</a>
f13 changed the topic of #fedora-meeting to: RELENG-Meeting - F8Test1 - JesseKeating		<a href="#t13:03" class="time">13:03</a>
f13	Ok, Test1 is right around the corner, freeze is tomorrow.	<a href="#t13:03" class="time">13:03</a>
f13	The typical workings that releng does during a freeze is thus:	<a href="#t13:03" class="time">13:03</a>
notting	1) panic	<a href="#t13:04" class="time">13:04</a>
f13	tag build(s) for freeze tag (f8-test1)	<a href="#t13:04" class="time">13:04</a>
f13	sign build(s)	<a href="#t13:04" class="time">13:04</a>
f13	mash freeze tag	<a href="#t13:04" class="time">13:04</a>
f13	pungi / livecd-tools runs	<a href="#t13:04" class="time">13:04</a>
f13	test	<a href="#t13:04" class="time">13:04</a>
f13	wash, rinse, repeat	<a href="#t13:04" class="time">13:04</a>
notting	where's the part about cursing at how broken the tree is?	<a href="#t13:05" class="time">13:05</a>
f13	The pungi and livecd-tools stage is most likely going to happen on workstations again, we haven't got to the point where we can do them all in the colo, but I'll try to get the content somewhere where rsync can just push up the differences for having public stuff out there sooner.	<a href="#t13:05" class="time">13:05</a>
f13	notting: that happens behind the scenes (:	<a href="#t13:05" class="time">13:05</a>
warren	we doing the same "spins" as F7 itself?	<a href="#t13:06" class="time">13:06</a>
f13	that's my plan, I haven't heard anything differently	<a href="#t13:06" class="time">13:06</a>
f13	and the anaconda work isn't quite done yet for being able to easily switch to using say the Everything/ repo for install	<a href="#t13:06" class="time">13:06</a>
* wwoods afk 1min		<a href="#t13:06" class="time">13:06</a>
f13	so a Fedora spin of the arches, and Everything repos of the arches	<a href="#t13:06" class="time">13:06</a>
f13	a Fedora and KDE LiveCD spin for i386/x86_64	<a href="#t13:07" class="time">13:07</a>
f13	(not sure the status of the ppc patches for livecd-creator; jeremy?	<a href="#t13:07" class="time">13:07</a>
f13	)	<a href="#t13:07" class="time">13:07</a>
jeremy	rdieter: where are things with kde4?	<a href="#t13:07" class="time">13:07</a>
jwb	f13, the ppc patches aren't around	<a href="#t13:08" class="time">13:08</a>
jeremy	f13: haven't gotten to them due to other things.  might try to take a look this afternoon while trying to get the i386 cd to fit	<a href="#t13:08" class="time">13:08</a>
jwb	f13, i'm shooting for test2 for a ppc live cd	<a href="#t13:08" class="time">13:08</a>
jwb	of some kind	<a href="#t13:08" class="time">13:08</a>
jeremy	or even better, I'll wait and let jwb look at it for test2 :-)	<a href="#t13:08" class="time">13:08</a>
f13	ok.	<a href="#t13:08" class="time">13:08</a>
rdieter	jeremy: on hold, looks like kde4 release schedule will be delayed, at least month, so we'll likely miss f8	<a href="#t13:09" class="time">13:09</a>
f13	I thought I saw dwmw2_gone put up some code somewhere, but yeah, good to know for this release.	<a href="#t13:09" class="time">13:09</a>
f13	rdieter: boo.  Oh well.	<a href="#t13:09" class="time">13:09</a>
jwb	f13, he did.  jeremy and i talked about it a bit ago.  needs rethinking	<a href="#t13:09" class="time">13:09</a>
* f13 phears a post-f8 update to kde4		<a href="#t13:09" class="time">13:09</a>
f13	gotcha	<a href="#t13:09" class="time">13:09</a>
jwb	rdieter, so is kde4 in rawhide atm?	<a href="#t13:09" class="time">13:09</a>
warren	what is our timetable for the presto part?	<a href="#t13:09" class="time">13:09</a>
jwb	or the alpha stuff?	<a href="#t13:09" class="time">13:09</a>
rdieter	f13: silver lining, it would've been hell to make it work anyway...	<a href="#t13:09" class="time">13:09</a>
rdieter	jwb: nope	<a href="#t13:09" class="time">13:09</a>
jeremy	rdieter: k.  still probably worth someone seeing how we are for fitting on the kde live image then	<a href="#t13:09" class="time">13:09</a>
jwb	rdieter, and won't be now until after f8 is frozen?	<a href="#t13:09" class="time">13:09</a>
rdieter	jwb: looks that way	<a href="#t13:10" class="time">13:10</a>
jwb	ok, thanks	<a href="#t13:10" class="time">13:10</a>
f13	warren: depends on buildsystem work, which right now the buildsystem work is going into garbage collection.	<a href="#t13:10" class="time">13:10</a>
notting	rdieter: i'm assuming no kde4 update for f8?	<a href="#t13:10" class="time">13:10</a>
rdieter	notting: :)  no.	<a href="#t13:10" class="time">13:10</a>
f13	*whew*	<a href="#t13:10" class="time">13:10</a>
jwb	well, *whew* and *ew*	<a href="#t13:10" class="time">13:10</a>
rdieter	at most, if we can come up with some parallel-install scheme that's sane.	<a href="#t13:11" class="time">13:11</a>
jeremy	rdieter: 'tis too bad.  but at least we know early enough for it to not be too bad	<a href="#t13:11" class="time">13:11</a>
* f13 gets parse error		<a href="#t13:12" class="time">13:12</a>
jwb	i understood	<a href="#t13:12" class="time">13:12</a>
jwb	f13, you need to learn more ninja-ese	<a href="#t13:12" class="time">13:12</a>
f13	apparently	<a href="#t13:12" class="time">13:12</a>
f13	so, back to test1	<a href="#t13:12" class="time">13:12</a>
f13	the freeze is tomorrow, but there is no listed time of day.  I somewhat want to play by ear, but that can be frustrating for folks too	<a href="#t13:12" class="time">13:12</a>
f13	I also want to get to signing packages as soon as possible as that can be the longest wait.	<a href="#t13:13" class="time">13:13</a>
f13	so I'm considering creating the freeze tag in the morning, tagging the latest builds, and starting the signing, but also tagging all the day's builds in the afternoon.	<a href="#t13:13" class="time">13:13</a>
jeremy	f13: might even be worth starting some of that today if you get a chance	<a href="#t13:13" class="time">13:13</a>
jwb	yes	<a href="#t13:14" class="time">13:14</a>
f13	then doing the actual 'freeze' (IE no more auto tagging into f8-test1) in the afternoon.	<a href="#t13:14" class="time">13:14</a>
jwb	jeremy, no presto for test1 still right?	<a href="#t13:14" class="time">13:14</a>
f13	jeremy: yeah, could start that overnight.	<a href="#t13:14" class="time">13:14</a>
f13	I'm also going to get out a pungi build that should have the configs I"ll be using to make test1, so that people can play at home and help us test the tree out.	<a href="#t13:14" class="time">13:14</a>
jwb	so i have an odd question	<a href="#t13:14" class="time">13:14</a>
f13	I've been beating on the broken deps report, but I haven't looked at all on the broken upgrades list.	<a href="#t13:15" class="time">13:15</a>
f13	jwb: shoot	<a href="#t13:15" class="time">13:15</a>
jwb	how many of the F8 features are actually read to test in test1?	<a href="#t13:15" class="time">13:15</a>
wwoods	are there candidate trees yet or are we waiting for the freeze?	<a href="#t13:15" class="time">13:15</a>
jeremy	jwb: no repos; the plugin bits should be there and people can create repos to play with	<a href="#t13:15" class="time">13:15</a>
wwoods	david nielsen's been doing some installer testing and his results are.. not encouraging	<a href="#t13:15" class="time">13:15</a>
notting	jwb: few	<a href="#t13:15" class="time">13:15</a>
f13	wwoods: rawhide is candidate trees.	<a href="#t13:16" class="time">13:16</a>
wwoods	I'm thinkin' media here but okay.	<a href="#t13:16" class="time">13:16</a>
f13	jwb: that's actually a really good question for poelcat.  We need to get al ist of things that are good for people to look at for test1	<a href="#t13:16" class="time">13:16</a>
* f13 hands wwoods a pungi (:		<a href="#t13:16" class="time">13:16</a>
jwb	yeah, i'm wondering what is actually ready to test	<a href="#t13:17" class="time">13:17</a>
f13	wwoods: for serial, there shouldn't be a need to wait for me to produce a tree	<a href="#t13:17" class="time">13:17</a>
wwoods	pungi default configs will work then?	<a href="#t13:18" class="time">13:18</a>
f13	does anybody want to tackle the broken upgrade-path list?	<a href="#t13:18" class="time">13:18</a>
poelcat	f13: I could round up a list of features that are % completion = 100 of close to	<a href="#t13:18" class="time">13:18</a>
f13	and just start going bofh mode on things?	<a href="#t13:18" class="time">13:18</a>
poelcat	s/of/or	<a href="#t13:18" class="time">13:18</a>
jwb	poelcat, that would be greate	<a href="#t13:18" class="time">13:18</a>
jwb	er, s/e//	<a href="#t13:18" class="time">13:18</a>
poelcat	so far I think there are only a few	<a href="#t13:18" class="time">13:18</a>
jwb	rsyslog is the only one i can think of	<a href="#t13:18" class="time">13:18</a>
f13	poelcat: also, just contacting feature owners and asking them if there is anything they'd like test1 users to touch on/test/report about.	<a href="#t13:18" class="time">13:18</a>
poelcat	f13: glad to	<a href="#t13:19" class="time">13:19</a>
f13	danke.	<a href="#t13:19" class="time">13:19</a>
* poelcat needs to run through all pages that are !approved and give feedback and ping owners as necessary		<a href="#t13:19" class="time">13:19</a>
poelcat	targetting EOD today	<a href="#t13:19" class="time">13:19</a>
warren	clarification:	<a href="#t13:19" class="time">13:19</a>
f13	wwoods: can you create us a f8test1 tracker bug (I don't want to use the term blocker just yet)	<a href="#t13:19" class="time">13:19</a>
warren	after test1 unfreezes, do we have to manually tag everything that gets into F8?	<a href="#t13:19" class="time">13:19</a>
wwoods	surely	<a href="#t13:20" class="time">13:20</a>
wwoods	we already have an F8blocker carried over from F7	<a href="#t13:20" class="time">13:20</a>
wwoods	wee	<a href="#t13:20" class="time">13:20</a>
f13	warren: no.	<a href="#t13:21" class="time">13:21</a>
wwoods	so we're creating a f8test1 entry in the version list for Fedora, right?	<a href="#t13:22" class="time">13:22</a>
f13	warren: builds from devel/ continue to get auto-tagged with 'dist-f8'.  To get them into the test release, we manually tag them with 'f8-test1'.  We point 'dist-rawhide' at 'f8-test1' during the freeze.  Post-freeze we re-direct 'dist-rawhide' to 'dist-f8' and life continues.	<a href="#t13:22" class="time">13:22</a>
notting	i thought we didn't do that no more	<a href="#t13:22" class="time">13:22</a>
f13	<insert long argument about bugzilla versions...>	<a href="#t13:22" class="time">13:22</a>
wwoods	we tried it and it was awful, we decided to redesign the bug entry page to only show a few versions	<a href="#t13:22" class="time">13:22</a>
f13	notting: we didn't, but it caused confusion because there existed versions for the old ones.	<a href="#t13:22" class="time">13:22</a>
wwoods	I did a mockup of that page and talked to the websites team about it, it stalled, nothing happened	<a href="#t13:23" class="time">13:23</a>
wwoods	so now we're back where we started	<a href="#t13:23" class="time">13:23</a>
f13	notting: if there were no old versions listed, it would probably be ok, but to have old ones there but no new ones didn't work out so hot.	<a href="#t13:23" class="time">13:23</a>
wwoods	because people *will* report against 'test1' and 'f7test1' and so on	<a href="#t13:23" class="time">13:23</a>
f13	wwoods: so yeah, I'll get a f8test1 bugzilla entry.	<a href="#t13:23" class="time">13:23</a>
notting	f13: then delist the old versions	<a href="#t13:23" class="time">13:23</a>
wwoods	delisting old versions is hard.	<a href="#t13:24" class="time">13:24</a>
notting	just move the bugs :)	<a href="#t13:24" class="time">13:24</a>
wwoods	hiding them from the form would be much smarter.	<a href="#t13:24" class="time">13:24</a>
* poelcat we were only using "devel" for all test releases		<a href="#t13:24" class="time">13:24</a>
wwoods	poelcat: yes, and we got bugs filed all over the damn place.	<a href="#t13:25" class="time">13:25</a>
* poelcat doesn't follow		<a href="#t13:25" class="time">13:25</a>
poelcat	give them *more* places to file?	<a href="#t13:25" class="time">13:25</a>
wwoods	we'll get bugs for test1, test4 (which is the default for some unknown reason), f7test1, and devel	<a href="#t13:25" class="time">13:25</a>
wwoods	give them a *correct* place to file	<a href="#t13:25" class="time">13:25</a>
f13	poelcat: it seemed to cause too much confusion.	<a href="#t13:26" class="time">13:26</a>
wwoods	or redesign the bug entry page. which is a stalled project, as mentioned.	<a href="#t13:26" class="time">13:26</a>
f13	poelcat: when there were options for old test releases, but no option for new, we were constantly getting hounded about where to file bugs and why there was no version for the test release.	<a href="#t13:26" class="time">13:26</a>
poelcat	seems like a simple wiki page to me... version under test = "devel" ; GA = GA version	<a href="#t13:27" class="time">13:27</a>
f13	poelcat: which unless we have a bugzilla front page in existance, people won't see.	<a href="#t13:27" class="time">13:27</a>
notting	constantly? surely it was not more than four or five times?	<a href="#t13:27" class="time">13:27</a>
f13	poelcat: we can wiki about it until we are blue in the face.	<a href="#t13:27" class="time">13:27</a>
notting	just taser everyone that asks	<a href="#t13:28" class="time">13:28</a>
f13	notting: try 4 or 5 times a day almost.	<a href="#t13:28" class="time">13:28</a>
poelcat	f13: fair enough	<a href="#t13:28" class="time">13:28</a>
f13	across email, bugs, irc, etc...	<a href="#t13:28" class="time">13:28</a>
poelcat	wwoods: what is stalled on front page design?	<a href="#t13:28" class="time">13:28</a>
wwoods	poelcat: someone who can actually do proper web design	<a href="#t13:28" class="time">13:28</a>
wwoods	I suck at it and I don't have time	<a href="#t13:28" class="time">13:28</a>
f13	The next question I have is what about new packages to the collection?	<a href="#t13:29" class="time">13:29</a>
f13	do we just punt on them until after the freeze?  that's what I would prefer...	<a href="#t13:29" class="time">13:29</a>
f13	(unless they're really needed for something that is broken in the freeze set)	<a href="#t13:29" class="time">13:29</a>
wwoods	it needs some backend CGI stuff to emit data like a full list of components, and an AJAX bit to request that full listing, etc.	<a href="#t13:29" class="time">13:29</a>
poelcat	wwoods: is there a project page for it? i'm no web designer either, but maybe I can find someone internally	<a href="#t13:30" class="time">13:30</a>
wwoods	punt 'til after freeze, but allow people to request inclusion if it's important	<a href="#t13:30" class="time">13:30</a>
jwb	yes	<a href="#t13:31" class="time">13:31</a>
jeremy	sounds reaonable	<a href="#t13:31" class="time">13:31</a>
wwoods	poelcat: no, there's no project page. Here's the mail thread. <a href="https://www.redhat.com/archives/fedora-websites-list/2007-June/msg00137.html">https://www.redhat.com/archives/fedora-websites-list/2007-June/msg00137.html</a>	<a href="#t13:31" class="time">13:31</a>
f13	Ok, so today I'll create the freeze tag, I'll create the version in bugzilla, do a pungi release with potential test1 configs (just generically named f8-*), start tagging packages and signing	<a href="#t13:32" class="time">13:32</a>
f13	and maybe even start a pungi spin	<a href="#t13:32" class="time">13:32</a>
jwb	that's a lot of "i'll"	<a href="#t13:32" class="time">13:32</a>
f13	tomorrow we'll see where we are with rawhide, tackle any issues that come up and start doing more tagging/spinning.	<a href="#t13:33" class="time">13:33</a>
jwb	we really need to look at scaling f13	<a href="#t13:33" class="time">13:33</a>
jeremy	jwb: I'm working on getting a live cd that fits on a cd	<a href="#t13:33" class="time">13:33</a>
f13	jwb: hehe, most of these are little 2 minute operations.	<a href="#t13:33" class="time">13:33</a>
jwb	jeremy, good :)	<a href="#t13:33" class="time">13:33</a>
jwb	f13, ok	<a href="#t13:33" class="time">13:33</a>
jwb	just sounds like a lot :)	<a href="#t13:33" class="time">13:33</a>
jwb	_i_ will merrily sit on my arse and do nothing since i'll be away from the interweb for the next week or so	<a href="#t13:34" class="time">13:34</a>
jwb	and i will feel bad about it	<a href="#t13:34" class="time">13:34</a>
* EvilBob runs in the door		<a href="#t13:34" class="time">13:34</a>
warren	f13, if you install F8test1, will it point to rawhide as an update source?	<a href="#t13:34" class="time">13:34</a>
jwb	should	<a href="#t13:34" class="time">13:34</a>
jeremy	warren: yes	<a href="#t13:35" class="time">13:35</a>
f13	warren: yes.	<a href="#t13:35" class="time">13:35</a>
warren	We screwed that up in past test releases, just making sure =)	<a href="#t13:35" class="time">13:35</a>
f13	just like all previous test releases.	<a href="#t13:35" class="time">13:35</a>
wwoods	tracker bug with alias "F8Test1" created	<a href="#t13:35" class="time">13:35</a>
f13	warren: when was the last time we screwed that up?	<a href="#t13:35" class="time">13:35</a>
warren	f13, a year ago?	<a href="#t13:35" class="time">13:35</a>
jwb	f7test4	<a href="#t13:35" class="time">13:35</a>
* f13 doesn't recall that.		<a href="#t13:35" class="time">13:35</a>
warren	anyway, sounds good.	<a href="#t13:36" class="time">13:36</a>
jwb	maybe i'm thinking of something else	<a href="#t13:36" class="time">13:36</a>
f13	I had a checklist of things to do before, and will need to consult again, as we need to do things like give legal a heads up, give the mirrors a heads up, make sure mmcgrath has enough space fo us, etc...	<a href="#t13:36" class="time">13:36</a>
f13	make sure the torrent has enough space, pre-generate torrent ini files, all that fun stuff.	<a href="#t13:37" class="time">13:37</a>
f13	hrm, I think we're too late to really look at jigdo support as well, unless somebody else wants to look at that.	<a href="#t13:37" class="time">13:37</a>
notting	are all these things documented? :)	<a href="#t13:37" class="time">13:37</a>
wwoods	bah. fie on jigdo	<a href="#t13:37" class="time">13:37</a>
f13	'fie' ?	<a href="#t13:37" class="time">13:37</a>
jwb	f13, should take your checklist and turn it into an SOP page	<a href="#t13:37" class="time">13:37</a>
wwoods	fie, I say!	<a href="#t13:37" class="time">13:37</a>
f13	notting: some of it is documented in the Overview page.	<a href="#t13:38" class="time">13:38</a>
wwoods	more trouble than it's worth in every situation where I've had to deal with it.	<a href="#t13:38" class="time">13:38</a>
f13	jwb: the checklist was one release specific and missing a lot.  The Overview could be turned into an SOP sortof.	<a href="#t13:38" class="time">13:38</a>
wwoods	naturally this is just my own personal curmudgeonry.	<a href="#t13:38" class="time">13:38</a>
f13	nod.	<a href="#t13:38" class="time">13:38</a>
rdieter	jigdo needs an owner for it who's responsible/accountable, is there such a person?	<a href="#t13:39" class="time">13:39</a>
f13	So, should we meet again on Thursday to discuss test1 status and plan for the weekend?	<a href="#t13:39" class="time">13:39</a>
rdieter	if not, punt it.	<a href="#t13:39" class="time">13:39</a>
f13	rdieter: not that I know of.  I think some of the unity guys are playing with auto-jigdo creation stuff, but not having a good time of it.	<a href="#t13:39" class="time">13:39</a>
rdieter	f13: well, there ya go.	<a href="#t13:39" class="time">13:39</a>
* f13 is quite a bit scared that davej is out this week at OSCON.		<a href="#t13:40" class="time">13:40</a>
notting	f13: thursday when?	<a href="#t13:40" class="time">13:40</a>
f13	notting: right after FESCO ?	<a href="#t13:40" class="time">13:40</a>
notting	ok	<a href="#t13:40" class="time">13:40</a>
f13	(2-3 eastern)	<a href="#t13:40" class="time">13:40</a>
f13	lets get a quick vote, Meet Thursday here after FESCo to discuss test1 status?	<a href="#t13:41" class="time">13:41</a>
f13	+1	<a href="#t13:41" class="time">13:41</a>
warren	2PM?	<a href="#t13:41" class="time">13:41</a>
warren	eastern	<a href="#t13:41" class="time">13:41</a>
wwoods	+1	<a href="#t13:41" class="time">13:41</a>
warren	f13, with davej gone, do we have anyone authorized to make changes to the kernel before test1?	<a href="#t13:41" class="time">13:41</a>
warren	(if needed)	<a href="#t13:41" class="time">13:41</a>
jwb	cebbert or *gasp* j-rod?	<a href="#t13:42" class="time">13:42</a>
jeremy	warren: plenty of people	<a href="#t13:42" class="time">13:42</a>
jwb	i say we nominate j-rod to be the test1 kernel wrangler	<a href="#t13:43" class="time">13:43</a>
* warren thinks it would be nice if cebbert came into IRC.		<a href="#t13:43" class="time">13:43</a>
jwb	warren, he does at times	<a href="#t13:43" class="time">13:43</a>
warren	ok	<a href="#t13:43" class="time">13:43</a>
f13	I would nominate j-rod, but it's not his $DAYJOB so I'd want to check with him first.	<a href="#t13:43" class="time">13:43</a>
f13	cebbert is a more likely candidate, or both of them.	<a href="#t13:44" class="time">13:44</a>
jwb	i was just joking	<a href="#t13:44" class="time">13:44</a>
jwb	he does seem to have good kernel foo in the specfile at least :)	<a href="#t13:44" class="time">13:44</a>
f13	everybody else OK with meeting Thursday?	<a href="#t13:44" class="time">13:44</a>
f13	jwb: oh indeed.  I think he's qualified for the job, just not sure what his manager would think of it (:	<a href="#t13:44" class="time">13:44</a>
poelcat	f13: at OSCON, but i'll be logging	<a href="#t13:45" class="time">13:45</a>
jwb	oh good.  we can bug davej by proxy then	<a href="#t13:45" class="time">13:45</a>
f13	hah	<a href="#t13:45" class="time">13:45</a>
poelcat	jwb: you got it	<a href="#t13:46" class="time">13:46</a>
poelcat	or if there is wireless "live from the Fedora booth"	<a href="#t13:46" class="time">13:46</a>
f13	anywho, is there any other Test1 related topics?	<a href="#t13:47" class="time">13:47</a>
notting	my god, my god, we're all gonna die?	<a href="#t13:47" class="time">13:47</a>
warren	notting, maybe.	<a href="#t13:48" class="time">13:48</a>
jwb	eventually	<a href="#t13:48" class="time">13:48</a>
f13	ok.	<a href="#t13:48" class="time">13:48</a>
f13 changed the topic of #fedora-meeting to: RELENG-Meeting - Open Discussion		<a href="#t13:48" class="time">13:48</a>
f13	any /other/ topics?	<a href="#t13:48" class="time">13:48</a>
jwb	signing server	<a href="#t13:48" class="time">13:48</a>
f13	ok	<a href="#t13:49" class="time">13:49</a>
jwb	is there anything someone other than f13 can do on this?	<a href="#t13:49" class="time">13:49</a>
f13 changed the topic of #fedora-meeting to: RELENG-Meeting - Signing Server		<a href="#t13:49" class="time">13:49</a>
f13	jwb: well, nobody is stopping anybody from producing code	<a href="#t13:49" class="time">13:49</a>
f13	all we have right now is a loosely agreed upon spec for what it should look like.	<a href="#t13:49" class="time">13:49</a>
jwb	can we set up a couple of xen guests to test with somewhere?	<a href="#t13:49" class="time">13:49</a>
jwb	writing code is sorta pointless without testing it :)	<a href="#t13:50" class="time">13:50</a>
jeremy	bah, testing is overrated	<a href="#t13:50" class="time">13:50</a>
* wwoods gets stabby		<a href="#t13:51" class="time">13:51</a>
* jeremy waves to wwoods :-)		<a href="#t13:51" class="time">13:51</a>
warren	f13, where is the spec again?	<a href="#t13:52" class="time">13:52</a>
f13	jwb: an RFR would not be turned down.	<a href="#t13:52" class="time">13:52</a>
jwb	f13, ok.  i might poke at that when i return then	<a href="#t13:52" class="time">13:52</a>
* jwb steps out for a few		<a href="#t13:52" class="time">13:52</a>
f13	warren: <a href="http://fedoraproject.org/wiki/JesseKeating/SigningServerSpecDraft">http://fedoraproject.org/wiki/JesseKeating/SigningServerSpecDraft</a>  seems I forgot to move it over to the ReleaseEngineering namespace.	<a href="#t13:53" class="time">13:53</a>
f13	will do that today.	<a href="#t13:53" class="time">13:53</a>
f13	I suppose somebody could match up our Spec to what RH uses today for signing and do some code investigation.  I did a little, and discovered that it would be a lot of changes and a big fork, so it might be better to just start our own from scratch and steal/share code where possible.	<a href="#t13:55" class="time">13:55</a>
f13	although RH's isn't opensource (yet) and there is some pain/process involved with making it such, so I've been avoiding looking too closely at the code	<a href="#t13:56" class="time">13:56</a>
f13	anything else on signing server?	<a href="#t13:56" class="time">13:56</a>
f13	(or rel-eng in general)	<a href="#t13:56" class="time">13:56</a>
f13	ok, calling hte meeting.  Thanks folks!	<a href="#t13:57" class="time">13:57</a>
f13 changed the topic of #fedora-meeting to: Channel is used by various Fedora groups and committees for their regular meetings | Note that meetings often get logged | See <a href="http://fedoraproject.org/wiki/Communicate/FedoraMeetingChannel">http://fedoraproject.org/wiki/Communicate/FedoraMeetingChannel</a> for meeting schedule		<a href="#t13:58" class="time">13:58</a>

Generated by irclog2html.py 2.3 by Marius Gedminas - find it at mg.pov.lt!