Tuesday, 2014-11-25

*** asalkeld has left #openstack-relmgr-office00:03
*** david-lyle is now known as david-lyle_afk00:17
*** david-lyle_afk has quit IRC00:45
*** david-lyle_afk has joined #openstack-relmgr-office01:14
*** SlickNik has joined #openstack-relmgr-office06:56
*** asalkeld has joined #openstack-relmgr-office08:46
ttxasalkeld: o/09:00
asalkeldhi ttx09:00
ttx#startmeeting ptl_sync09:00
openstackMeeting started Tue Nov 25 09:00:56 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
openstackThe meeting name has been set to 'ptl_sync'09:01
ttx#topic Heat09:01
ttx#link https://launchpad.net/heat/+milestone/kilo-109:01
ttxhttps://blueprints.launchpad.net/heat/+spec/lazy-load-outputs is marked "unknown" status -- should I consider that not started ?09:01
asalkeldttx, i need to check on that one09:02
asalkeldi just noticed it myself09:02
ttxasalkeld: ok, just set status when you know it -- "Not started" is fine :)09:02
asalkeldit might be small09:02
ttxOtherwise status looks good in general09:02
asalkeldyeah, more action in k209:02
ttxdo you expect much more stuff to get done for k1 ? Any work pending a spec approval ?09:03
asalkeldi have 2 bp's with code ready09:03
asalkeldbut trying to get people happy with it09:03
asalkeldeither in fast or not09:03
ttxasalkeld: would it make sense to track them in the milestone as "Blocked" ?09:04
ttxat least people would know it's potentially coming ?09:04
asalkeldmaybe, I have them as k209:04
asalkeldjust to be cautious09:04
ttxah, ok09:04
ttxthat's fione, you can move them if they are approved09:04
asalkeldi would love a tool that would tell me what bp's i need to tweak09:05
ttxSo I have spec2bp v2 here: https://review.openstack.org/#/c/108041/09:05
asalkeldi might as the nova guys09:05
ttxstill need to check with current users (dhellmann) if that's a welcome evolution09:05
ttxbut you can keep an eye on it09:06
ttxasalkeld: it doesn't prevent you from having to file the blueprint manually09:06
ttxbut after that it aligns fiedl status09:06
asalkeldthat's fine, i wouldn't mind just a tool in our specs repo that i can run09:06
asalkeldthat says x,y and z have just been approved09:07
asalkeldand need their status tweaking09:07
asalkeldmaybe i can come up with that09:07
asalkeldi'll dig into your code09:08
ttxdid you have any question?09:08
asalkeldall good09:08
ttxalright then, have a good day!09:08
asalkeldand 2 mins to go!09:08
asalkeldyou too09:08
ttxmikal: shall we wait for John?09:11
*** zz_johnthetubagu is now known as johnthetubaguy09:44
ttxjohnthetubaguy, mika: around now ?09:48
johnthetubaguyttx: I am09:51
ttxalright then, let's do this09:51
ttx#topic Nova09:51
johnthetubaguyso meeting time, 9am UTC tuesday?09:52
ttx#link https://launchpad.net/nova/+milestone/kilo-109:52
ttx9:10 UTC actually09:52
johnthetubaguyyeah, its kicking out time I think09:52
johnthetubaguyOK, cool09:52
ttxHeat goes at 909:52
johnthetubaguynot got that in my calendar yet09:52
ttxLooking at the kilo-1 page, there are a few unknown statuses to clarify, but otherwise looks good09:53
johnthetubaguyyeah, the unknown usually means not started, but yeah09:53
johnthetubaguyI am thinking we need to punt some stuff to kilo-2 soon/09:53
ttxyeah, as usual, the conversion rate is a bit slow09:54
ttxmaybe after thanksgiving, you can kick out not started ones to k209:54
johnthetubaguyyeah, that seems reasonable09:54
johnthetubaguyI mean, I am thinking everything that is not fully up for review09:55
johnthetubaguyso we have a smaller list to concentrate on09:55
ttxit's easy to bring them back from k2 to k1 if a miuracle happens09:55
johnthetubaguyyeah, very true09:55
johnthetubaguyafter thanksgiving it is09:55
ttxdo you expect a lot more stuff to show up on the k1 list ?09:55
johnthetubaguywell, maybe09:56
johnthetubaguythere are lots of specs that are close09:56
johnthetubaguybut I am adding them to k-2 by default at this point09:56
johnthetubaguybut thats just storing up problems for later in a way09:56
johnthetubaguywe spoke at the summit about all non-priority stuff needing to be merged by the end of kilo-209:57
johnthetubaguyso I need to start making that clear I guess09:57
ttxok, makes sense09:57
ttxAlso note that Nova doesn't have a stable branch liaison yet, so mikal is the liaison by default. Would be great for him to find someone to represent there09:57
ttxespecially with a point release coming up soon09:57
ttxjohnthetubaguy: maybe mention that at the next Nova meeting?09:58
johnthetubaguyyeah, I will just keep raising were I can I guess09:58
johnthetubaguyah, I will try to remember to ask about the sable branch09:59
johnthetubaguynot really sure who is active there09:59
ttxjohnthetubaguy: let me check09:59
ttxpadraig, vish and russell would be the more active stable people09:59
ttxand already part of stable-maint10:00
ttxso..; good candidates10:00
johnthetubaguythats a good list to ask, cool10:00
ttxjohnthetubaguy: other questions ? topics for the cross-project meeting today?10:00
johnthetubaguyttx: I guess specs follow up stuff10:01
ttxspecs follow up stuff ?10:01
johnthetubaguywe have tried to make changes to the template to make it clearer about the specs process10:01
johnthetubaguyfrom the cross project summit session, basically10:01
ttxoh, about converging multiple approaches ?10:01
johnthetubaguyI need to review the wiki page we have, and I just haven't done that yet10:01
johnthetubaguyright now we are trying to properly document the nova approach in kilo10:02
ttxis it ready for discussion, or would you rather solidify your approach and present it to the others10:02
johnthetubaguyits a bit distributed, but we seem to be getting closer10:02
johnthetubaguyI think we should solidify ideas first10:02
johnthetubaguyits more that, its not forgotton10:02
ttxideally you would set your process in stone and then present it for others to adopt and RFC on10:02
ttxOK, maybe a theme for next week meeting10:03
ttxrather than this week's10:03
johnthetubaguyyeah, thats a good target, while the US folks are eating turkey, I might get time for that10:03
ttxjohnthetubaguy: ok then, ttyl!10:03
johnthetubaguyttx: thank you, as always!10:04
*** asalkeld has left #openstack-relmgr-office11:18
SergeyLukjanovttx, /me ready when you're12:55
ttxSergeyLukjanov: your time is 13:10utc so eglynn will go first12:57
*** eglynn has joined #openstack-relmgr-office12:57
ttxeglynn: o/12:57
eglynnttx: hey, ready when you are12:57
ttx#topic Ceilometer12:57
eglynn#link https://launchpad.net/ceilometer/+milestone/kilo-112:58
eglynnI've fleshed out the kilo-1 roster12:58
ttxLooks good. All 4 blocked are pending specs ?12:58
eglynnyep, I've include some "blocked" BPs as discussed last week12:58
ttxI have spec2bp v2 here: https://review.openstack.org/#/c/108041/ which you might want to experiment with12:58
eglynnonly in the cases where I know some implementation work has been done12:58
eglynn(e.g. a PoC or a patch already proposed, so likely to be landable for Dec 18th)12:59
eglynncool, I'll have a play with it12:59
ttxprogress looks good13:00
ttxyou nominated a stable liaison (yourself)13:00
ttxso I have all the bases covered13:00
ttxanything you wanted to discuss ?13:00
eglynnyep, I got no volunteer for stable-maint liaison (asked at a couple of meetings)13:01
eglynnall other liaison positions covered though13:01
eglynnnothing else on my end13:01
ttxalright then, talk to you later!13:01
eglynncool, thanks for your time :)13:01
ttxSergeyLukjanov: you can go now if you want13:01
SergeyLukjanovttx, /me ready13:02
ttx#topic Sahara13:02
SergeyLukjanovttx, I forget about +10 mins ;(13:02
ttx#link https://launchpad.net/sahara/+milestone/kilo-113:02
SergeyLukjanovso, I've cleaned up the milestone page13:02
ttxnice progress. Exepcting a lot more to show up in that milestone before k1?13:02
SergeyLukjanovttx, yup13:03
SergeyLukjanovttx, I expect 2-3 more blueprints done in k113:04
ttxremember you can track blueprints lacking spec approval but likely to make it by k1 with the "Blocked" status13:04
SergeyLukjanovttx, in addition to the list if specs will be approved this week13:04
SergeyLukjanovttx, yup, I think I'll add them to k1 to add more info13:04
ttxalright, that looks pretty sane13:04
ttxand... You're the stable branch liaison for sahara13:05
SergeyLukjanovttx, exactly13:05
ttxso everything looks good. Any question on your side ?13:05
SergeyLukjanovI think nope, everything going very good, we have a lot of new contributors after the first integrated release13:06
SergeyLukjanovttx, and btw all other liaisons positions are covered now13:06
SergeyLukjanovso, nothing more from my13:07
SergeyLukjanovttx, thx!13:07
ttxSergeyLukjanov: thx!13:07
ttxdhellmann: we can go whenever you're available13:07
dhellmannttx: ready13:07
ttx#topic Oslo13:07
ttx#link https://launchpad.net/oslo/+milestone/next-kilo13:07
ttxfeels like a lot more is going on than apparent here13:08
dhellmannwe have some specs up for review still where work has started, I think13:08
dhellmannoh, and see:13:08
dhellmann#link https://launchpad.net/oslo/+milestone/kilo-113:08
dhellmannthe stuff in the incubator is still targeted at the regular milestones13:09
ttxah hm13:09
dhellmannI guess I can move those things to "next-kilo" as well13:09
ttxchecking if we have another view that would work13:10
ttxhmm, no per-projectgroup series view13:10
ttxso probably not13:10
ttxwe can still check two places if that makes more sense13:10
dhellmannI hate to put something like the namespace package change in next-kilo since we expect that to take quite a while.13:10
dhellmannlet's give it a week or two and see how it goes? I'm OK with merging them if we decide we need to do that13:11
ttxI think oslo-incubator should keep kilo-X13:11
ttxmakes a lot more sense to be aligned with projects it's copy-pasted from/to13:11
ttxok, you hjave a few "unknown" status that might be turned ito something more explicit, but otherwise looks good13:12
dhellmannI'll work on updating those. I'm taking a sick day today, so it may be next week13:12
ttxwon't hold you away from bed then... just a couple things13:13
ttxhttps://review.openstack.org/#/c/136820/ -- that's the oslo-enabled autokick.py13:13
dhellmannnah, this is just an annoying cold, but it gives me an excuse to do some reading :-)13:14
ttxif I ran it on oslo now it would do:13:14
ttx(wait for it)13:14
ttxSETGOAL is just setting the series goal according to target milestone13:15
ttxCLEARGOAL is removing the series goal since there is no target milestone13:15
dhellmannwhy are some of them being cleared? do those have kilo set as the series but the spec isn't approved?13:15
dhellmannok, I guess that looks right13:16
ttxKICK would mean removing target milestone because no priority set, but you don't have one of those13:16
dhellmannI sort of like having the option of adding a series goal but we can keep up with those items through the specs I guess13:16
ttxyeah, the trick is, it can get confusing if you don't keep the two aligned13:16
ttxyou can have blueprints showing up in series view but not in milestone views13:17
ttx(and the other way around, damn LP13:17
dhellmannI don't think there's anything too destructive going on here, so you can run it on oslo when you're ready13:17
ttxOK, will upgrade the version I use in my cron and run it for oslo13:17
dhellmannyeah, having them in the series was a way I kept up with what we said we might do before we started using specs13:17
ttxsecond review is the new spec2bp13:17
dhellmannbut specs give us that now13:18
ttxsince you are one of the few to actually use v1, I'd like to have an opinion if it's better/worse13:18
ttxthe goal is to support blueprints for not-yet-approved specs13:18
ttxso most of the logic around starting from the approved spec falls down13:18
ttxand I rewrote it to take a blueprint as input13:19
ttx(since those need to be craeted separately anyway)13:19
dhellmannI was looking over that. I think in general it's good, but I'm worried about the specs repository name handling change.13:19
dhellmannI was adding review comments when you pinged me13:19
dhellmannI'll submit them....13:19
ttxok, just take your time13:19
ttxjust a heads-up13:19
ttxquestions ?13:20
dhellmannno, I'll leave a couple of comments on that review but that's all I had today13:20
ttxalright then, get well soon13:21
dhellmannoh, sdague talked to you about the stable branch version caps, right? that's a topic for this afternoon?13:21
ttxit's on the agenda for the meeting today13:21
dhellmannok, good, he and I spoke yesterday and agree on what we need so if I can't make it this afternoon he will be representing both of us13:21
ttxmestery: around?15:05
mesteryttx: o/.15:05
ttx#topic Neutron15:05
ttx#link https://launchpad.net/neutron/+milestone/kilo-115:05
ttxStill feels very much partial to me15:06
mesteryYes, I agree, we're reviewing specs but it's still very thin15:06
mesteryAlso, did you see this: https://review.openstack.org/#/c/136514/15:06
mesterySimilar to Nova, I created a priorities spec for Neutron. Most of the things on that list are in review in neutron-specs15:06
ttxfeel free to add "blocked" specs if you expect stuff to be approved and implemented in time for k115:07
mesteryGot it15:07
ttxlike one of those priorities15:07
mesteryWill do15:07
* mestery makes a note to do that post-meeting with ttx15:07
ttxalso if you know what's going on there you can update the "unknown" statuses15:08
mesteryYes, agreed. Are we also running your automatic pruning script now for neutron? I believe we are, just wanted to confirm.15:09
ttxLooks like Ihar voluntered to do stable branch liaison for neutron too15:09
mesteryYes, he's been doing a really good job there in fact!15:09
mesteryI am very thankful for that. :)15:10
ttxwe have arosen, markmcclain and garyk on the neutron-stable-maint future team at this point15:10
mesteryI think all three of those folks are good to have there.15:10
mesteryI may see if amotoki wants to join as well, he would be a good candidate there in addition.15:10
mesteryI'll ask him.15:10
ttxok, so for next week it would be good to beef up that k1 milestone if you expect other stuff to make it by Dec 1815:11
ttxI guess that's all I had15:11
mesterySame for me, I just wanted to highlight the priorities BP and that's it.15:11
mesteryNothing yet.15:11
mesteryThanks ttx!15:11
ttxno pb15:12
* mestery is slowly ramping up more post fourth child birth.15:12
ttx#info priorities for kilo at: https://review.openstack.org/#/c/136514/15:12
mesteryIt's taking longer than I thought :)15:12
ttxnikhil_k: ready when you are (if you are around)15:12
*** nikhil_k|vacay is now known as nikhil_k15:15
nikhil_kttx: o/15:15
ttx#topic Glance15:16
ttx#link https://launchpad.net/glance/+milestone/kilo-115:16
* ttx checks why that undefined spec was not autokicked out of milestone15:17
ttxoh, the script is not really enabled for Glance yet15:18
nikhil_kttx: we want it in k1 though15:18
nikhil_kah ok15:18
ttxok, then that's fine.15:18
ttxnikhil_k: just let me know if you want to switch to using that in the future15:18
ttxyou should still probably set a priority for that undefined spec15:19
nikhil_ksounds good15:19
ttxAre those the two things you expect to land before the k1 date ?15:19
nikhil_kttx: there are a couple more15:19
* nikhil_k will ask for a bp to be created15:20
nikhil_kthere was a mis-communication that spec auto creates bp post approval15:20
ttxyes, you can add a blueprint and set it to "Blocked" until the spec is approved15:20
nikhil_kthere was one more communicated by another dev15:20
ttxno, BP needs to be manually created (LP has no API for creatign blueprints)15:20
nikhil_khe's still working on details15:20
ttxthen you can use a script of mine to update it if you want15:20
ttxin progress at https://review.openstack.org/#/c/108041/15:21
ttxbut in all cases you need a blueprint up and manually created15:21
nikhil_kah cool15:21
ttxso for next week it would be great to see those blocked blueprints on the milestone map15:22
ttxping me if you have any question on how to achieve that15:22
ttxErno Kuvaja volunteered to be stable liaison for Glance, does that sound good to you ?15:22
nikhil_kyeah, it was post communication from me15:23
nikhil_kso you need me to send email or something to confirm that?15:23
ttxno no, it's fine15:23
ttxok, I think that's all I had, status looks generally good.15:23
ttxQuestions on your side ?15:23
nikhil_kttx: nothing this week :)15:24
ttxok then, talk to you later!15:24
nikhil_kholiday week :))15:24
nikhil_ksounds good15:25
ttxthingee: ready when you are15:25
thingeettx: o/15:25
ttx#topic Cinder15:25
ttx#link https://launchpad.net/cinder/+milestone/kilo-115:26
thingeegot our first blueprint done!15:26
thingeestarted doing specs for k-215:26
ttxthere are two specs without an assignee on that list... any chance some person (or group) actually signed up to do that one ?15:26
thingeewe have about four drivers that are just about ready to be approved. We'll see if that'll be possible this week.15:27
thingeeah good catch. There are people for those already working on them15:27
thingeeI'll fix that15:27
ttxcool, looks good (and ambitious) otherwise15:28
ttxCinder did not formally designate a stable branch liaison yet, which means it falls back on you15:28
thingeeI agree. For those drivers on the list that still have a 'not started' status right now, I'm a bit worried15:28
ttxyes, starting next week you could defer not started stuff to k215:29
ttxJay Bryant is on the stable-maint group, could be a good candidate15:29
thingeethat would be jay bryant. What should I update to make that so?15:29
thingeeoh heh15:29
*** nikhil_k is now known as nikhil_k|vacay15:29
ttxthingee: https://wiki.openstack.org/wiki/CrossProjectLiaisons#Stable_Branch15:29
*** david-lyle has joined #openstack-relmgr-office15:30
thingeeI'll verify with him and update it15:30
ttxok, that's all I had I think15:31
ttxquestions at this point ?15:31
thingeethe problem is we can't defer drivers to k-2. The group has already agreed to leave k-2 and k-3 for other things than new drivers :(15:31
ttxwell, they should better get started then :)15:31
ttxotherwise you'll be15:31
thingeeI'll reach out to them for good measure15:31
ttx...soon in exception hell15:32
thingeethanks ttx!15:32
ttxthingee: thx!15:32
ttxdavid-lyle: ready when you are15:32
david-lylettx: ready15:32
ttx#topic Horizon15:32
ttx#link https://launchpad.net/horizon/+milestone/kilo-115:32
ttxSo... a few undefined priorities, a few unassigned blueprints, and a few unknown statuses15:33
ttxOtherwise progress looks good15:33
david-lyleI need to filter the new arrivals15:33
david-lylewill work on that later today15:33
ttxHorizon did not formally designate a stable branch liaison yet, which means it falls back on you15:34
ttxanyone that would make a great choice ?15:34
ttxWe have Mathias Runge on the stable-maint list15:34
david-lylemrunge is the first that comes to mind15:34
david-lyleyeah, same idea15:34
ttxyou may want to handle it too :)15:34
ttxor not.15:34
david-lyleI'll see if he's interested15:35
ttxwould be good to reach out to him. We plan to switch to new model in 10 days when 2014.2.1 is out15:35
ttxok, that's all I had at this early stage of the game. Questions on your side ?15:36
david-lyleno, I'm set15:36
ttxdavid-lyle: alright then. have a good day!15:36
david-lylettx: you too15:37
*** david-lyle has quit IRC15:43
*** david-lyle_afk is now known as david-lyle16:07
*** eglynn has quit IRC16:26
*** eglynn has joined #openstack-relmgr-office16:28
notmynamettx: good morning16:46
ttx#topic Swift16:47
ttxnotmyname: hi!16:47
ttxwhat does the future hold for swift ?16:48
notmynameI have one big thing to chat with you about as an FYI16:48
notmynameat the summit we talked about what's going on with swiftclient (we'd like to make big changes, but that's hard for compat reasons)16:48
notmynameso what we agreed to at the summit was to focus new cSDK dev effort into openstack-sdk16:49
notmynamesee the bottom of that link16:49
notmynamewe'll keep developing CLI functionality in python-swiftclient16:49
notmynameand of course we arent' throwing anything away or breaking anything for existing users16:49
notmynamebut we, as a dev group, want to focus new SDK feature dev work in openstack-sdk16:49
notmynamettx: what questions do you have?16:50
ttxso the big changes you want to make are more client library than CLI ?16:50
notmynamethe big change is where dev effort for new stuff is focused16:50
ttxand you'll use the existign python-swiftclient to handle compat ?16:51
notmynamethat's one possibility. I don't know the answer to that fully yet, since it's really early16:51
notmynameie there's a lot of work that has to be done in openstack-sdk before that even becomes realistic16:51
notmynamethe "Matt's plan" and my notes at the bottom of the etherpad are pretty much where we're at right now16:52
notmynameand so I wanted to make sure you know early what we're talking about and panning16:52
notmynameso realize this isn't anything that is close to done yet ;-)16:53
ttxok, all good16:53
ttxdo you plan a new version before end of year ? Or more next year at this point ?16:54
notmynameplease let me know what questions or advice you have :-)16:54
ttx(on swift proper)16:54
notmynamenew version of swift? or SDK/CLI?16:54
ttxSDK/CLI is obviously a bit further away :)16:54
notmynamenot sure about swift release yet. probably, but honestly I haven't looked at that yet16:55
notmynamemost swift effort is focused around EC right now16:55
ttxnotmyname: given that the end of year is really close now (if you count thanksgiving and the endof year holidays...) would be good to have a rough idea by next week ?16:55
ttxlike "definitely not in December", or "maybe in December"16:56
notmynameunfortunately I've got to run now. I have an online meetup starting in 4 minutes16:56
ttxsure, no pb16:56
ttxall I had anyway16:56
notmynameya, I'll have a better answer net week :-)16:56
ttxmorganfainberg: ready when you are16:56
morganfainbergttx o/16:56
ttx#topic Keystone16:56
ttx#link https://launchpad.net/keystone/+milestone/kilo-116:57
ttxLooks good to me. Expecting more to show up before k1 ?16:57
morganfainbergi hope (if anything) just minor bugs that will get fixed along the way16:57
morganfainbergbut nothing major16:58
ttxI see Dolph volunteered to handle stable branch liaison stuff16:58
ttxsounds good16:58
morganfainbergmakes my life easier :)16:58
ttxwe'll keep you in the future keystone-stable-maint team though :P16:58
morganfainbergi expect to jump through and do some stable reviews now that the cycle is getting under way16:59
ttxok, all lights seem to be green. Questions on your side ?16:59
morganfainbergit's been a mad dash getting my feet under me as PTL.16:59
morganfainbergthe Cleanup token Providers might move to K2. but i think everything else is no questions17:00
morganfainbergoh, i do have a question17:00
morganfainbergyour thoughts17:00
morganfainbergpython-keystoneclient, we'd like to do a rework of it - non-compatible, a v1.0.0 or v2 or whatever. Should this be a separate repository in that case?17:00
ttxthat sounds like a popular thing17:01
morganfainbergyeah, there is a lot of potential cleanup that could be done, and we have a lot of tech debt (for compatibility reasons)17:01
morganfainbergand CLI17:01
ttxwas discussing it with notmyname just before17:02
ttxyou can do the work in openstack-sdk and keep python-keystoneclient around for compat17:02
ttxand CLI17:02
ttxalthough if that gets more popular we could discuss it at a cross-project meeting17:03
morganfainbergthats it for me then.17:03
ttxthe agenda for today is a bit crowded, could that wait until next week ?17:03
ttxok, will add a note to remember it17:03
morganfainbergthis is a short week anyway, people are likely partially checked out in the US already17:03
ttxok added17:04
ttxmorganfainberg: anything else ?17:05
morganfainbergttx, nope. will ping you if anything else comes up.17:05
ttxmorganfainberg: alrightn have a good day17:05
ttxdevananda: around ?17:05
devanandattx: hi!17:06
ttx#topic Ironic17:06
ttx#link https://launchpad.net/ironic/+milestone/kilo-117:06
devanandait's still a bit under-targeted - we've been doing a -lot- of spec work the last two weeks17:07
ttxThose "unknown" statuses could be clarified, otherwise looks good17:07
devanandathere are now a lot more specs approved than are reflected on there, with a couple more big ones in the works17:07
ttxdevananda: don't forget you can add specs as "Blocked" if you want to track them as part of the milestone but they aren't approved specs yet17:07
devanandarefactoring our state machine is going to be, I hope, the largest change this cycle -- and several other things depend on that17:07
ttxthat conveys a more useful information than droping them from heavens on the last week :)17:07
devanandattx: ack. though at this stage, afaict, the majority of developers in Ironic are using specs, not LP17:08
ttxdevananda: I'd only track the ones that are team priorities17:08
ttxcraete a blueprint, then you can use https://review.openstack.org/#/c/108041/ to keep statuses up to date17:09
ttx(still manual, but at least doesn't require to click on LP)17:09
devanandaI'm using the old version (currently in tree)17:09
ttxthat new version (proposed) is compatible with not-yet-approved specs17:09
ttxsets them to Blocked17:09
devanandaawesome. I'll pull that rev and try it today17:10
ttxreveiws welcome17:10
devanandaother news ...17:11
ttxin other news, adam_g is your stable liaison, but since Ironic wasn't part of the Juno release, you won't have point releases handled by the stable maint team anyway17:11
ttxso I don't expect him to have a lot to do there17:11
devanandawe've changed our IRC meeting structure, and are starting to send weekly "status update" emails rather than take up meeting time with that17:11
ttxhe can still do backports and keep stable/juno sane I guess17:11
devanandaand we agreed to start alternating weekly meeting times17:11
ttxsounds good17:12
devanandattx: great. also, I'm now auth'd for stable-maint team as well, so between adam_g and I, we can actually land fixes for stable/juno :)17:12
devanandattx: fwiw, time slots we agreed to are alternating between Monday 1700 UTC && Tuesday 0500 UTC17:13
devanandai'll update the wiki today. do I have access to update the iCal feed, or is that something you still do?17:13
ttxit's something someone volunteered to do17:14
ttxhe should track the wiki page changes17:14
ttxwill be a good test :)17:14
devanandawhich someone? :)17:14
devanandaor just wait and see if he does?17:14
ttxTony Breeds17:14
ttxno idea what's his irc nick was17:14
devanandak k17:15
ttxmore questions ?17:15
ttxalright then17:15
ttxhave a good day!17:16
devanandayou too!17:16
ttxno Trove this week17:16
openstackMeeting ended Tue Nov 25 17:16:42 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-11-25-09.00.html17:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-11-25-09.00.txt17:16
openstackLog:            http://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-11-25-09.00.log.html17:16
*** russellb has quit IRC18:11
*** russellb has joined #openstack-relmgr-office18:12
*** johnthetubaguy is now known as zz_johnthetubagu18:53
*** zaneb has quit IRC20:05
*** zaneb has joined #openstack-relmgr-office20:20
*** zaneb has quit IRC20:33
*** asalkeld has joined #openstack-relmgr-office20:49
*** nikhil_k|vacay is now known as nikhil_k21:01
*** asalkeld has left #openstack-relmgr-office21:47
*** nikhil_k is now known as nikhil_k|vacay21:56
*** zaneb has joined #openstack-relmgr-office22:45
*** zaneb has quit IRC23:30
*** zaneb has joined #openstack-relmgr-office23:43

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