ReleaseEngineering/Meetings/2007-sep-10

From FedoraProject

Jump to: navigation, search

Contents

Fedora Release Engineering Meeting :: Monday 2007-09-10

News Update From F13

  • Test2 is on the way to mirrors
  • rawhide is now back to being rawhide unfrozen
  • minimal buildroots have been adjusted (util-linux-ng is back, perl(-devel) not listed)
  • have a list of names for F8--need to followup with legal
  • we should really go after the broken deps and upgrade paths a week or two before the test3 freeze
  • when are we supposed to turn off new packages for FC6?
  • FC6 gets shut down one month after F8, do we turn off new packages beforehand?
  • I'm working on the signing server stuff, and making good progress. I updated the Spec page for it and moved it into ReleaseEngineering/Projects/ space.
  • hope to have something reasonable for a code drop in a git module or something by the end of this week. Right now things like gpg key and passphrase are hardcoded so I don't want to commit that anywhere right now (:

Miscellaneous

IRC Transcript

Idea.png f13 changed the topic of #fedora-meeting to: Release Engineering Meeting<a href="#t12:58" class="time">12:58</a>
f13jeremy: jwb: spot: rdieter: warren: poelcat: notting: ping<a href="#t13:01" class="time">13:01</a>
* jeremy is here<a href="#t13:01" class="time">13:01</a>
rdieterhere (until I pass out for lack of food anyway)<a href="#t13:01" class="time">13:01</a>
* spot is here<a href="#t13:01" class="time">13:01</a>
* warren here<a href="#t13:02" class="time">13:02</a>
f13ok, well there isn't too much to talk about.<a href="#t13:02" class="time">13:02</a>
f13Test2 is on the way to mirrors.<a href="#t13:02" class="time">13:02</a>
f13rawhide is now back to being rawhide unfrozen.<a href="#t13:02" class="time">13:02</a>
f13minimal buildroots have been adjusted (util-linux-ng is back, perl(-devel) not listed)<a href="#t13:03" class="time">13:03</a>
f13hi notting<a href="#t13:03" class="time">13:03</a>
f13we've got a few days or relative quiet before we start hitting the test3 panic (:<a href="#t13:03" class="time">13:03</a>
f13things needed for test 3, a name.  Legal has the list, I need to ping them again.<a href="#t13:03" class="time">13:03</a>
f13we should really go after the broken deps and upgrade paths a week or two before the test3 freeze<a href="#t13:04" class="time">13:04</a>
f13and go all bofh on packages just to get them fixed.<a href="#t13:04" class="time">13:04</a>
* spot noted that sqlite2 disappeared<a href="#t13:05" class="time">13:05</a>
spotthats a rather significant problem<a href="#t13:05" class="time">13:05</a>
rdieterawol, orphaned?<a href="#t13:05" class="time">13:05</a>
spoti think it was orphaned<a href="#t13:05" class="time">13:05</a>
rdieterwhat (still) needs it?<a href="#t13:05" class="time">13:05</a>
spottwo of my packages do at a minimum<a href="#t13:05" class="time">13:05</a>
nottingsome moodle thing, iirc<a href="#t13:05" class="time">13:05</a>
spotone of which i could drop, but the other has rather adamant users<a href="#t13:06" class="time">13:06</a>
f13hrm.<a href="#t13:06" class="time">13:06</a>
* spot made an attempt to port it to sqlite3, but I don't understand sqlite well enough<a href="#t13:07" class="time">13:07</a>
* poelcat here<a href="#t13:07" class="time">13:07</a>
f13we can definitely bring it back, guess that was my bad for dropping something without checking first.<a href="#t13:07" class="time">13:07</a>
rdieterI could help comaintain (me being package-monkey mostly) with somebody...<a href="#t13:08" class="time">13:08</a>
spotrdieter: yeah, i'd be in the same boat, due to aforementioned sqlite know-nothing<a href="#t13:08" class="time">13:08</a>
rdieterrock. :)<a href="#t13:09" class="time">13:09</a>
f13One question I have in my mind is when are we supposed to turn off new packages for FC6?<a href="#t13:10" class="time">13:10</a>
f13FC6 gets shut down one month after F8, do we turn off new packages beforehand?<a href="#t13:10" class="time">13:10</a>
rdieterisn't the freeze (aka updates-only for F-2) kick in a test2?  If so, then it would seem so.<a href="#t13:11" class="time">13:11</a>
rdieterif fergit the exactly policy....<a href="#t13:11" class="time">13:11</a>
* rdieter goes looking...<a href="#t13:11" class="time">13:11</a>
f13there could be policy, I hadn't gone hunting for it lately.<a href="#t13:13" class="time">13:13</a>
f13in other news I'm working on the signing server stuff, and making good progress.  I updated the Spec page for it and moved it into ReleaseEngineering/Projects/ space.<a href="#t13:13" class="time">13:13</a>
rdieterwell, we have <a href="http://fedoraproject.org/wiki/Extras/Policy/EOL">http://fedoraproject.org/wiki/Extras/Policy/EOL</a><a href="#t13:13" class="time">13:13</a>
f13I hope to have something reasonable for a code drop in a git module or something by the end of this week.  Right now things like gpg key and passphrase are hardcoded so I don't want to commit that anywhere right now (:<a href="#t13:13" class="time">13:13</a>
rdieterThe EOL policy is clearly stale/out-out-date, something FESCo should probably clarify/update.<a href="#t13:15" class="time">13:15</a>
f13yeah<a href="#t13:16" class="time">13:16</a>
* jeremy wonders if f13 got distracted by his new laptop :)<a href="#t13:16" class="time">13:16</a>
f13jeremy: no, not at all...<a href="#t13:16" class="time">13:16</a>
f13so other than business as usual with tag requests and buildsystem unfucking and rawhide prodding, is there any thing else anybody would like to discuss?<a href="#t13:17" class="time">13:17</a>
jeremysome of the feedback from my blog post is probably worth discussing<a href="#t13:17" class="time">13:17</a>
jeremysadly, nothing earth shattering<a href="#t13:18" class="time">13:18</a>
f13yeah<a href="#t13:18" class="time">13:18</a>
jeremythe best thing I've heard is trying to cut down on the number of freezes<a href="#t13:19" class="time">13:19</a>
f13yeah, that could be useful.<a href="#t13:19" class="time">13:19</a>
jeremyie, we need to have one around feature freeze just to get things to calm down a little<a href="#t13:19" class="time">13:19</a>
jeremybut that before and after that, maybe we're better just trying to do weekly/bi-weekly snapshots<a href="#t13:19" class="time">13:19</a>
f13that sounds reasonable.<a href="#t13:20" class="time">13:20</a>
jeremyand with trying to get a little less out of them<a href="#t13:20" class="time">13:20</a>
jeremyprobably not something to change for F8, but more thinking for F9 would be good<a href="#t13:20" class="time">13:20</a>
f13more silent freezes where we just snapshot and only pull a few things in that are needed, but not freeze the whole set.<a href="#t13:20" class="time">13:20</a>
f13nod<a href="#t13:20" class="time">13:20</a>
nottingso, scrap test releases altogether in favor of snapshots?<a href="#t13:21" class="time">13:21</a>
jeremyand probably around the feature freeze, something more like the test releases of now<a href="#t13:22" class="time">13:22</a>
f13no, we'd still have a test release to co-incide with the feature freeze.<a href="#t13:22" class="time">13:22</a>
f13snapshots, an alpha, snapshots, maybe an RC or two, final.<a href="#t13:23" class="time">13:23</a>
jeremymaybe "beta" rather than "alpha", but yeah<a href="#t13:24" class="time">13:24</a>
f13sure.<a href="#t13:24" class="time">13:24</a>
jeremyI think the main thing to take away is that we want to try and get some snapshots going between now and final and then we can kind of see how that goes<a href="#t13:25" class="time">13:25</a>
jeremybased on that, we can have a better idea as far as what to propose for F9<a href="#t13:25" class="time">13:25</a>
f13yea<a href="#t13:26" class="time">13:26</a>
f13and we need something of a goal for those snapshots.  "Installable" is pretty easy to hit, but if we know that lots of stuff is still broken once installed...<a href="#t13:26" class="time">13:26</a>
jeremyI think "installable" and "running list of caveats" isn't unreasonable<a href="#t13:28" class="time">13:28</a>
jeremyrelease early, release often.  stuff that is broken should be used to convince people to do a better job of testing things before committing/building :)<a href="#t13:30" class="time">13:30</a>
linux_geekhi jeremey f13<a href="#t13:33" class="time">13:33</a>
f13jeremy: I agree<a href="#t13:34" class="time">13:34</a>
f13so lets try to do some more snapshots till the end and discuss towards the end of f8 what we do for f9<a href="#t13:34" class="time">13:34</a>
jeremysounds like a plan<a href="#t13:34" class="time">13:34</a>
f13ok, anything else?<a href="#t13:37" class="time">13:37</a>
f13I"d like to get back to my laptop and the signing server.<a href="#t13:37" class="time">13:37</a>
* rdieter just sent msg to fesco-list to clarify EOL/maintainance policy wrt FC-6.<a href="#t13:37" class="time">13:37</a>

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