From FedoraProject

Jump to: navigation, search


Fedora Release Engineering Meeting :: Monday 2008-05-19

Open Tickets


  • Figure out a way to use bodhi for tagging for F10
  • Perhaps auto-tagging via karma of a non-updates repo with restricted karma ability?
  • Infrastructure is asking us for an outage window to do an fsck of /mnt/koji file store
  • Do it this weekend starting Friday evening or Saturday morning
  • Estimated to run for 22 hours

IRC Transcript

-!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering Meeting - Roll Call13:14
f13ping: notting wwoods jeremy spot warren rdieter lmacken jwb poelcat13:15
jwbmissing today13:15
* notting is here13:15
* jeremy 13:15
f13ok.  Lets look at our open milestones first13:17
-!- f13 changed the topic of #fedora-meeting to: Fedora releng - tickets13:17
* spot is here13:17
f13.rel 2413:17
zodbotf13: #24 (spins for Fedora 9) - Fedora Release Engineering - Trac -
* poelcat here13:17
f13THis is the ticket to create the custom spins for F9.  It's assigned to jwb now, since he did them before13:18
f13but since he's missing today's meeting we can skip that.13:18
jwbi'll do them when we have something decided on which to spin...13:18
f13However we do need to come up with some written expectations as to custom spins for F1013:18
jwbyeah, that13:18
nottingi'm concerned about 'haven't received updates but should work the same'13:18
jeremyespecially as I know for a *fact* that FEL won't just work the same13:18
jeremyhence why chitlesh had explicitly asked for it to not be done for f913:19
f13notting: right.  I'm thinking that if the spin owner hasn't demonstrated that their spin still works and hasn't done any QA on it, we shouldn't push it.13:19
f13no filled in test matrix, no cookie.13:19
nottingare the spin owners noted somewhere?13:20
jeremyfor the few we have, I can note it off the top of my head and then we can note it somewhere :)13:20
f13realistically this is a requirement we should deliver to the Spins SIG13:21
f13and I think we can safely nominate jwb to be our representation there.  (especially because he'd not here right now)13:21
nottingeven so, any spins we make based on this ticket are only beta spins at first, correct?13:21
jeremynotting: that's what I remember of the approved process13:22
jwbf13, that's fine.  though i'll note i'll be pretty much "gone" end of may/beginning of june due to moving13:22
jwbnotting, yes13:22
f13alright, I think we can move on from this one.13:25
f13.rel 2313:25
zodbotf13: #23 (Fedora 10 Naming) - Fedora Release Engineering - Trac - <a href="">
f13whoops, another jwb item (:13:26
jwbi'll send an email for that on wed13:26
jwbany other questions there?13:26
f13don't think so.13:27
* jwb goes back to not being here13:27
f13That reaches the end of our open tickets (:13:27
f13We do however have a F10 milestone that I'll be adding tickets to over time, and I encourage other people to add tickets to it as well13:27
f13having tickets for our tasks does help with overall visibility and making sure nothing slips through the cracks.13:28
f13Also, I've packaged up and submitted for review an application that will allow us to take email in and have them converted to Trac tickets.13:28
f13this will allow tag requests and whatnot to become tickets, which will help again with making sure things don't get lost.13:28
f13.ticket 19813:28
zodbotf13: #198 (Enable email to Trac Ticket filing aliases) - Fedora Infrastructure - Trac -
f13that's the Infrastructure ticket concerning this effort.13:29
f13at the time we enable email -> trac, I want to create a real releng mailing list, since we can now do hosted mailing lists13:29
f13move discussion to the public list, and get rid of the alias which is difficult to maintain and archive13:29
f13Does anybody see a problem with going this route?13:30
nottingsounds good. is it possible to close the same tickets via e-mail?13:31
f13theoretically you can, if you add some extra junk to your subject line13:31
f13you can certainly update the ticket via email, it reads the re: [number] 13:31
rdieterf13: no problems, me likey.13:31
jeremyf13: I want to figure out how we can use bodhi for tagging for f10...13:32
f13jeremy: yeah, that's also a useful avenue to persue13:33
* jeremy looks at lmacken13:33
f13anything further on tickets?  (I'm going to run through relevant open tickets at each meeting too, again visiblity)13:35
nottingjeremy: hm, so auto-tagging via karma of a non-updates repo with restricted karma ability?13:35
jeremynotting: that seems like a more "right" answer.  or hell, even let people add karma and comments.  then we have a better idea if the package actually works13:36
-!- f13 changed the topic of #fedora-meeting to: Fedora releng - open floor13:37
f13I don't have any other topics for today's meeting.  I'm still in post-f9 recovery mode and concentrating on some other things.13:37
nottingf13: releng migration status? anything you need an assist with?13:38
f13ah good topic13:38
-!- f13 changed the topic of #fedora-meeting to: fedora releng -
f13I've done a some work, as noted in the ticket.  THe work left to be done involves bodhi, which is luke's domain13:39
nottingf13: is the mockified buildrawhide in git now the actual one being used? :)13:39
f13notting: it will be when we start composing from rhel5releng13:39
nottingf13: so, the repodiff usage in current rawhide is still based off the old code?13:40
f13notting: correct, I hand edited the buildrawhide on releng1 to switch over to repodiff13:41
f13since treediff was failing repeatedly13:41
jeremyanything else?13:44
f13not with releng2, just got to get luke to test/verify his stuff and then schedule a time for the cutover.13:44
-!- f13 changed the topic of #fedora-meeting to: fedora releng - fsck outage13:45
f13Infrastructure is asking us for an outage window to do an fsck of /mnt/koji filestore13:45
f13testing has shown that it takes roughly 22 hours to do the fsck.  I've initially given the suggestion of memorial day weekend, starting Friday evening or saturday morning13:45
jwbthat sounds sane13:46
jeremysounds good to me13:46
f13I think that's this weekend.13:46
jeremyit is!13:46
f13I'll let infra now that we all signed off on it.13:48
-!- f13 changed the topic of #fedora-meeting to: fedora releng - open floor (again)13:48
f13If there are no topics in 2 minutes...13:48
wwoodsjeremy: so if we can't change that behavior somehow, then there's no way of doing preupgrade without network connectivity13:51
f13Thanks all.13:52
-!- 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 | For questions about using Fedora please ask in #fedora | See for meeting schedule13:52

Generated by 2.3 by Marius Gedminas - find it at!