19:02:31 <notmyname> #startmeeting swift
19:02:32 <openstack> Meeting started Wed Mar 20 19:02:31 2013 UTC.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:02:33 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:02:35 <openstack> The meeting name has been set to 'swift'
19:03:13 <notmyname> today we need to talk about the QA status and any backports
19:03:41 <notmyname> creiht: ping
19:03:46 <notmyname> anyone from RAX here?
19:03:50 <notmyname> for a QA status
19:04:47 <notmyname> also, we've had a few merges into master (and some patches proposed) since the rc1 was tagged. I'm guessing some of those need to be in the release and some don't
19:04:49 <creiht> howdy
19:05:20 <notmyname> creiht: know anything about the status of QA on swift?
19:05:43 <creiht> creiht: dunno.. I'm WFH today
19:05:48 <notmyname> heh, ok
19:06:41 <creiht> and there may or may not be a cloudfiles meeting going on now
19:06:42 <notmyname> looks like we have a keystoneauth patch that should be merged and a bulk delete patch that should probably get backported
19:07:02 <notmyname> creiht: ah, ok. if that's a regularly scheduled thing, then we may need to adjust our meeting time
19:07:18 <cschwede> talking about QA & rc: is this the right time to submit a patch to improve (my account quota) documentation?
19:07:55 <notmyname> cschwede: it's always the right time to submit improvements to docs ;-)
19:08:36 <notmyname> are there other patches that should be backported?
19:08:52 <cschwede> notmyname: then I'll submit the patch tomorrow :)
19:10:25 <notmyname> fun times in a swift meeting when most of the core devs aren't here :-/
19:10:48 <notmyname> reminder to submit summit talks at summit.openstack.org
19:10:54 <notmyname> we've got some good talks proposed
19:11:03 <creiht> notmyname: I think there are a couple of bugfixes that will need to get in from our side
19:11:17 <dfg> ya what he said
19:11:28 <notmyname> dfg: beyond the bulk?
19:11:40 <davidha> hi, sorry for being late
19:12:05 <ogelbukh> notmyname: could we assist getting replication network in?
19:12:10 <notmyname> davidha: no worries
19:12:53 <notmyname> ogelbukh: checking
19:12:54 <davidha> notmyname: do we want to backport anything related to the hash function?
19:13:28 <notmyname> ogelbukh: looks like that needs some additional review love, so it's blocked on that now. I'd love to see it merged and backported, but that has QA consequences
19:13:56 <creiht> It would seem a bit late to get it in without rushing it
19:14:09 <notmyname> davidha: I've only been following the discussion on the LP bug, but I see there is a -2 in gerrit
19:14:11 <creiht> and it feels like we have already rushed quite a bit in the release
19:14:13 <notmyname> creiht: agreed
19:14:50 <davidha> creiht: was this reg the hash item?
19:15:09 <creiht> davidha: I was referring to replication network
19:16:03 <davidha> notmyname: ok, I am not sure gholt objects to this still  - but we need hholt for that :)
19:16:21 <creiht> the hash thing is kinda meh
19:16:24 <creiht> to me
19:16:30 <dfg> notmyname: right now slo- but we're still testing so there could be more
19:16:50 <notmyname> dfg: ok, thanks
19:18:36 <notmyname> as new things come in that need to be backported, please propose them to milestone-proposed
19:18:52 <ogelbukh> ogelbukh: ok, will wait for reviews then
19:18:56 <ogelbukh> oops
19:19:03 <ogelbukh> notmyname I meant )
19:19:30 <notmyname> davidha: I think the hash issue discussion can stay in LP/gerrit for now. especially since all of the interested parties aren't here anyway
19:20:20 <notmyname> anything else that needs to be discussed specifically regarding swift for the grizzly release?
19:20:53 <torgomatic> if the syslog/infinite loop bug can get fixed, we should definitely backport that one
19:20:55 <davidha> notmyname: sure - we are also still discussing it internally, have some more ideas for improvements, will take one or two more days to go through evenrything
19:20:57 <notmyname> QA is being done by RAX. others should do it too, if they can. patches that need to be backported should be proposed to milestone-proposed (after being proposed to master)
19:21:01 <tongli> @notmyname, not particularly for grizzly, but this patch sit there for two months now, and I have rebased quite few times,
19:21:04 <notmyname> davidha: ok, cool
19:21:06 <tongli> can any one please review it.
19:21:08 <tongli> https://review.openstack.org/#/c/15818/
19:21:22 <SpamapS> o/
19:21:32 <notmyname> tongli: ya, :-(
19:21:45 <chmouel> i'll try to update https://review.openstack.org/#/c/24415/ and propose it for milestone by tomo
19:22:37 <notmyname> chmouel: cool. I just now saw your follow-up comments
19:23:16 <notmyname> as we get closer to april 4, please also review the python-swiftclient patches. there are a few that implement the new functionality that will be in the release
19:23:45 <tongli> @notmyname, yeah, and this one.
19:23:46 <tongli> https://review.openstack.org/#/c/22569/
19:23:50 <chmouel> yep will get some time for review tomo morning
19:24:32 <notmyname> tongli: yup, that's something that should be fixed before the next python-swiftclient release
19:25:32 <notmyname> last call for anything else pertaining to the release?
19:26:31 <notmyname> I'll get a chance to start reviewing the summit talk proposals soon. if you've submitted one, you'll hear something soon
19:27:08 <notmyname> dfg: do you have a team meeting at this time?
19:28:17 <notmyname> if so, I'll propose a few alternate time slots and send an email out
19:28:31 <creiht> notmyname: I was wrong
19:28:40 <notmyname> ah ok
19:28:42 <dfg> huh?
19:28:50 <creiht> my calendar is messed up
19:29:06 <dfg> i'm just doing other stuff. did you need something?
19:29:15 <tongli> who will be at the summit?
19:29:27 <tongli> just know today, that I am approved to go to the summit.
19:29:32 <notmyname> dfg: creiht said the cloudfiles team meeting was now, and then he said his calendar was messed up
19:30:42 <notmyname> tongli: great. see you there
19:30:43 <dfg> notmyname: i don't know, i just work here- they're always changing the time but I'll tell him not to put it in this time slot
19:30:54 <notmyname> dfg: ok, thanks :-)
19:31:25 <notmyname> I think that covers it for stuff that needed to get mentioned at this meeting. let's call it done.
19:31:55 <notmyname> thanks for your time today
19:31:57 <chmouel> thanks
19:32:03 <notmyname> #endmeeting