From FedoraProject

Jump to: navigation, search


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


  • off to the mirrors; torrents are in progress
  • later this afternoon hope to get a push of F8 updates(-testing) done and drop the mirror-manager redirect
  • F8 is unlocked in bodhi so the requests will now show up in the list.
  • 170 0-day updates so far

Post F8

  • implement new development cycle
  • change of names from "development" tree to "rawhide"
  • making these changes early next week
  • f13 to send out a proposal
  • we need to prioritize F8Target blocker bug
  • other details in IRC transcript

IRC Transcript


f13jeremy: notting: rdieter: wwoods: jwb: spot: warren: poelcat: ping<a href="#t13:02" class="time">13:02</a>
* poelcat present<a href="#t13:02" class="time">13:02</a>
rdieterhere<a href="#t13:02" class="time">13:02</a>
jwbhere<a href="#t13:03" class="time">13:03</a>
* wwoods almost here<a href="#t13:04" class="time">13:04</a>
* jeremy is here<a href="#t13:04" class="time">13:04</a>
f13heh<a href="#t13:05" class="time">13:05</a>
f13I'll give it a few more minutes<a href="#t13:05" class="time">13:05</a>
* wwoods here<a href="#t13:10" class="time">13:10</a>
f13well, we're in a holding pattern for Fedora 8 now.<a href="#t13:11" class="time">13:11</a>
f13It's going to mirrors, torrents are in progress<a href="#t13:11" class="time">13:11</a>
f13I made the bugzilla entry today<a href="#t13:11" class="time">13:11</a>
f13and later this afternoon I hope to get a push of F8 updates(-testing) done and drop the mirror-manager redirect<a href="#t13:12" class="time">13:12</a>
lmackenf13: just unlocked F8 in bodhi, so the requests will now show up in the list.<a href="#t13:13" class="time">13:13</a>
wwoodscool. how many 0-day updates are we looking at right now?<a href="#t13:13" class="time">13:13</a>
lmacken170<a href="#t13:13" class="time">13:13</a>
wwoodsphrreeow.<a href="#t13:14" class="time">13:14</a>
poelcatyouch<a href="#t13:14" class="time">13:14</a>
wwoodsthat's updates-testing day 0. how many of those have actually requested a push to stable?<a href="#t13:14" class="time">13:14</a>
lmacken68 stable<a href="#t13:16" class="time">13:16</a>
lmacken97 testing<a href="#t13:16" class="time">13:16</a>
lmackenwhich means there are 5 not submitted<a href="#t13:16" class="time">13:16</a>
* lmacken is thinking about making updates get auto-submitted to testing.. and still allow people to push right to stable.<a href="#t13:17" class="time">13:17</a>
f13lmacken: or just nag mail for things unsubmitted<a href="#t13:18" class="time">13:18</a>
lmackenthat would work too.. but with the cli doing a single command would be nice, instead of create, then submit.<a href="#t13:19" class="time">13:19</a>
f13yeah<a href="#t13:21" class="time">13:21</a>
f13So, post f8 stuff.<a href="#t13:29" class="time">13:29</a>
-!- f13 changed the topic of #fedora-meeting to: Post F8<a href="#t13:29" class="time">13:29</a>
f13We have the new development cycle to implement<a href="#t13:30" class="time">13:30</a>
f13mostly that means changing the Overview page and making sure the new schedule follows suit<a href="#t13:30" class="time">13:30</a>
f13We also wanted to do an s/development/rawhide/ on the mirror<a href="#t13:31" class="time">13:31</a>
wwoodsright<a href="#t13:31" class="time">13:31</a>
wwoodsand probably s/devel/rawhide/ in bugzilla versions<a href="#t13:31" class="time">13:31</a>
wwoodsWe talked before a little bit about giving releases names at the start of the cycle<a href="#t13:33" class="time">13:33</a>
EvilBobWasn't there talk of dropping the "rawhide" name?<a href="#t13:34" class="time">13:34</a>
jeremyEvilBob: back in FC1, yes<a href="#t13:34" class="time">13:34</a>
wwoodsI think mostly we just haven't been clear on the fact that 'rawhide' *is* the internal codename for the new product<a href="#t13:34" class="time">13:34</a>
jeremyEvilBob: we're going back... what's old is new and all that :)<a href="#t13:34" class="time">13:34</a>
EvilBob;^)<a href="#t13:34" class="time">13:34</a>
rdieterretro rawhide<a href="#t13:34" class="time">13:34</a>
mdomschrawhide++<a href="#t13:37" class="time">13:37</a>
wwoodsf13: so F9Alpha, F9Beta, F9PR1, ... F9<a href="#t13:38" class="time">13:38</a>
wwoods(PR1 subject to change)<a href="#t13:39" class="time">13:39</a>
wwoodshow are those going to be numbered? 8.91, 8.92, 8.93, ... 9?<a href="#t13:39" class="time">13:39</a>
f13yes.<a href="#t13:39" class="time">13:39</a>
wwoodsso pre-Alpha rawhide will be.. 8.90?<a href="#t13:40" class="time">13:40</a>
f13I thik that's what I set it for<a href="#t13:40" class="time">13:40</a>
f13but if we are going to change development/rawhide/ I have to update it again anyway<a href="#t13:40" class="time">13:40</a>
wwoodsI remember seeing a couple of exchanges like: "do you have the development repository enabled?" "no, I'm not doing software development, I just want to run rawhide"<a href="#t13:41" class="time">13:41</a>
f13yep<a href="#t13:42" class="time">13:42</a>
wwoodsare we going to change the repo file name?<a href="#t13:42" class="time">13:42</a>
f13hrm, good question.<a href="#t13:43" class="time">13:43</a>
f13we probably should<a href="#t13:44" class="time">13:44</a>
f13but... that may leave folks in an odd lurch<a href="#t13:44" class="time">13:44</a>
wwoodsoh, true. how do we determine the initial state of the 'rawhide' repo? it should match 'development'<a href="#t13:45" class="time">13:45</a>
f13not only that, but introducing a new file, and removing an old one, will keep the old one around, maybe as .rpmsave though<a href="#t13:46" class="time">13:46</a>
wwoodsI have a feeling the window for a change like this is open right now but closing rapidly<a href="#t13:47" class="time">13:47</a>
rdieterdoit++<a href="#t13:47" class="time">13:47</a>
f13yeah, we'd have to announce now and give folks some time to prepare.<a href="#t13:48" class="time">13:48</a>
f13(read mirrors)<a href="#t13:48" class="time">13:48</a>
wwoodsI'd like for skvidal / notting / jeremy / etc. to weigh in on this before we start changing things<a href="#t13:48" class="time">13:48</a>
wwoodswould we change the name of the dir on the mirrors too?<a href="#t13:48" class="time">13:48</a>
* rdieter wants T-shirts: LIve 'n die by rawhide, livin la vida rawhide<a href="#t13:48" class="time">13:48</a>
f13I'd like to do this in a way that we don't make the mirrors have to resync everything.<a href="#t13:48" class="time">13:48</a>
f13wwoods: yes.<a href="#t13:48" class="time">13:48</a>
* skvidal reads up on what I'm weighing in on<a href="#t13:48" class="time">13:48</a>
f13wwoods: it doesn't make sense to do this half assed.<a href="#t13:49" class="time">13:49</a>
wwoodswe can change the name of the repo, the *filename* of the repo, and the bugzilla version<a href="#t13:49" class="time">13:49</a>
wwoodswithout touching mirror layout<a href="#t13:49" class="time">13:49</a>
skvidalah, okay<a href="#t13:49" class="time">13:49</a>
f13wwoods: but then the baseurl for rawhide points to development/<a href="#t13:49" class="time">13:49</a>
skvidalso we're changing things to say 'rawhide' everywhere<a href="#t13:49" class="time">13:49</a>
skvidalare we going to manually [re] move those files in %scriptlets or are we counting on rpmnew/rpmsaves?<a href="#t13:50" class="time">13:50</a>
jwbfor "continuity" reasons<a href="#t13:50" class="time">13:50</a>
wwoodsf13: right, well - that's a little odd but I don't think we're going to change package CVS f'rinstance<a href="#t13:50" class="time">13:50</a>
wwoodsso there's some things that aren't going to be changing from 'devel' to 'rawhide'<a href="#t13:51" class="time">13:51</a>
wwoodsthe baseurl is more user-visible than that, though<a href="#t13:51" class="time">13:51</a>
f13skvidal: I was going ot count on .rpmsave<a href="#t13:52" class="time">13:52</a>
skvidalokay so we're just nuking the file in fedora-release<a href="#t13:52" class="time">13:52</a>
f13skvidal: the new file would be fedora-rawhide.repo so there /shouldn't/ be something to .rpmnew<a href="#t13:52" class="time">13:52</a>
f13skvidal: yeah, introduce new repo file in fedora-release, change bugzilla entry, change url on mirrors(potentially)<a href="#t13:53" class="time">13:53</a>
wwoodswhere else have we called rawhide 'development'?<a href="#t13:53" class="time">13:53</a>
skvidaldo it - throw up a flag on blogs + mailing lists + the update notices (if any)<a href="#t13:53" class="time">13:53</a>
f13so yeah, making these changes early next week seems apropos<a href="#t13:56" class="time">13:56</a>
f13any other thoughts about this?  I'll send up some proposals.<a href="#t13:56" class="time">13:56</a>
wwoodsyeah, make some proposals so we can get other people to find places we might be forgetting about<a href="#t13:57" class="time">13:57</a>
GeroldKahi all<a href="#t13:58" class="time">13:58</a>
f13ok, any other business to bring up?<a href="#t13:58" class="time">13:58</a>
wwoodsIf there's stuff that should really be handled in 0-day updates, let me know<a href="#t13:59" class="time">13:59</a>
wwoodswe need to prioritise F8Target but I'm not sure there's time to go through and actually set pri/sev on them<a href="#t14:00" class="time">14:00</a>
wwoodsand people monkey with those anyway<a href="#t14:00" class="time">14:00</a>
f13yeah<a href="#t14:00" class="time">14:00</a>
f13well, attacking what's going to land in updates and updates-testing would be good, once they land that is.<a href="#t14:00" class="time">14:00</a>
wwoodsyeah, use bodhi to karma the important stuff that's there and bug people about what isn't<a href="#t14:00" class="time">14:00</a>
wwoodsor just give me bug IDs and I'll track it, since that's probably what I'll be doing for the next few days<a href="#t14:01" class="time">14:01</a>
f13ok, anything else?  tummy monster needs to be fed.<a href="#t14:01" class="time">14:01</a>
wwoodsF8Target is still 126/391 open<a href="#t14:01" class="time">14:01</a>
wwoods:/<a href="#t14:01" class="time">14:01</a>
* wwoods done<a href="#t14:01" class="time">14:01</a>
f13ok, meeting over.  thanks all.<a href="#t14:02" class="time">14:02</a>

Generated by 2.3 by Marius Gedminas - find it at!