Tuesday, 2015-09-29

*** dims has joined #openstack-relmgr-office00:24
*** bdemers has quit IRC00:34
*** bdemers has joined #openstack-relmgr-office00:35
*** bdemers has quit IRC01:09
*** bdemers has joined #openstack-relmgr-office01:20
*** bdemers has quit IRC01:45
*** bdemers has joined #openstack-relmgr-office01:46
*** dims has quit IRC02:09
*** dims has joined #openstack-relmgr-office03:09
*** dims has quit IRC03:16
*** bnemec has quit IRC03:17
*** nikhil_k has joined #openstack-relmgr-office04:16
*** nikhil has quit IRC04:18
*** aukhan has joined #openstack-relmgr-office04:33
*** dims has joined #openstack-relmgr-office05:13
*** dims has quit IRC05:18
*** sileht has quit IRC05:33
*** openstackgerrit has quit IRC06:16
*** openstackgerrit has joined #openstack-relmgr-office06:16
*** armax has quit IRC06:24
*** dtantsur|afk is now known as dtantsur06:33
ttxack06:43
ttxflaper87: ping for quick release status update08:31
flaper87ttx: here08:32
ttxflaper87: wanted to discuss RC2 with you08:32
flaper87ttx: Glance's, I guess!08:32
ttxwe'll have to do one later to catch translations, likely early next week08:33
ttxno, Zaqar08:33
flaper87ah, translations08:33
ttxany reason to do one before ?08:33
flaper87no reasons08:33
flaper87There are no standing backports that'd require an early RC208:33
ttxok, let's wait then. keep me posted if that changes08:33
ttxKiall: ping for quick release status update08:36
Kiallttx: heya08:36
ttxKiall: we'll have to do a RC2 for translations early next week. Any reason to rush another RC in the mean time ?08:36
KiallSo, as far as I'm aware, we have one issue which would be nice to get an rc2 for - but might not happen - bumping global-requirements for python-designateclient (we use it internally, as does searchlight)08:37
Kiall(us + searchlight need the newer version, heat/trove also use it, but work with the version in g-r currently)08:37
ttxKiall: depending on which projects are affected we can consider that. We'll have to branch requirements first (should be done today)08:38
ttxwe'd liekly do that at the same time as the translations update08:38
Kiallttx: Yea, it means anyone affected would need a new rc - which sucks, so it's probably reasonable to leave as is knowing that 99% of people will use the latest, as will packaers08:38
Kiallpackagers*08:38
ttxbut nothing in master that you urgently need in becaus ethat invalidates all RC1 testing, right08:38
KiallNot to my knowledge anyway.. We have our IRC meet tomorrow, and chances are someone will raise something there..08:39
ttxok08:39
ttxKiall: thx!08:40
Kiallno problem08:40
ttxjohnthetubaguy: ping me when around08:40
Kiallttx: can I has you to create a rc2 milestone on LP?08:40
Kiall(We'll need one anyway, useful to tag bugs there right out if any come about)08:41
ttxKiall: well, we usually wait to do that, since it seems to result in my experience in a loss of testing of the current RC08:42
ttxKiall: people stop testing RC1 when they know a RC2 is cooking08:43
ttxso we usually try to delay opening RC2 milestone08:43
KiallLol - that makes no sense, and so much sense. heh. OK08:43
ttxMaybe in a couple of days08:43
KiallK08:43
ttxKiall: I mean, *we* know that there will be a RC2, but we also are the people that will test it anyway08:44
ttxKiall: packagers for example just stop packaging RC1 when they realize a RC2 is cooking08:44
ttxand we kinda want them to work on RC1 packaging and anticipate issues08:44
Kiallthat I can understand :)08:44
ttxbut then like all things it's a trade-off. When the pain of not having the milestone is too big it's just simpler to create it08:45
KiallPain is fine, we can label any bugs we find..08:47
*** dtantsur is now known as dtantsur|brb08:51
johnthetubaguyttx: hi, around now, if thats helpful08:58
ttxjohnthetubaguy: yeah, quick release status update08:58
johnthetubaguysure thing08:58
ttxjohnthetubaguy: nova will need a RC2 to catch translations, ETA next Tuesday08:58
ttxdo you need one before then ?08:59
johnthetubaguyyes, +1 for that one08:59
johnthetubaguyso we do have some nasty bugs: https://bugs.launchpad.net/nova/+bugs?field.tag=liberty-rc-potential08:59
ttxanything that landed in master that you would like to include, that invalidates RC1 testing to the point where rushing a RC2 is useful ?08:59
johnthetubaguythis one is tempting: https://review.openstack.org/#/c/228304/09:00
ttxhmm, maybe those criticals could warrant doing a RC2 this week09:00
johnthetubaguyyeah, the other critical is a little overkill, but handy09:00
ttxunless they are sufficiently narrow09:00
johnthetubaguyits more one the the schedule filters stopped working09:01
johnthetubaguythe other one, does break live upgrades, so that is one I would consider worthwhile09:01
ttxjohnthetubaguy: if we do one, I'd like to close it ~ tomorrow ideally09:01
johnthetubaguyyeah, that makes sense09:02
ttxjohnthetubaguy: shall we open the milestone and start the work now ?09:02
johnthetubaguyso I will go double check about that upgrade one09:02
johnthetubaguyjust make sure its as serious as I suspect it is, before we do another RC build09:03
ttxok, ping me when you're ready to open the milestone09:03
*** dims has joined #openstack-relmgr-office09:16
*** dims has quit IRC09:22
*** dims has joined #openstack-relmgr-office09:47
*** dtantsur|brb is now known as dtantsur09:49
sdaguettx: so... when would be least disruptive to cut the devstack stable branch? Last time it led to realizing something was funky in upgrading from kilo to master10:33
sdagueor, more importantly, do all the projects have stable branches now?10:33
johnthetubaguyttx: so been digging not sure I got the the bottom of how serious the bug actually is yet10:35
johnthetubaguyttx: well, slightly correction, we don't think its actually that serious, basically build retries fail during the upgrade process, I think that can wait a week at this point10:36
*** dtantsur is now known as dtantsur|brb10:54
*** aukhan has quit IRC10:57
ttxsdague: all except Swift. I'd say we can cut it once we are done with the requirements stable/liberty branch11:31
ttxthat should happen today. Once we are confident that didn't break anything we can move to devstack. Tomorrow maybe ?11:31
ttxjohnthetubaguy: noted11:32
sdaguettx: sounds reasonable11:40
sdaguethe fallout will happen with grenade if it's going to happen11:41
sdaguewed is my less busy day so if we do it first think wed morning, I can play run around and try to fix whatever is bonkers11:42
ttxsounds good11:42
*** gordc has joined #openstack-relmgr-office11:48
*** bdemers has quit IRC11:49
*** dtantsur|brb is now known as dtantsur11:52
*** dims_ has joined #openstack-relmgr-office12:36
*** dims has quit IRC12:40
ttxgordc: quick ping for release status update12:44
gordcttx: hi, no blocking bugs found so far. just one low/medium bug which we can probably just include in next stable.12:47
ttxgordc: we'll do a RC next week to catch latest translations, maybe we can include a few safe fixes then12:47
ttx(ETA: next Wednesday)12:48
ttxbut no urgency12:48
gordcttx: oh ok. in that case, i'll backport it if the fix comes in on time.12:48
gordcthanks for heads up12:48
ttxack, thx!12:48
ttxgordc: oh, another quick question12:49
ttxhttps://blueprints.launchpad.net/ceilometer/+spec/declarative-snmp-metrics12:49
ttxand12:49
ttxhttps://blueprints.launchpad.net/ceilometer/+spec/events-rbac12:49
ttxoh, done for rc1. Ignore me12:50
gordcignored :)12:50
*** dims_ has quit IRC12:53
ttxjohnthetubaguy: fwiw status on https://blueprints.launchpad.net/nova/+spec/libvirt-spice-video-sound-driver looks a bit weird, you might want to check it out12:57
johnthetubaguyttx: yeah, the code is up for review, its not implemented12:58
johnthetubaguyttx: thats for the heads up there12:58
ttxnp12:59
*** dims has joined #openstack-relmgr-office13:01
*** mriedem_away is now known as mriedem13:07
mesteryttx: Looks like we'll need a Neutron RC2 for this one: https://bugs.launchpad.net/neutron/+bug/149903313:10
openstackLaunchpad bug 1499033 in neutron "Add Liberty release milestone" [High,In progress] - Assigned to Henry Gessau (gessau)13:10
mesteryThe team discussed this at the meeting yesterday and we would like to have this, so lets prep for that.13:10
ttxmestery: ok, so we'll have a RC next week around Wednesday to catch the latest translations. Should we do this one before, or should we wait ?13:11
ttxBasically how disruptive is this issue to RC1 testing ?13:11
mesteryttx: We're fine waiting until next week.13:11
mesteryttx: It won't disrupt RC1 testing at all13:11
ttxyeah, that's my understanding as well13:12
mesteryttx: I've got a liberty-rc-potential tag in LP now, we're targeting potential RC2 bugs there13:12
ttxSo let's put it on the backlog for now13:12
mesteryack13:12
mesterythanks ttx13:12
ttxHad a few extra questions for you regarfing a number of mistargeted blueprints13:12
mesteryAck, please go ahead, I'm here13:12
ttxmestery: https://blueprints.launchpad.net/neutron/+spec/onos-neutron-interaction13:12
ttxhttps://blueprints.launchpad.net/neutron/+spec/service-function-chaining-using-openflow13:12
ttxhttps://blueprints.launchpad.net/neutron/+spec/ml2-ovs-qos-with-bwlimiting13:13
* mestery looks13:13
ttxsome of them migth be RC1 material13:13
ttxsome others might have been in liberty-313:13
ttx(they are "implemented" but do not appear in any milestone page)13:14
mesteryThe first one (https://blueprints.launchpad.net/neutron/+spec/onos-neutron-interaction) is done completely in networking-onos, so should be targeted to liberty13:14
mesteryI'll mark it as Liberty-313:14
ttxok13:14
mesteryCan you target https://blueprints.launchpad.net/neutron/+spec/onos-neutron-interaction to Liberty-3? It won't let me (it's not a choice)13:15
mesteryLooking at the others now too13:15
ttxok let me do that13:15
ttxprobably need to reopen the milestone13:15
mesteryAck13:15
ttxdone13:16
mesteryThis one (https://blueprints.launchpad.net/neutron/+spec/common-service-chaining-driver-api) I don't uinderstand, I'll talk to Vikram and figure it out13:16
mesterySorry13:16
mesteryhttps://blueprints.launchpad.net/neutron/+spec/service-function-chaining-using-openflow13:16
mesteryThat one ^^^ claims to be a part of the previous one13:16
mesteryConfusing, I'll sort with vikram13:16
ttxyeah, a bit unclear13:16
mesteryhttps://blueprints.launchpad.net/neutron/+spec/ml2-ovs-qos-with-bwlimiting can be marked Liberty-3, it was completed then13:16
ttxok, will do13:17
ttxthx!13:17
mesterythank you ttx!13:18
*** bdemers has joined #openstack-relmgr-office13:19
ttxnikhil_k: quick ping on release status13:56
ttxredrobot, same ^13:57
*** bswartz has joined #openstack-relmgr-office14:00
bswartzttx: RC2 is still a day away at least for Manila14:00
bswartzbut at least new bugs have stopped coming in and the count is strictly declining now14:00
ttxbswartz: we can create the milestone and you can target things that are fixed in master to it and start backporting if you want14:01
ttx(and I can start approving backports through)14:01
bswartzttx: even though we're expecting more patches?14:01
ttxbswartz: if there is a critical thing you absolutely need in, maybe better to wait14:02
ttxbswartz: so let's open it tomorrow ?14:02
bswartzit's mostly small stuff that's important and just hasn't been merged yet14:02
bswartzso we're working on it today14:02
ttxbswartz: ok, ping me when all you want in it is merged in master, then14:03
bswartzokay that could be later today or early tomorrow14:03
ttxdhellmann: I think we should branch stable/liberty requirements now and approve https://review.openstack.org/228805 after14:04
ttxfungi: should we line up approvals first ? We want that merged shortly after the branch creation so they can start diverging14:04
ttxbswartz: ack14:04
dhellmannttx: let me check if that reno addition merged...14:05
dhellmannttx: do we need https://review.openstack.org/#/c/226560/ ?14:05
fungittx: i think it's a bit of a race in either direction. either you approve before and then branch from an earlier commit and some stable changes are incorrectly tested against the new additions, or you merge after and some master changes are tested against stale requirements14:06
dhellmannfungi, ttx: we can control what's approved, right?14:07
fungittx: once that change merges, consider somewhere on the order of 30 minutes needed for it to take effect14:07
fungidhellmann: yep, you can. you just might want/need to recheck some things which get tested in the few minutes of grey area, if any14:07
dhellmannk14:08
ttxfungi: right, so will unfreeze master requirements 30 minutes after the change merges14:08
ttxbut create the branch before we approve it14:08
fungisounds safe enough14:09
ttxdhellmann: should the reno change merge before or after the branch point ?14:09
*** sigmavirus24_awa is now known as sigmavirus2414:10
ttxit should not trigger any requirement sync right ?14:10
ttx(yet)14:10
dhellmannttx: that depends on whether we need it in the stable branch. We can always backport it, but it seems like we might want it -- right, no sync yet14:10
ttxok, we should get it in before then, that will save us a backport14:12
ttxwe want it in post-release stable/liberty14:13
dhellmannttx: sounds good, want to approve it?14:14
ttx+2ed14:14
ttxneeds another +2/approve14:15
ttxthen we can branch as soon as that merges14:15
* ttx glances at zuul queue14:15
ttxabout 1-2 hours away14:15
dhellmannI can create the branch14:16
redrobotttx we've identified 2 barbican bugs that will require an RC214:16
dhellmannand I'm just going to approve the addition14:16
ttxyeah, maybe we should just create the branch first and backport after14:16
ttxI'd like to catch any issue while we are all awake14:16
ttxredrobot: are they all fixed in master yet ?14:16
dhellmannttx: sure, that works14:16
redrobotttx not yet14:17
redrobotttx we should have a patch today or tomorrow.14:17
ttxredrobot: ok, as soon as they are, we can open a RC2 milestone and backport/mertge/release that14:17
ttxping me when all you need in it is up on master14:17
redrobotttx will do thanks14:17
ttxdhellmann: ok, let's do this. Shall I use Gerrit UI or should we reuse a magic script14:18
dhellmannttx: the script requires a tag and milestone, so you should probably just use gerrit14:18
ttxack14:18
ttxon it14:19
dhellmannI can prepare the patch for the .gitreview file14:19
ttxyep14:19
ttxok, stable/liberty branched on HEAD14:20
ttxfungi: we can approve https://review.openstack.org/22880514:21
ttxremoved my W-114:21
dhellmannttx: https://review.openstack.org/228930 sets up .gitreview14:23
ttxok maybe we'll wait for teh job change and test that with it14:24
dhellmannttx: ++14:25
ttxnikhil_k, david-lyle: ping me when around for quick release status update14:25
dimsyay stable/liberty requirements! :)14:31
ttxdhellmann: I listed the content of the status update for this week, in case you need to do any. See "20150929 update content:" under https://etherpad.openstack.org/p/liberty-final-release14:33
ttxdhellmann: let me know if you have questions14:33
ttxI'll try to cover as much as I canduring my time but there will be leftovers as always14:33
dhellmannttx: reading now14:33
ttxmy best try at a telemarketer script14:34
dhellmannttx: so "open the RC window" means we change ACLs? or that we approve patches they have 2 +2 on already?14:34
ttxno, open the RC window means creating the milestone on LP and starting to approve stable/liberty patches lined up (as long as they are fixed in master and targeted to RC2 in LP)14:36
dhellmannok, the LP part was clear, it was how the patches actually land that wasn't, because the ACLs are restricted right now14:36
ttxright, approval rule is: if it's targeted to the RC and has been fixed in master (and doesn't seem obviously wrong / featury / plain dangerous) it's OK14:38
ttxif it seems wrong it should trigger a quick discussion with the PTL to make sure we get the risk right14:38
dhellmannttx: ok, and who has the permissions needed in gerrit to W+1 those patches is the real question, I guess. Are you and I looking at patches? Or is it the core review teams?14:39
ttx*like if the change changes the database model completely, it's not really RC material14:39
ttxdhellmann: it's generally us giving it the final +2/approve, although the pTL can give it too14:39
ttxgenerally core teams can't approve there14:40
ttxthe trick being we have no guarantee the patch in stable/liberty was merged in master, it's a manual check14:40
ttxnecessary to make sure we don't regress14:40
ttxand checkign that the bug is targeted to the RC makes sure we communicate what was changed between RCs properly14:41
ttxwhich is important for testers14:41
nikhil_kttx: hi14:42
dhellmannttx: ok, got it14:42
ttxnikhil_k: ohai! Wanted to check on your needs for a RC2. Any release-critical issues justifying an early RC respin ?14:42
ttxOr can we wait for the translations RC respin next week ?14:43
ttx(should happen ~ next Thursday)14:43
nikhil_kttx: this one is quite imp https://bugs.launchpad.net/glance/+bug/150036114:44
openstackLaunchpad bug 1500361 in Glance "Generated config files are completely wrong" [High,In progress] - Assigned to Erno Kuvaja (jokke)14:44
nikhil_ksomeone proposed changes using conf auto-gen and they messed up last min14:44
ttxah, hm, this one might actually impact testing14:44
jokke_I did :(14:45
nikhil_kyeah14:45
ttxso we might want to roll a RC2 earlier than next week14:45
nikhil_kand it's merge in flight so we are good14:45
jokke_yes that was brought up by zigo trying to build debian packages14:45
nikhil_kttx: I think sycn on thursday would help14:45
ttxnikhil_k: how about we open a RC2 window tomortrow and try to close it on Thursday then ? That way we can include the other fix you know about to it14:45
nikhil_kttx: sounds good14:45
ttxnikhil_k: I'll be in touch tomorrow. In the mean time, get that one fixed in master14:46
ttxnikhil_k: thanks!14:46
nikhil_kttx: sure, it's already in-flight merge!14:46
nikhil_kttx: https://bugs.launchpad.net/glance/+bug/1441453 is soon going to be out of RC2 (fyi)14:47
openstackLaunchpad bug 1441453 in Glance "Image members CRUD doesn't generate notifications which impacts searchlight RBAC." [High,In progress] - Assigned to Lakshmi N Sampath (lakshmi-sampath)14:47
nikhil_kThanks!14:47
nikhil_k(out of RC2 as in no RC backport)14:47
ttxok14:47
*** armax has joined #openstack-relmgr-office14:51
*** dims has quit IRC15:04
*** dims__ has joined #openstack-relmgr-office15:16
david-lylettx: o/15:21
ttxdavid-lyle: quick update on how that RC1 is going for you so far15:22
ttxdavid-lyle: we'll have a RC respin late next week to include translations, any reason you might need a RC respin earlier ?15:22
ttxlike a bug that screws up all testing ?15:23
david-lylewe have one critical issue which is actually in django_openstack_auth, but otherwise no major issues in horizon15:23
ttxright, that one can be fixed anytime15:23
ttxand we'll do a point release on the stable branch15:23
david-lyleonce we have a fix for the d-o-a issue, we'll need a release15:23
david-lyleyup15:23
ttxdavid-lyle: in other news I have a few blueprints that seem to miss proper milestone targets / series goal15:24
ttx    https://blueprints.launchpad.net/horizon/+spec/data-processing-edit-templates15:24
ttx    https://blueprints.launchpad.net/horizon/+spec/horizon-sahara-module-selenium-integration-tests15:24
ttx    https://blueprints.launchpad.net/horizon/+spec/project-disabling-warning15:24
ttx    https://blueprints.launchpad.net/horizon/+spec/trove-replication-v1-support15:24
ttx    https://blueprints.launchpad.net/horizon/+spec/remove-unittest215:24
ttxcould you look them up and set the milestone and series goal accordingly ?15:24
ttxThat may require reactivating the milestone15:25
ttxtemporarily to add it15:25
ttxI can do the changes if you tell me what to change15:25
david-lyleok, yeah, I've noticed I can't set to a past milestone15:25
*** dtantsur is now known as dtantsur|afk15:26
david-lylesecond on is kilo, do we want to go back that far?15:26
david-lyles/on/one/15:26
ttxdavid-lyle: yes, taht way it won't reappear in future script runs15:26
ttxyes tell me which milestone it landed and I'll fix it15:27
david-lylettx: https://blueprints.launchpad.net/horizon/+spec/data-processing-edit-templates  -> L-315:32
ttxdavid-lyle: done15:33
david-lylehttps://blueprints.launchpad.net/horizon/+spec/horizon-sahara-module-selenium-integration-tests,  https://blueprints.launchpad.net/horizon/+spec/trove-replication-v1-support,  https://blueprints.launchpad.net/horizon/+spec/remove-unittest2  -> K-315:33
david-lylehttps://blueprints.launchpad.net/horizon/+spec/project-disabling-warning is not complete, author updated status incorrectly15:33
ttxdavid-lyle: ok, all set. Thx!15:38
david-lylethanks ttx15:38
ttxit seems our branch didn't break the world just yet15:42
*** thingee has joined #openstack-relmgr-office15:50
thingeettx: ping15:55
ttxthingee: hey, quick release status15:55
ttxthingee: do you urgently need a RC2 ?15:55
ttxI suspect we need to do one due to the licensing issue15:55
thingeettx: that and the recent migration placeholders patch https://review.openstack.org/#/c/228107/15:56
ttxwe have one RC respin planned for enxt Tuesday to catch last translations, so the question is, should we wait15:56
ttxIt feels safe to wait, doesn't invalidate testing ?15:56
thingeenot worried about waiting15:57
ttxok, let's wait then15:57
ttxI was cleaning up and found a few mistargeted bps, too15:57
ttx    https://blueprints.launchpad.net/cinder/+spec/extract-brick15:57
ttx    https://blueprints.launchpad.net/cinder/+spec/pure-manage-snapshot15:57
ttx    https://blueprints.launchpad.net/cinder/+spec/non-disruptive-backup-in-vnx15:57
ttx    https://blueprints.launchpad.net/cinder/+spec/support-hosttype-on-attach15:57
ttxcould you let me know which milestones I should target them to ?15:57
ttx(that may involve reopening closed milestoens so I'll do it for you)15:57
thingeeextract brick - L-115:59
thingeepure-manage-snapshot is L-315:59
thingeenon-disruptive backup is L-316:00
thingeesupport-hosttype-on-attach is L-316:02
thingeettx: thanks16:02
ttxthingee: will fix16:02
*** TravT has quit IRC16:11
*** TravT has joined #openstack-relmgr-office16:13
ttxthingee: done16:36
ttxdhellmann: I'm going to dinner. I'll let you chase down the last 416:37
dhellmannttx: ack16:37
dhellmannmorgan, SergeyLukjanov, SlickNik, stevebaker : let me know when you have a minute to catch up on status16:37
*** dims__ has quit IRC16:38
*** dims__ has joined #openstack-relmgr-office16:39
SergeyLukjanovdhellmann, hi, I'm here16:42
*** stevemar has joined #openstack-relmgr-office16:47
stevemarmorgan: o/16:47
morgandhellmann: stevemar is here. We can sync up now16:47
* morgan is delegating the bull of end of release to stevemar.16:48
morganBulk*16:48
mtreinishmorgan: I think you had it right the first time...16:51
morganmtreinish: hehe16:52
dhellmannSergeyLukjanov: have you identified any release-critical issues that affect testing?16:53
dhellmannstevemar, morgan : let me catch up with SergeyLukjanov first16:53
SergeyLukjanovdhellmann, nope, everything is ok still ;)16:54
SergeyLukjanovdhellmann, I've release 0.11.1 client yesterday16:54
dhellmannSergeyLukjanov: great! how are things looking with translations? we expect to do RC2s next week to pull in final translations, are you seeing patches for those?16:54
SergeyLukjanovdhellmann, not really16:55
SergeyLukjanovdhellmann, there are not too many translations for sahara16:55
dhellmannSergeyLukjanov: ok, that's ok, there's time16:55
dhellmannSergeyLukjanov: ok16:55
SergeyLukjanovdhellmann, thx16:55
dhellmannSergeyLukjanov: we have https://blueprints.launchpad.net/sahara/+spec/keystone-sessions marked as implemented, but not targeted, do you know which milestone that should go in?16:55
SergeyLukjanovdhellmann, I will check and update to the correct target16:56
dhellmannSergeyLukjanov: ok, if it is for a closed milestone you might need to re-open it first16:57
SergeyLukjanovdhellmann, yup, I'll do it, it's from b316:57
dhellmannstevemar, morgan : how are things looking, have you had any release-critical bugs filed yet?16:57
dhellmannSergeyLukjanov: ok, I think you should have permissions to do that but let me know16:57
dhellmannSergeyLukjanov: "b3"?16:58
SergeyLukjanovdhellmann, liberty-3 (3.0.0.0b3 version :) )16:58
SergeyLukjanovdhellmann, I have permissions16:58
dhellmannah, ok16:58
morganI havenotseen any. stevemar ?16:59
stevemardhellmann: morgan nothing crazy, i wouldn't mind adding: https://review.openstack.org/#/c/215870/16:59
stevemarmorgan: dhellmann i was going to ask in the keystone meeting today16:59
stevemarbut i think that's the only potential candidate ^17:00
dhellmannstevemar: ok, if that doesn't hold up your current testing it could go into the RC2 we have planned for translations next week17:00
morganAre we getting auto proposals or do we nee dro backport?17:00
dhellmannI don't know about "autoproposals" so I would go ahead and set up the backport17:01
dhellmannor do you mean the translations?17:01
morganTranslations17:01
dhellmanngood question -- how did that work in the past? (oslo didn't really have those)17:01
morganWe used to get translations pre rc17:02
dhellmannok, I'll catch up with ttx on that tomorrow17:02
dhellmannthat window isn't until next week, so we have time17:02
dhellmannstevemar, morgan : there are 2 blueprints marked as implemented but not targeted17:04
dhellmannhttps://blueprints.launchpad.net/keystone/+spec/remove-oslo-incubator and https://blueprints.launchpad.net/keystone/+spec/remove-py26-hacks17:04
dhellmannstevemar, morgan : can you target those to the right milestone for us?17:05
stevemardhellmann: yeah, i think remove-oslo-incubator was liberty-317:05
stevemarbut yes, i will17:05
dhellmannstevemar: you will need to re-open the milestone, so let me know if you don't have permission to do that and I can fix it17:05
morganIll make stevemar admin for everything in lp today too17:06
stevemardhellmann: morgan sorry, i was just on the phone arranging japan travel17:07
dhellmannstevemar: np17:07
*** armax has quit IRC17:25
stevemardhellmann: back, sorry about that. i'm going to mark those guys in their appropriate releases17:34
SlickNikdhellmann: around?17:34
SlickNikLet me know when's a good time to catch up.17:34
stevemardhellmann: i'll give you an update post-keystone-meeting if we need an rc217:34
*** mriedem has quit IRC17:38
*** mriedem has joined #openstack-relmgr-office17:43
*** sileht_ has joined #openstack-relmgr-office17:44
*** sileht_ is now known as sileht17:45
*** sileht has quit IRC17:45
dhellmannSlickNik: here17:45
dhellmannstevemar: ack17:45
*** sileht has joined #openstack-relmgr-office17:46
dhellmannSlickNik: have you identified any critical bugs that affect testing and would need an RC2 before next week?17:46
*** sdague has quit IRC17:58
*** dims has joined #openstack-relmgr-office18:00
*** dims__ has quit IRC18:02
*** sdague has joined #openstack-relmgr-office18:02
dhellmannttx, lifeless: thinking about how we want to roll out release notes (maybe I'm early for this), I am making some notes in https://etherpad.openstack.org/p/reno-rollout18:19
lifelessdhellmann: heh, I've already been telling folk to use it ;)18:25
dhellmannlifeless: great! I haven't made any public announcements yet, because there are some patches with docs I'd like to land first18:25
*** armax has joined #openstack-relmgr-office18:29
lifelessdhellmann: seems good - see my comment18:32
dhellmannlifeless: makes sense18:37
*** nikhil has joined #openstack-relmgr-office18:42
*** nikhil_k has quit IRC18:44
*** stevemar has quit IRC19:01
*** stevemar has joined #openstack-relmgr-office19:08
*** sileht has quit IRC19:39
*** sileht has joined #openstack-relmgr-office19:45
*** sileht has quit IRC19:47
*** sileht has joined #openstack-relmgr-office19:48
*** bdemers has quit IRC20:04
*** bdemers has joined #openstack-relmgr-office20:05
*** stevemar has quit IRC20:25
*** Kiall has quit IRC20:27
*** dims has quit IRC20:28
*** stevemar has joined #openstack-relmgr-office20:29
*** dims has joined #openstack-relmgr-office20:29
*** Kiall has joined #openstack-relmgr-office20:29
*** bswartz has quit IRC20:37
dimsdhellmann: looks like the flood gates opened on g-r repo :)20:41
dhellmanndims: yeah, let's not be hasty with approvals20:41
dimsdhellmann: just +120:41
dims's for now :)20:41
dimsmtreinish and i were talking that we should probably wait till grenade and devstack etc are branched20:42
dhellmanndims, mtreinish : makes sense -- we should capture that in the end of release checklist https://etherpad.openstack.org/p/liberty-end-of-release-requirements-checklist20:45
lifelessdims: yes21:14
lifelesserm, dhellmann dims: yes21:14
dimsdhellmann: done21:17
dhellmanndims: ty21:17
*** bdemers has quit IRC21:17
*** gordc has quit IRC22:05
*** mriedem is now known as mriedem_away22:09
*** mriedem_away has quit IRC22:09
*** sigmavirus24 is now known as sigmavirus24_awa22:19
*** stevemar has quit IRC22:38
*** jhesketh has quit IRC23:01
*** jhesketh has joined #openstack-relmgr-office23:02
*** dims_ has joined #openstack-relmgr-office23:19
*** dims has quit IRC23:22
*** dims_ has quit IRC23:31
*** dims_ has joined #openstack-relmgr-office23:32
*** flaper87 has quit IRC23:32
*** johnthetubaguy has quit IRC23:32
*** flaper87 has joined #openstack-relmgr-office23:32
*** johnthetubaguy has joined #openstack-relmgr-office23:34

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