ReleaseEngineering/Meetings/2007-nov-12

Fedora Release Engineering Meeting :: Monday 2007-11-12

Schedule Review

• http://poelstra.fedorapeople.org/schedules/f9/f9-tasks-overview.html
• Make sure no collisions with holidays
• Next proposed FUDCon: January 11-13, 2008, at Red Hat HQ in Raleigh
• http://gregdek.livejournal.com/17724.html
• Need to have other teams review: FESCo, Docs, translation team, QA
• Change Alpha Freeze to Jan. 15, Alpha release Jan. 24

F9 Tasks & Targets

• Fill out Trac tickets for things that need to get done
• https://hosted.fedoraproject.org/projects/rel-eng/
• Python scripts that can take email as input and create Trac tickets from them
• use rel-eng@fedoraproject.org as Trac input.

DECISIONS:

• continue move to Trac for task management
• work toward turning rel-eng@fp.o into a Trac ticket gateway
• create an invite only or otherwise moderated mailing list for rel-eng discussion/voting

Ideas for Goals for F9 Release

• brainstorm before next week's meeting to figure out what we want to do for this release outside the typical make bits show up stuff
• send preferably by Friday so we can digest it over the weekend.
• wwoods: http://fedoraproject.org/wiki/ReleaseEngineering/Overview
• notting
• signing server
• potentially the big multilib change--i need to get some stuff written down for that
• kill the buildroot overrides stuff
• wwoods
• bodhi depchecking!
• PPC as the trailblazer secondary arch
• f13
• signing server
• complete the s/development/rawhide/ changes.
• post-build processing--running rpmlint and other such things.
• jigdo support
• dealing with rawhide late in the cycle so that we have two nightly trees
• composes in Colo for F9
• warren
• delta rpm and presto by default
• jeremy
• less involvement
• need help spinning live images

Fedora CD Releases

• The board has asked that we produce split CD media once again.
• Release Engineering has not fully agreed, though have it would be possible
• really just a matter of time and space, yes?
• warren: can't upgrade with live images.
• would increase number of test targets
• affects on Release Engineering are more of the following:
• compose time
• validation time
• sync time
• disc space used

Meeting Time

• Going forward (starting with next week) we will meet at 1800 UTC (1300 EST)

Fedora 8 Jigdo Data from Fedora Unity

• 600 downloads of the .jigdo file
• 400 downloads of the CD1 template
• thus so 200 or so users did not know where to get started with jigdo or did not start yet.
• thought to be useful to people that cannot do network installs
• if we can look at what packages are on what CD and what CD other than 1 is most popular that might make for some interesting analysis

IRC Transcript

f13	notting: wwoods: warren: jwb: jeremy: spot: rdieter: poelcat: ping	<a href="#t13:03" class="time">13:03</a>
wwoods	hi!	<a href="#t13:04" class="time">13:04</a>
notting	it's like i never left!	<a href="#t13:04" class="time">13:04</a>
* poelcat here		<a href="#t13:04" class="time">13:04</a>
rdieter	here	<a href="#t13:04" class="time">13:04</a>
* warren here		<a href="#t13:04" class="time">13:04</a>
* jeremy is here at least sort of		<a href="#t13:07" class="time">13:07</a>
f13	ok.	<a href="#t13:08" class="time">13:08</a>
f13	<a href="http://poelstra.fedorapeople.org/schedules/f9/f9-tasks-overview.html">http://poelstra.fedorapeople.org/schedules/f9/f9-tasks-overview.html</a>	<a href="#t13:08" class="time">13:08</a>
f13	please review, I'd like to give John the thumbs up from our end.	<a href="#t13:08" class="time">13:08</a>
notting	we're going to have the release scoped in 10 days?	<a href="#t13:08" class="time">13:08</a>
f13	poelcat: nothing changed since I gave you the thumbs up this weekend right?	<a href="#t13:08" class="time">13:08</a>
poelcat	f13: correct	<a href="#t13:09" class="time">13:09</a>
f13	notting: suppose that depends on what "scope" means	<a href="#t13:09" class="time">13:09</a>
f13	since our feature review is open far longer than the scope period	<a href="#t13:09" class="time">13:09</a>
poelcat	notting: yeah, that was kind of place holder for "let's do *some* planning " :)	<a href="#t13:09" class="time">13:09</a>
warren	looks a lot like RHEL	<a href="#t13:09" class="time">13:09</a>
warren	=)	<a href="#t13:09" class="time">13:09</a>
poelcat	i know fedora board is talking about overall things they would like to see	<a href="#t13:10" class="time">13:10</a>
poelcat	so that kind of fits in	<a href="#t13:10" class="time">13:10</a>
poelcat	warren: nothing like it ;-)	<a href="#t13:10" class="time">13:10</a>
poelcat	ours is better :)	<a href="#t13:10" class="time">13:10</a>
notting	if so, the taskjuggler bars should be blue, not red~	<a href="#t13:10" class="time">13:10</a>
warren	Yeah, RHEL is just a cheap knock-off spin	<a href="#t13:10" class="time">13:10</a>
f13	ours is achievable.	<a href="#t13:11" class="time">13:11</a>
notting	can we put RHEL on spins.fp.o?	<a href="#t13:11" class="time">13:11</a>
f13	LOL	<a href="#t13:11" class="time">13:11</a>
warren	hah	<a href="#t13:11" class="time">13:11</a>
poelcat	LOL	<a href="#t13:11" class="time">13:11</a>
wwoods	their packages are all old and crusty	<a href="#t13:11" class="time">13:11</a>
wwoods	they barely update them at all	<a href="#t13:11" class="time">13:11</a>
warren	and no excitement	<a href="#t13:11" class="time">13:11</a>
wwoods	and ugh, that color scheme	<a href="#t13:11" class="time">13:11</a>
wwoods	so red!	<a href="#t13:11" class="time">13:11</a>
wwoods	I mean, at least it's not brown, but still	<a href="#t13:11" class="time">13:11</a>
warren	There is currently a flamewar going on at <that project> about moving away from brown.	<a href="#t13:12" class="time">13:12</a>
notting	obviously we should switch to a green theme. it's the in thing!	<a href="#t13:12" class="time">13:12</a>
wwoods	but their entire identity is tied up in the brownness! there is none more brown!	<a href="#t13:13" class="time">13:13</a>
f13	poelcat: one thing I didn't look at was the mash up of any holidays	<a href="#t13:13" class="time">13:13</a>
wwoods	(this idle chitchat is me stalling while I read through the schedule)	<a href="#t13:13" class="time">13:13</a>
f13	poelcat: I don't /think/ we have any significant dates falling on holidays, did you check that?	<a href="#t13:13" class="time">13:13</a>
notting	wwoods: they wear brown coats? explains the rabid online fans.	<a href="#t13:13" class="time">13:13</a>
poelcat	f13: i don't believe there are any... but TJ can schedule around them	<a href="#t13:13" class="time">13:13</a>
f13	k	<a href="#t13:13" class="time">13:13</a>
* poelcat will look into it		<a href="#t13:13" class="time">13:13</a>
warren	notting, is the new multilib plugin going to happen for F9?	<a href="#t13:13" class="time">13:13</a>
jeremy	alpha freeze is likely to be "interesting" as the first work-week post the holidays	<a href="#t13:13" class="time">13:13</a>
notting	warren: REPLY HAZY. ASK AGAIN LATER.	<a href="#t13:14" class="time">13:14</a>
rdieter	multilib plugin?	<a href="#t13:14" class="time">13:14</a>
wwoods	I'm going to be gone during the first week of April I think	<a href="#t13:14" class="time">13:14</a>
f13	rdieter: doing away with the idea of pre-defining what is or isn't multilib at compose time, and instead do it at run time, based on local policy, on the client.	<a href="#t13:15" class="time">13:15</a>
rdieter	wee!	<a href="#t13:15" class="time">13:15</a>
wwoods	actually 7-12. which coincides with PR1.	<a href="#t13:15" class="time">13:15</a>
warren	I don't get back until January 8th	<a href="#t13:15" class="time">13:15</a>
wwoods	oh man, having a "i386 compatibility" checkbox in the installer/yum config would be just awesome	<a href="#t13:16" class="time">13:16</a>
rdieter	welcome aboard, capt awesome. :)	<a href="#t13:17" class="time">13:17</a>
warren	good friends with captain obvious	<a href="#t13:17" class="time">13:17</a>
f13	wwoods: having composes that don't take 14 hours would be awesome too	<a href="#t13:17" class="time">13:17</a>
wwoods	all aboard the H.M.S. whupass! SET SAIL FOR RADNESS!!	<a href="#t13:17" class="time">13:17</a>
wwoods	f13: roger that	<a href="#t13:17" class="time">13:17</a>
rdieter	*cough* 14 hours! ouchie.	<a href="#t13:17" class="time">13:17</a>
wwoods	so yeah, I'll have to get someone to fill in as QA Lead for PR1	<a href="#t13:18" class="time">13:18</a>
poelcat	wwoods:  and a free bottle of awesome sauce?	<a href="#t13:18" class="time">13:18</a>
wwoods	but given 5 months to do so, I think that'll be OK	<a href="#t13:18" class="time">13:18</a>
warren	Could we possibly push back Alpha freeze by a week?	<a href="#t13:18" class="time">13:18</a>
wwoods	well, it's a non-blocking ("honor system") freeze	<a href="#t13:19" class="time">13:19</a>
f13	warren: which direction is "back", and why?	<a href="#t13:19" class="time">13:19</a>
wwoods	so the first week could just be a polite request to skip non-essential builds	<a href="#t13:19" class="time">13:19</a>
warren	"Please don't cause new breakage."	<a href="#t13:20" class="time">13:20</a>
wwoods	and subsequent weeks the request becomes less polite?	<a href="#t13:20" class="time">13:20</a>
warren	f13, 1/8 seems to be too early, especially with many people returning from holidays	<a href="#t13:20" class="time">13:20</a>
f13	if you mean make it a week later, ditto the release of Alpha1, I'm OK with that, without adjusting other schedules.	<a href="#t13:20" class="time">13:20</a>
warren	yes, htat	<a href="#t13:21" class="time">13:21</a>
f13	note that during the holidays is when a lot of our maintainers actually have /time/ to do Fedora stuff	<a href="#t13:21" class="time">13:21</a>
f13	it's just the paid shills that stop work	<a href="#t13:21" class="time">13:21</a>
warren	I did lots of work during last holidays	<a href="#t13:21" class="time">13:21</a>
wwoods	does it make sense to move the release a week later and leave the freeze where it is?	<a href="#t13:22" class="time">13:22</a>
f13	I would be board out of my mind if I didn't do work.	<a href="#t13:22" class="time">13:22</a>
f13	wwoods: no, because then we wouldn't get all those fun builds which would actually be worth testing.	<a href="#t13:22" class="time">13:22</a>
warren	wwoods, if honor system freeze, i guess so.	<a href="#t13:22" class="time">13:22</a>
warren	f13, oh	<a href="#t13:22" class="time">13:22</a>
f13	wwoods: if we're worried about new stuff landing due to holiday hackfests, we should include that in the Alpha	<a href="#t13:23" class="time">13:23</a>
wwoods	true	<a href="#t13:23" class="time">13:23</a>
wwoods	and the alpha is already 3 weeks longer than the beta	<a href="#t13:23" class="time">13:23</a>
warren	push back freeze and release by a week	<a href="#t13:23" class="time">13:23</a>
warren	+1	<a href="#t13:23" class="time">13:23</a>
wwoods	our test releases become a burden after ~4wks	<a href="#t13:24" class="time">13:24</a>
wwoods	err, start becoming a burden	<a href="#t13:24" class="time">13:24</a>
warren	Perhaps an important priority for November/December is to make composes faster	<a href="#t13:25" class="time">13:25</a>
warren	Wont really have time to work on that next year with F9 fires	<a href="#t13:25" class="time">13:25</a>
jeremy	also, what's up with fudcon and how does the schedule mesh (or not) with that	<a href="#t13:26" class="time">13:26</a>
warren	jeremy, URL?	<a href="#t13:26" class="time">13:26</a>
jeremy	warren: don't have one -- just greg's blog post from a few weeks ago	<a href="#t13:26" class="time">13:26</a>
warren	vaporconference	<a href="#t13:27" class="time">13:27</a>
wwoods	"Next proposed FUDCon: January 11-13, 2008, at Red Hat HQ in Raleigh."	<a href="#t13:27" class="time">13:27</a>
wwoods	(that was oct. 17)	<a href="#t13:27" class="time">13:27</a>
wwoods	<a href="http://gregdek.livejournal.com/17724.html">http://gregdek.livejournal.com/17724.html</a>	<a href="#t13:27" class="time">13:27</a>
f13	that would put fudcon the weekend before the Alpha freeze	<a href="#t13:27" class="time">13:27</a>
warren	pushing back the Alpha freeze to be after FUDcon would be good, suck in possible hackfest results	<a href="#t13:27" class="time">13:27</a>
f13	not a bad time for it.	<a href="#t13:27" class="time">13:27</a>
wwoods	yeah, alpha freeze should definitely be post-fudcon-hackfest	<a href="#t13:28" class="time">13:28</a>
f13	which it would be, if we all agree to kick it out a week due to vacation spew	<a href="#t13:29" class="time">13:29</a>
warren	spew	<a href="#t13:30" class="time">13:30</a>
wwoods	do we need to do a proposal/vote or can we just go with implied consent?	<a href="#t13:30" class="time">13:30</a>
f13	anybody opposed to pushing alpha freeze/release out a week later?	<a href="#t13:31" class="time">13:31</a>
warren	15th/	<a href="#t13:31" class="time">13:31</a>
warren	15th?	<a href="#t13:31" class="time">13:31</a>
poelcat	is fudcon for sure? greg's blog says "proposed"	<a href="#t13:32" class="time">13:32</a>
wwoods	not for sure. still in discussions etc.	<a href="#t13:32" class="time">13:32</a>
wwoods	ask greg for details.	<a href="#t13:33" class="time">13:33</a>
warren	Then let's push it back a week for now, and see how FUDCon crystalizes.	<a href="#t13:33" class="time">13:33</a>
warren	or congeals	<a href="#t13:33" class="time">13:33</a>
f13	but we can't wait for vapourconference.	<a href="#t13:33" class="time">13:33</a>
* warren likes congeal		<a href="#t13:33" class="time">13:33</a>
f13	and there are other reasons to adjust	<a href="#t13:33" class="time">13:33</a>
warren	Let's do it	<a href="#t13:33" class="time">13:33</a>
EvilBob	NOTE: the last word I got from Greg about FUDcon was "Working on it" so I am not sure that date is solid	<a href="#t13:33" class="time">13:33</a>
gregdek	WORKING TO FINISH PLANS FOR FUDCON.	<a href="#t13:33" class="time">13:33</a>
rdieter	do it +1, can revisit later when/if new information comes	<a href="#t13:33" class="time">13:33</a>
gregdek	The date is solid.  The location, though, is up in the air.	<a href="#t13:33" class="time">13:33</a>
gregdek	More info as I have it.	<a href="#t13:34" class="time">13:34</a>
EvilBob	gregdek: K	<a href="#t13:34" class="time">13:34</a>
f13	ok.	<a href="#t13:34" class="time">13:34</a>
rdieter	mmmm. solid.	<a href="#t13:34" class="time">13:34</a>
* EvilBob goes to post his other reservations as "for sale"		<a href="#t13:34" class="time">13:34</a>
rdieter	my back yard is free, it's pretty big. :)	<a href="#t13:34" class="time">13:34</a>
warren	poelcat, I assume you've already looked at how the proposed F9 schedule may affect <awful red colored commercial spin> schedule?	<a href="#t13:34" class="time">13:34</a>
wwoods	I think that's due to be discussed later this week	<a href="#t13:35" class="time">13:35</a>
poelcat	warren: having weekly meeting with them	<a href="#t13:35" class="time">13:35</a>
warren	k	<a href="#t13:35" class="time">13:35</a>
wwoods	having rel-eng approval will give this schedule more weight, prolly	<a href="#t13:35" class="time">13:35</a>
f13	yes	<a href="#t13:36" class="time">13:36</a>
f13	other people still need to weigh in	<a href="#t13:36" class="time">13:36</a>
f13	FESCo, Docs, translation team, QA	<a href="#t13:36" class="time">13:36</a>
f13	(although QA is kind of doing that now)	<a href="#t13:36" class="time">13:36</a>
wwoods	Yeah, thus far I'm happy with it but I'll ping testers and such	<a href="#t13:36" class="time">13:36</a>
wwoods	I'm not sure if the denizens of -test-list are fully aware of the changes being proposed	<a href="#t13:37" class="time">13:37</a>
wwoods	but I can't see there being major opposition	<a href="#t13:37" class="time">13:37</a>
wwoods	mostly we're codifying existing procedure and streamlining the early half of the process	<a href="#t13:38" class="time">13:38</a>
wwoods	it's a solid plan and I like it a lot.	<a href="#t13:38" class="time">13:38</a>
warren	Do it	<a href="#t13:38" class="time">13:38</a>
warren	let's move on	<a href="#t13:38" class="time">13:38</a>
f13	ok, moving on.	<a href="#t13:38" class="time">13:38</a>
* poelcat hears action as move Alpha to 15th... hold to other dates		<a href="#t13:39" class="time">13:39</a>
f13	As some of you noticed due to email, we now have a Trac instance at hosted.fp.o	<a href="#t13:39" class="time">13:39</a>
warren	poelcat, and the release one week as well.	<a href="#t13:39" class="time">13:39</a>
f13	I've created milestones for Alpha/Beta/Final Freeze/Release s	<a href="#t13:39" class="time">13:39</a>
f13	warren: what?	<a href="#t13:39" class="time">13:39</a>
warren	f13, wasn't that the plan?	<a href="#t13:39" class="time">13:39</a>
wwoods	Alpha Freeze Jan. 15, Alpha release Jan. 24	<a href="#t13:39" class="time">13:39</a>
f13	warren: we're not moving the final release, just the Alpha freeze/release set.	<a href="#t13:39" class="time">13:39</a>
warren	ok yes.	<a href="#t13:40" class="time">13:40</a>
poelcat	f13: carry on :)	<a href="#t13:40" class="time">13:40</a>
warren	f13, does this mean freeze requests go into trac instead of flooded lit?	<a href="#t13:40" class="time">13:40</a>
warren	list?	<a href="#t13:40" class="time">13:40</a>
f13	warren: getting to that.	<a href="#t13:40" class="time">13:40</a>
f13	So far I've filed some pretty important things we need to do for each of those things	<a href="#t13:41" class="time">13:41</a>
f13	and I'd like to encourage all of you to add tickets as you think of things that need to be done.	<a href="#t13:41" class="time">13:41</a>
f13	or propose milestones for things.	<a href="#t13:41" class="time">13:41</a>
f13	This is really our first stab at writing up each part.	<a href="#t13:41" class="time">13:41</a>
f13	And since we /have/ Trac, we can start looking at using it for processing tag requests	<a href="#t13:42" class="time">13:42</a>
f13	however, I don't want to force people to click through web forms, I"d like to allow them to just email an address and have it go into a ticket	<a href="#t13:42" class="time">13:42</a>
wwoods	that would be good, because it sucks when we worry about dropping rel-eng requests on the floor	<a href="#t13:42" class="time">13:42</a>
notting	where is the frontpage for this?	<a href="#t13:42" class="time">13:42</a>
f13	THere are python scripts that can take email as input and create Trac tickets from them, and I would like to make use of that to turn 'rel-eng@fedoraproject.org' into a Trac input.	<a href="#t13:42" class="time">13:42</a>
warren	notting, <a href="https://hosted.fedoraproject.org/projects/rel-eng/">https://hosted.fedoraproject.org/projects/rel-eng/</a>	<a href="#t13:42" class="time">13:42</a>
f13	notting: <a href="https://hosted.fedoraproject.org/projects/rel-eng/">https://hosted.fedoraproject.org/projects/rel-eng/</a>	<a href="#t13:43" class="time">13:43</a>
f13	Right now all tickets are assigned to rel-eng@ alias, which wouldn't work so hot if we turned that into a Trac input	<a href="#t13:44" class="time">13:44</a>
f13	so we'll either need a new alias or something else to assign tickets to	<a href="#t13:44" class="time">13:44</a>
f13	I wouldn't mind creating a full email-list for release engineering, and making that list the default assignee of tickets.	<a href="#t13:45" class="time">13:45</a>
warren	assign to nobody@	<a href="#t13:45" class="time">13:45</a>
f13	rel-eng@ could be the trac input still.	<a href="#t13:45" class="time">13:45</a>
f13	warren: nobody@ sucks for getting notified of new tickets filed.	<a href="#t13:45" class="time">13:45</a>
f13	Any thoughts about this?	<a href="#t13:47" class="time">13:47</a>
wwoods	would the releng list be invite-only or what?	<a href="#t13:47" class="time">13:47</a>
warren	archives not open to public?	<a href="#t13:47" class="time">13:47</a>
* poelcat posts refreshed schedule... still researching holidays		<a href="#t13:47" class="time">13:47</a>
wwoods	it makes sense to me, anyway. would be nice to have public archives etc	<a href="#t13:47" class="time">13:47</a>
f13	public archives yes.	<a href="#t13:48" class="time">13:48</a>
warren	so this replaces rel-eng@ ?	<a href="#t13:48" class="time">13:48</a>
f13	invite only, I'm not sure.  If we're doing voting on that list then yeah, I'd like to keep it that way to avoid confusing noise from non-voters.	<a href="#t13:48" class="time">13:48</a>
wwoods	well, maybe moderated such that only voting members can post freely. I don't care if people want to join and follow the list	<a href="#t13:49" class="time">13:49</a>
f13	warren: yes, rel-eng@ would cease to be a wide alias for us, and would be come an email gateway to our trac.  We'd gain a new mailing list for us, and that would be come the default owner of tickets.  If you're going to work on a ticket, you can reassign to yourself.  (not mandatory)	<a href="#t13:49" class="time">13:49</a>
f13	wwoods: perhaps	<a href="#t13:49" class="time">13:49</a>
wwoods	so how would people create tickets? mail to rel-eng@fp.o, which goes to trac, which sends mail to fedora-rel-eng@r.c	<a href="#t13:49" class="time">13:49</a>
warren	So people should no longer send mail to rel-eng@	<a href="#t13:50" class="time">13:50</a>
f13	wwoods: that's the easiest way yes.	<a href="#t13:50" class="time">13:50</a>
wwoods	no, I think the mail alias would stay the same	<a href="#t13:50" class="time">13:50</a>
f13	wwoods: alternatively they could file directly in Trac	<a href="#t13:50" class="time">13:50</a>
wwoods	but this new list would take the *role* of rel-eng@fp.o	<a href="#t13:50" class="time">13:50</a>
wwoods	build requests still go to the same place, and they still get to all of us	<a href="#t13:51" class="time">13:51</a>
wwoods	but they go through trac->mailman first	<a href="#t13:51" class="time">13:51</a>
wwoods	so we get public archives and ticketing	<a href="#t13:51" class="time">13:51</a>
wwoods	accountability, transparency, all that good stuff	<a href="#t13:51" class="time">13:51</a>
wwoods	I guess you can tell that I support this idea.	<a href="#t13:52" class="time">13:52</a>
f13	heh	<a href="#t13:52" class="time">13:52</a>
wwoods	so, yeah. let's make a decision and move on?	<a href="#t13:55" class="time">13:55</a>
f13	anybody against moving in this direction?	<a href="#t13:56" class="time">13:56</a>
jeremy	nope	<a href="#t13:56" class="time">13:56</a>
f13	It may take a while to hook up the email gateway, rel-eng@fp.o won't go away as our communication method until that happens I think.	<a href="#t13:56" class="time">13:56</a>
warren	wwoods, wait	<a href="#t13:57" class="time">13:57</a>
warren	wwoods, if people can still post to rel-eng@	<a href="#t13:57" class="time">13:57</a>
warren	how does that make it invite-only?	<a href="#t13:57" class="time">13:57</a>
f13	...	<a href="#t13:57" class="time">13:57</a>
f13	warren: /two/ addresses.	<a href="#t13:57" class="time">13:57</a>
warren	oh	<a href="#t13:58" class="time">13:58</a>
f13	warren: rel-eng@  -> trac.  feodra-release-engineering@redhat.com -> moderated mailing list.	<a href="#t13:58" class="time">13:58</a>
warren	trac can create tickets from an e-mail?	<a href="#t13:58" class="time">13:58</a>
f13	warren: that's what I said above.  There is a python tool to do this, we just have to hook it up somewhere in Fedora infrastructure.	<a href="#t13:58" class="time">13:58</a>
warren	ok cool	<a href="#t13:58" class="time">13:58</a>
f13	alright, nobody said no.	<a href="#t13:59" class="time">13:59</a>
f13	poelcat: decision: continue move to Trac for task management.  Work toward turning rel-eng@fp.o into a Trac ticket gateway, and creating an invite only or otherwise moderated mailing list for rel-eng discussion/voting.	<a href="#t14:00" class="time">14:00</a>
f13	This is just a quick blurb, that since FESCo approved the proposal, I made some big updates to the Overview page to reflect this.	<a href="#t14:00" class="time">14:00</a>
f13	If i've missed anything, please let me know.	<a href="#t14:00" class="time">14:00</a>
wwoods	f13: for reference, URL for the Overview page?	<a href="#t14:01" class="time">14:01</a>
f13	This I"d like ya'll to brainstorm a bit befor enext week's meeting, to figure out what we want to do for this release, outside the typical make bits shwo up stuff.	<a href="#t14:01" class="time">14:01</a>
f13	wwoods: <a href="http://fedoraproject.org/wiki/ReleaseEngineering/Overview">http://fedoraproject.org/wiki/ReleaseEngineering/Overview</a>	<a href="#t14:01" class="time">14:01</a>
notting	signing server!	<a href="#t14:01" class="time">14:01</a>
f13	Personally, I'd really like to get the signing server in place	<a href="#t14:02" class="time">14:02</a>
wwoods	bodhi depchecking!	<a href="#t14:02" class="time">14:02</a>
f13	and complete the s/development/rawhide/ changes.	<a href="#t14:02" class="time">14:02</a>
notting	potentially the big multilib change. i need to get some stuff written down for that	<a href="#t14:02" class="time">14:02</a>
f13	wwoods: that would be nice in some form.	<a href="#t14:02" class="time">14:02</a>
f13	notting: please for the love of god (:	<a href="#t14:02" class="time">14:02</a>
wwoods	at least in an informative manner: "pushing this update will break deps on the following live packages"	<a href="#t14:03" class="time">14:03</a>
notting	also, i'd like to kill the buildroot overrides stuff	<a href="#t14:03" class="time">14:03</a>
wwoods	and holy merciful crap yeah, everyone is dying for multilib reworking. but that's a much more invasive thing than the signing server	<a href="#t14:03" class="time">14:03</a>
f13	notting: can you explain that more?	<a href="#t14:03" class="time">14:03</a>
wwoods	and I think bodhi depchecking is going to be a lot more complex than the signing server	<a href="#t14:04" class="time">14:04</a>
notting	f13: push updates-candidate into the buildroot automatically	<a href="#t14:04" class="time">14:04</a>
f13	notting: that gives me a bit of the hives.	<a href="#t14:04" class="time">14:04</a>
f13	notting: but I await your proposal (:	<a href="#t14:05" class="time">14:05</a>
warren	notting, what do we do instead of buildroot override?	<a href="#t14:05" class="time">14:05</a>
f13	I'd also like to see something done with ppc	<a href="#t14:05" class="time">14:05</a>
warren	oops	<a href="#t14:05" class="time">14:05</a>
notting	f13: bodhi was going to grow a flag if an update was built against unreleased packages . this is all old stuff that just hasn't happened yet.	<a href="#t14:05" class="time">14:05</a>
f13	notting: sure, it's also making things pretty complicated for somebody trying to push an update, or figure out why an update hasn't been pushed.	<a href="#t14:06" class="time">14:06</a>
f13	lets see, what else woudl I not be upset if it magically happened.	<a href="#t14:06" class="time">14:06</a>
notting	free beer everywhere.	<a href="#t14:06" class="time">14:06</a>
f13	oh!  post-build processing, say running rpmlint and other such things.	<a href="#t14:06" class="time">14:06</a>
warren	delta rpm and presto by default?	<a href="#t14:07" class="time">14:07</a>
f13	that could happen.	<a href="#t14:07" class="time">14:07</a>
f13	jigdo support	<a href="#t14:07" class="time">14:07</a>
warren	And I really don't buy that we need delta rpm to be generated by koji/bodhi.  Why can't it be an async process?	<a href="#t14:07" class="time">14:07</a>
f13	dealing with rawhide late in the cycle so that we have two nightly trees	<a href="#t14:07" class="time">14:07</a>
wwoods	oh yeah, PPC as the trailblazer secondary arch	<a href="#t14:08" class="time">14:08</a>
f13	warren: for much of the same reason why pcakage signing shouldn't necessarily be async.	<a href="#t14:08" class="time">14:08</a>
warren	delta rpm generation would have to happen after packaging signing	<a href="#t14:08" class="time">14:08</a>
wwoods	if the compose process is already too slow, adding more steps seems like a loss	<a href="#t14:08" class="time">14:08</a>
warren	wwoods, +1	<a href="#t14:08" class="time">14:08</a>
warren	f13, delta rpm missing or existing doesn't break existing users	<a href="#t14:08" class="time">14:08</a>
f13	warren: but if package signing is automated...	<a href="#t14:08" class="time">14:08</a>
warren	f13, no reason to slow down the composing process for deltas	<a href="#t14:09" class="time">14:09</a>
f13	warren: if you don't create them during the compose process, how else do they show up?	<a href="#t14:09" class="time">14:09</a>
warren	f13, perhaps we should talk about this in detail later, I think there is an understanding disconnect about how it could work.	<a href="#t14:09" class="time">14:09</a>
warren	a bit off-topic for here	<a href="#t14:09" class="time">14:09</a>
f13	sure, somebody needs to own the feature and run with it.	<a href="#t14:10" class="time">14:10</a>
f13	anywho, I'd love to hear some thoughts and proposals on what to do for F9 by next week's meeting.	<a href="#t14:10" class="time">14:10</a>
warren	ok	<a href="#t14:10" class="time">14:10</a>
f13	preferrably by Friday so we can digest it over the weekend.	<a href="#t14:10" class="time">14:10</a>
wwoods	things proposed thus far: signing server, bodhi depchecking, multilib rework, deltarpm (presto) support, buildroot overrides(?)	<a href="#t14:11" class="time">14:11</a>
f13	poelcat: decision: prepare and present Fedora 9 rel-eng goals by next week's meeting.	<a href="#t14:11" class="time">14:11</a>
f13	wwoods: and jigdo	<a href="#t14:11" class="time">14:11</a>
f13	oh geez, I forgot something.	<a href="#t14:11" class="time">14:11</a>
f13	The board has asked that we produce split CD media once again.	<a href="#t14:12" class="time">14:12</a>
f13	I haven't fully agreed, I just indicated that it would be possible.	<a href="#t14:12" class="time">14:12</a>
notting	it's really just a matter of time and space, yes?	<a href="#t14:12" class="time">14:12</a>
warren	installing from live is insufficient?	<a href="#t14:12" class="time">14:12</a>
notting	there shouldn't be any *technical* concerns?	<a href="#t14:12" class="time">14:12</a>
notting	(i don't care one way or another, just clarifying)	<a href="#t14:12" class="time">14:12</a>
f13	notting: just crufty code.	<a href="#t14:13" class="time">14:13</a>
f13	warren: can't upgrade with live images.	<a href="#t14:13" class="time">14:13</a>
warren	f13, good point	<a href="#t14:13" class="time">14:13</a>
warren	f13, although we need that crufty code to work for RHEL6	<a href="#t14:13" class="time">14:13</a>
f13	yes	<a href="#t14:14" class="time">14:14</a>
f13	but they have their own crufty code.	<a href="#t14:14" class="time">14:14</a>
f13	not necessarily the same as ours.	<a href="#t14:14" class="time">14:14</a>
f13	(lets not go there here)	<a href="#t14:14" class="time">14:14</a>
wwoods	I sure do love having more test targets	<a href="#t14:14" class="time">14:14</a>
f13	From our side of things, its not that big of a deal.  more compose time, more validation time, more sync time, larger space used.	<a href="#t14:15" class="time">14:15</a>
warren	f13, eh?  isn't RHEL6 split-CD upgrade going to be based on Fedora <some number>	<a href="#t14:15" class="time">14:15</a>
f13	warren: RHEL's tool has their own copy of splittree.py and potentially more things.	<a href="#t14:15" class="time">14:15</a>
warren	oh	<a href="#t14:15" class="time">14:15</a>
f13	but not a discussion for here.	<a href="#t14:15" class="time">14:15</a>
jeremy	another important thing to note -- my availability for rel-eng types of tasks is going to be a lot lower for f9.  I'm hoping to find some one else to volunteer to run with building live images too	<a href="#t14:15" class="time">14:15</a>
f13	If nobody else volunteers, I'll be taking that task on	<a href="#t14:16" class="time">14:16</a>
warren	jeremy, just show me how, I'd love to.	<a href="#t14:16" class="time">14:16</a>
* poelcat might be interested too		<a href="#t14:16" class="time">14:16</a>
warren	jeremy, would I need a ppc box to do it?	<a href="#t14:16" class="time">14:16</a>
f13	wwoods: I think QA gets to make their own stink regarding split media showing up again.	<a href="#t14:16" class="time">14:16</a>
f13	warren: if we still make ppc live images yes, or you can use mine like Jeremy has been doing.	<a href="#t14:16" class="time">14:16</a>
jeremy	warren: I just used the ppc that f13 uses for the regular composes.  but hopefully we'll be doing composes in the colo for f9	<a href="#t14:17" class="time">14:17</a>
f13	jeremy: ooh good point.	<a href="#t14:17" class="time">14:17</a>
f13	Composes in Colo for F9	<a href="#t14:17" class="time">14:17</a>
f13	which ties into 'reverse the netapp stream'	<a href="#t14:17" class="time">14:17</a>
notting	and syncs from colo	<a href="#t14:17" class="time">14:17</a>
f13	it'll be good to have all these in Trac for well, tracking (:	<a href="#t14:17" class="time">14:17</a>
jeremy	(in an ideal world, we could then have an "external" person do the live composes.  which would be nice.   if nothing else, I'd like to let the kde sig take ownership of their own destiny, and the same with other spins)	<a href="#t14:17" class="time">14:17</a>
f13	Last item.	<a href="#t14:18" class="time">14:18</a>
f13	any objections to moving the meeting time one hour later to match up with DST?	<a href="#t14:18" class="time">14:18</a>
f13	(we did it today based on vote of those that showed up at the regular time)	<a href="#t14:19" class="time">14:19</a>
notting	no objections from me	<a href="#t14:19" class="time">14:19</a>
warren	do it	<a href="#t14:20" class="time">14:20</a>
* wwoods +1		<a href="#t14:20" class="time">14:20</a>
f13	poelcat: decision: Meeting time now one hour later (1800 UTC) to stay in sync with American DST	<a href="#t14:20" class="time">14:20</a>
jeremy	do it!	<a href="#t14:21" class="time">14:21</a>
f13	ok, unless there is anything else, we should call it.	<a href="#t14:21" class="time">14:21</a>
wwoods	I think we're good	<a href="#t14:22" class="time">14:22</a>
wwoods	Woo	<a href="#t14:22" class="time">14:22</a>
wwoods	goooo rel-eng!	<a href="#t14:23" class="time">14:23</a>
f13	Thanks all!	<a href="#t14:23" class="time">14:23</a>
poelcat	wwoods: figured it was an important conversation to have a record of	<a href="#t14:25" class="time">14:25</a>
wwoods	agreed. I had a log of it and was trying to find the irc2html stuff when I noticed you'd already done it	<a href="#t14:25" class="time">14:25</a>
EvilBob	Just a note on jogdo and the Split CD media, looking at the F8 CD logs Fedora Unity has had just over 600 downloads of the .jigdo file, about 400 downloads of the CD1 template, so 200 or so users did not know where to get started with jigdo or did not start yet.	<a href="#t14:33" class="time">14:33</a>
poelcat	EvilBob: why is F8 CD1 so popular when you can download F8 rescue.iso just as easily?	<a href="#t14:37" class="time">14:37</a>
f13	EvilBob: jigdo is a bit more interesting now that we populate rawhide with signed packages.	<a href="#t14:37" class="time">14:37</a>
EvilBob	poelcat: for people that do not have the connectivity to do a network install is my best guess	<a href="#t14:39" class="time">14:39</a>
poelcat	ahh	<a href="#t14:39" class="time">14:39</a>
EvilBob	poelcat: we don't know all the reasons why people have asked for us to release these but that was one arguement	<a href="#t14:40" class="time">14:40</a>
EvilBob	poelcat: a lot of users are getting the .jigdo and the CD1 template, checking to see what other media they need and are only building those images	<a href="#t14:41" class="time">14:41</a>
EvilBob	Hopefully this week we will get it so the logs are merged between all the round robin servers we are using so we can start looking at where users are coming from	<a href="#t14:43" class="time">14:43</a>
poelcat	that's pretty interesting	<a href="#t14:44" class="time">14:44</a>
EvilBob	if we can look at what packages are on what CD and what CD other than 1 is most popular that might make for some interesting analysis	<a href="#t14:46" class="time">14:46</a>

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