19:02:49 <notmyname> #startmeeting swift
19:02:50 <openstack> Meeting started Wed Apr  3 19:02:49 2013 UTC.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:02:51 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:02:54 <openstack> The meeting name has been set to 'swift'
19:03:10 <notmyname> not a lot on the agenda today
19:03:24 <notmyname> (and will go very fast if we don't get a QA update for RAX)
19:03:31 <notmyname> but let's leave that for later
19:03:55 <lifeless> chmouel: fair enough; was following up on my name being mentioned :P
19:03:58 <notmyname> first up, general QA question. are there any QA efforts beyond rackspace that anyone is doing now?
19:04:30 <notmyname> I'm guessing that's a now
19:04:33 <notmyname> *no
19:04:36 <chmouel> noip not for me
19:05:03 <notmyname> creiht: ping. know anything about RAX QA status?
19:05:29 <notmyname> until we get that, let's move on to summit scheduling
19:05:34 <cschwede> please let me know if i can help out with some QA tasks
19:05:40 <zaitcev> RHOS and Fedora have some QA running, but the former goes release to release, while the latter is a bit bug-oriented and package oriented.
19:05:57 <notmyname> cschwede: thanks. we'll talk about that at the summit. the basic answer is "YES!"
19:06:16 <cschwede> notmyname: ok :)
19:06:30 <notmyname> zaitcev: cool. do you know if they've been looking at the 1.8.0 RC?
19:07:16 <notmyname> we've backported just about everything that's come in since the RC cut, so we're probably ok. I haven't heard of any showstoppers yet
19:07:26 <zaitcev> notmyname: No. Latest is 1.7.6.
19:07:41 <notmyname> ok
19:08:07 <notmyname> zaitcev: I'd love to chat at the summit about how to potentially do that more often (ie for each swift release)
19:08:28 <notmyname> we had 18 sessions proposed for our 8 slots at the summit. I think all of you have proposed at least one session
19:09:25 <notmyname> but since there is no more room left in the official schedule for oveerflow slots, I've got to schedule 8 of the proposals. I'm planning on signing up for unconference sessions on tuesday as soon as I get to PDX.
19:09:52 <notmyname> it's first-come-first-server as far as I know, so I'll try to be early :-)
19:10:24 <notmyname> the goal will be to write in our overflow sessions
19:10:45 <cschwede> when does the unconference signing start?
19:10:51 <notmyname> just about all of the proposals have been great. things that various people in the community have been asking for and talking about
19:10:56 <notmyname> ttx: ^?
19:11:07 <zaitcev> I'm ok with going into an overflow session, but I leave on Thursday.
19:11:13 <ttx> Monday morning. Usually people start signing up a bit later
19:11:39 <ttx> And most general incubaton wanabees should go on monday
19:11:58 <notmyname> I've got stuff going on (ie other talks and meetings) on wednesday and thursday, so I'll be shooting for tuesday time slots
19:11:58 <ttx> so you should be able to get most of tuesday without too much issues
19:12:42 <ttx> but some grouping and merging couldn't hurt. Each session is 40min long
19:12:47 <notmyname> I should point out for the official record that the lack of scheduling space is not something that could have been predicted based on previous summit participation. we generally matched our slots 1:1 for previous summits
19:13:08 <dfg> hello
19:13:14 <notmyname> yay, dfg!
19:13:32 <dfg> sorry for being late and stuff
19:13:44 <notmyname> np. thanks for coming
19:13:44 <notmyname> dfg: can you give a status update on QA?
19:13:53 <dfg> um- i'll go ask
19:14:26 <notmyname> dfg: thanks. basically, it comes down to 1) stop everything we can't release 2) looks ok 3) we need an rc3 with one or 3 more backports
19:14:37 * notmyname is hoping for 2
19:15:36 <notmyname> for the official summit sessions, I'm planning on performance-related talks and API-related talks. these are 2 of the big things that I think we'll be working on over the next 6 months
19:15:38 <Shree> I have a question regarding the Grizzly API doc release, are the Grizzly API docs ready and are the post on wiki the final released version?
19:16:08 <notmyname> Shree: I think that'd be a question for annegentle and the doc team. AFAIK, yes
19:16:43 <Shree> yes ping her but waiting for her response
19:16:54 <notmyname> unfortunately, a focus on performance and API work will mean that other really cool stuff will be pushed to the unconference
19:17:14 <Shree> BTW, +1 for performance. is it  uconf session or part of the summit?
19:17:28 <notmyname> I've "preapproved" all of the talks in order that each of you can still prepare your session, even if I can't promise a time slot
19:17:59 <notmyname> Shree: we've got 4 sessions related to performance that I'll target for the official time slots, I think
19:18:21 <notmyname> sorry for the confusion some of you got from having sessions approved, refused, approved
19:18:25 <zaitcev> I've already beated my preso on my coworkers but the main part is a discussion and decisions how to proceed.
19:18:44 <notmyname> zaitcev: ya, I want your LFS talk too :-)
19:19:10 <dfg> notmyname: regression is passing, there's still a couple smallish features he's testing. CORS, tempurl fix, couple other things.
19:19:10 <notmyname> are there any questions about the summit of scheduling or what to expect?
19:19:32 <notmyname> dfg: cool, thanks. do you have an ETA? like today or next week? or ...?
19:20:18 <dfg> i don't know. our QA situation has gotten pretty annoying because they're pulling our guys off onto other projects. nothing i can do about that though
19:20:27 <notmyname> if there are no questions about the summit, are there questions about anything else?
19:21:11 <ogelbukh> notmyname: does replication network fall into performance? )
19:21:13 <notmyname> dfg: I understand. thanks for letting me know.
19:21:20 <notmyname> ogelbukh: no :-(
19:21:25 <ogelbukh> ok, thanks )
19:22:18 <notmyname> I'm hoping we can do some code review for the repl network patch and perhaps get it merged next week.
19:23:15 <notmyname> so it looks like our time window is closing for the release and we'll do a final release for grizzly this evening (dfg)
19:23:22 <notmyname> ttx: ^
19:23:49 <notmyname> ah. almost forgot
19:23:50 <ttx> notmyname: sounds good. Just push the Final=True review when you're happy wit hit
19:23:56 <notmyname> ttx: will do
19:24:13 <ttx> notmyname: the common release will be out by the time you ge tup
19:24:35 <notmyname> our "Every two week" meeting means that our next meeting will be scheduled for the wednesday of the summit. I propose that we skip it
19:24:35 <ttx> unless shit happens in some othe rproject, but unlikely at htis point
19:24:40 <notmyname> ttx: ok
19:25:03 <clayg> notmyname: or move it to a bar
19:25:19 <swifterdarrell> clayg: ++
19:25:32 <ogelbukh> )
19:25:34 <notmyname> let's just schedule all our sessions there :-)
19:25:39 <zaitcev> oh god, no, those are so noisy, you cannot multicast worth anything
19:26:09 <zaitcev> I managed a bunch of 1:1 in San Antonio bars but it's a PITA
19:26:22 <notmyname> I'm sure there will be plenty of opportunity for free booze next week
19:26:36 <notmyname> err..two weeks
19:26:52 <portante> whew
19:27:08 <notmyname> so if there's nothing else, let's call the meeting. 30 seconds.....
19:27:26 <clayg> see ya'll in a couple weeks!
19:27:56 <chmouel> looking forward to it!
19:28:14 <notmyname> thanks again for coming. dfg, if anything comes up this afternoon, please let me know ASAP
19:28:22 <notmyname> see you in portland
19:28:24 <notmyname> #endmeeting