ReleaseEngineering/Meetings/2008-may-19

From FedoraProject

Jump to: navigation, search

Contents

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

Open Tickets

Miscellaneous

  • 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?
  • http://fedoraproject.org/wiki/Infrastructure/RelengRhel5Migration
  • 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 Call<a href="#t13:14" class="time">13:14</a>
f13ping: notting wwoods jeremy spot warren rdieter lmacken jwb poelcat<a href="#t13:15" class="time">13:15</a>
jwbmissing today<a href="#t13:15" class="time">13:15</a>
warrenhi<a href="#t13:15" class="time">13:15</a>
* notting is here<a href="#t13:15" class="time">13:15</a>
* jeremy <a href="#t13:15" class="time">13:15</a>
rdieterhere<a href="#t13:15" class="time">13:15</a>
f13ok.  Lets look at our open milestones first<a href="#t13:17" class="time">13:17</a>
-!- f13 changed the topic of #fedora-meeting to: Fedora releng - tickets<a href="#t13:17" class="time">13:17</a>
* spot is here<a href="#t13:17" class="time">13:17</a>
f13.rel 24<a href="#t13:17" class="time">13:17</a>
zodbotf13: #24 (spins for Fedora 9) - Fedora Release Engineering - Trac - <a href="https://fedorahosted.org/projects/rel-eng/ticket/24">https://fedorahosted.org/projects/rel-eng/ticket/24</a><a href="#t13:17" class="time">13:17</a>
* poelcat here<a href="#t13:17" class="time">13:17</a>
f13THis is the ticket to create the custom spins for F9.  It's assigned to jwb now, since he did them before<a href="#t13:18" class="time">13:18</a>
f13but since he's missing today's meeting we can skip that.<a href="#t13:18" class="time">13:18</a>
jwbi'll do them when we have something decided on which to spin...<a href="#t13:18" class="time">13:18</a>
f13However we do need to come up with some written expectations as to custom spins for F10<a href="#t13:18" class="time">13:18</a>
jwbyeah, that<a href="#t13:18" class="time">13:18</a>
nottingi'm concerned about 'haven't received updates but should work the same'<a href="#t13:18" class="time">13:18</a>
jeremyespecially as I know for a *fact* that FEL won't just work the same<a href="#t13:18" class="time">13:18</a>
jeremyhence why chitlesh had explicitly asked for it to not be done for f9<a href="#t13:19" class="time">13:19</a>
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.<a href="#t13:19" class="time">13:19</a>
f13no filled in test matrix, no cookie.<a href="#t13:19" class="time">13:19</a>
rdieteragreed.<a href="#t13:20" class="time">13:20</a>
jeremy+1<a href="#t13:20" class="time">13:20</a>
notting+1<a href="#t13:20" class="time">13:20</a>
nottingare the spin owners noted somewhere?<a href="#t13:20" class="time">13:20</a>
jeremyfor the few we have, I can note it off the top of my head and then we can note it somewhere :)<a href="#t13:20" class="time">13:20</a>
f13realistically this is a requirement we should deliver to the Spins SIG<a href="#t13:21" class="time">13:21</a>
f13and I think we can safely nominate jwb to be our representation there.  (especially because he'd not here right now)<a href="#t13:21" class="time">13:21</a>
jeremyhaha<a href="#t13:21" class="time">13:21</a>
nottingeven so, any spins we make based on this ticket are only beta spins at first, correct?<a href="#t13:21" class="time">13:21</a>
jeremynotting: that's what I remember of the approved process<a href="#t13:22" class="time">13:22</a>
jwbf13, that's fine.  though i'll note i'll be pretty much "gone" end of may/beginning of june due to moving<a href="#t13:22" class="time">13:22</a>
jwbnotting, yes<a href="#t13:22" class="time">13:22</a>
f13alright, I think we can move on from this one.<a href="#t13:25" class="time">13:25</a>
f13.rel 23<a href="#t13:25" class="time">13:25</a>
zodbotf13: #23 (Fedora 10 Naming) - Fedora Release Engineering - Trac - <a href="https://fedorahosted.org/projects/rel-eng/ticket/23">https://fedorahosted.org/projects/rel-eng/ticket/23</a><a href="#t13:25" class="time">13:25</a>
f13whoops, another jwb item (:<a href="#t13:26" class="time">13:26</a>
jwbi'll send an email for that on wed<a href="#t13:26" class="time">13:26</a>
jwbany other questions there?<a href="#t13:26" class="time">13:26</a>
jeremynope<a href="#t13:27" class="time">13:27</a>
f13don't think so.<a href="#t13:27" class="time">13:27</a>
jwbk<a href="#t13:27" class="time">13:27</a>
* jwb goes back to not being here<a href="#t13:27" class="time">13:27</a>
f13That reaches the end of our open tickets (:<a href="#t13:27" class="time">13:27</a>
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 well<a href="#t13:27" class="time">13:27</a>
f13having tickets for our tasks does help with overall visibility and making sure nothing slips through the cracks.<a href="#t13:28" class="time">13:28</a>
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.<a href="#t13:28" class="time">13:28</a>
f13this will allow tag requests and whatnot to become tickets, which will help again with making sure things don't get lost.<a href="#t13:28" class="time">13:28</a>
f13.ticket 198<a href="#t13:28" class="time">13:28</a>
zodbotf13: #198 (Enable email to Trac Ticket filing aliases) - Fedora Infrastructure - Trac - <a href="https://fedorahosted.org/projects/fedora-infrastructure/ticket/198">https://fedorahosted.org/projects/fedora-infrastructure/ticket/198</a><a href="#t13:28" class="time">13:28</a>
f13that's the Infrastructure ticket concerning this effort.<a href="#t13:29" class="time">13:29</a>
f13at the time we enable email -> trac, I want to create a real releng mailing list, since we can now do hosted mailing lists<a href="#t13:29" class="time">13:29</a>
f13move discussion to the public list, and get rid of the alias which is difficult to maintain and archive<a href="#t13:29" class="time">13:29</a>
f13Does anybody see a problem with going this route?<a href="#t13:30" class="time">13:30</a>
nottingsounds good. is it possible to close the same tickets via e-mail?<a href="#t13:31" class="time">13:31</a>
f13theoretically you can, if you add some extra junk to your subject line<a href="#t13:31" class="time">13:31</a>
f13you can certainly update the ticket via email, it reads the re: [number] <a href="#t13:31" class="time">13:31</a>
rdieterf13: no problems, me likey.<a href="#t13:31" class="time">13:31</a>
jeremyf13: I want to figure out how we can use bodhi for tagging for f10...<a href="#t13:32" class="time">13:32</a>
f13jeremy: yeah, that's also a useful avenue to persue<a href="#t13:33" class="time">13:33</a>
* jeremy looks at lmacken<a href="#t13:33" class="time">13:33</a>
f13anything further on tickets?  (I'm going to run through relevant open tickets at each meeting too, again visiblity)<a href="#t13:35" class="time">13:35</a>
nottingjeremy: hm, so auto-tagging via karma of a non-updates repo with restricted karma ability?<a href="#t13:35" class="time">13:35</a>
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 works<a href="#t13:36" class="time">13:36</a>
-!- f13 changed the topic of #fedora-meeting to: Fedora releng - open floor<a href="#t13:37" class="time">13:37</a>
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.<a href="#t13:37" class="time">13:37</a>
nottingf13: releng migration status? anything you need an assist with?<a href="#t13:38" class="time">13:38</a>
f13ah good topic<a href="#t13:38" class="time">13:38</a>
-!- f13 changed the topic of #fedora-meeting to: fedora releng - <a href="http://fedoraproject.org/wiki/Infrastructure/RelengRhel5Migration">http://fedoraproject.org/wiki/Infrastructure/RelengRhel5Migration</a><a href="#t13:38" class="time">13:38</a>
f13I've done a some work, as noted in the ticket.  THe work left to be done involves bodhi, which is luke's domain<a href="#t13:39" class="time">13:39</a>
nottingf13: is the mockified buildrawhide in git now the actual one being used? :)<a href="#t13:39" class="time">13:39</a>
f13notting: it will be when we start composing from rhel5releng<a href="#t13:39" class="time">13:39</a>
nottingf13: so, the repodiff usage in current rawhide is still based off the old code?<a href="#t13:40" class="time">13:40</a>
f13notting: correct, I hand edited the buildrawhide on releng1 to switch over to repodiff<a href="#t13:41" class="time">13:41</a>
f13since treediff was failing repeatedly<a href="#t13:41" class="time">13:41</a>
jeremyanything else?<a href="#t13:44" class="time">13:44</a>
f13not with releng2, just got to get luke to test/verify his stuff and then schedule a time for the cutover.<a href="#t13:44" class="time">13:44</a>
-!- f13 changed the topic of #fedora-meeting to: fedora releng - fsck outage<a href="#t13:45" class="time">13:45</a>
f13Infrastructure is asking us for an outage window to do an fsck of /mnt/koji filestore<a href="#t13:45" class="time">13:45</a>
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 morning<a href="#t13:45" class="time">13:45</a>
jwbthat sounds sane<a href="#t13:46" class="time">13:46</a>
jeremysounds good to me<a href="#t13:46" class="time">13:46</a>
f13I think that's this weekend.<a href="#t13:46" class="time">13:46</a>
jeremyit is!<a href="#t13:46" class="time">13:46</a>
nottingwfm<a href="#t13:47" class="time">13:47</a>
f13ok.<a href="#t13:48" class="time">13:48</a>
f13I'll let infra now that we all signed off on it.<a href="#t13:48" class="time">13:48</a>
-!- f13 changed the topic of #fedora-meeting to: fedora releng - open floor (again)<a href="#t13:48" class="time">13:48</a>
f13If there are no topics in 2 minutes...<a href="#t13:48" class="time">13:48</a>
wwoodsjeremy: so if we can't change that behavior somehow, then there's no way of doing preupgrade without network connectivity<a href="#t13:51" class="time">13:51</a>
f13Thanks all.<a href="#t13:52" class="time">13:52</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 | For questions about using Fedora please ask in #fedora | See <a href="http://fedoraproject.org/wiki/Communicate/FedoraMeetingChannel">http://fedoraproject.org/wiki/Communicate/FedoraMeetingChannel</a> for meeting schedule<a href="#t13:52" class="time">13:52</a>

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