Friday, 2016-03-04

*** sdake has quit IRC00:09
*** sigmavirus24 is now known as sigmavirus24_awa00:15
flwangdhellmann: i'm waiting for the commit from jenkins   the patch has been merged though00:25
*** grabiel has joined #openstack-release00:30
*** grabiel has quit IRC00:33
dhellmannflwang : I don't understand what you mean?00:34
*** thinrichs has left #openstack-release00:34
flwangdhellmann: i'm waiting for this patch "Support metadata update issue for v2"00:34
dhellmannflwang : you said it has been merged, but you're still waiting?00:35
flwangbut seems there is jenkins commit yet, like this:      Merge "Fix the TTL issue of subscriptions for MongoDB"00:35
flwangdhellmann: can you open this link ?00:35
amrithdhellmann, we can freeze requirements. But can I release another client in a couple of days for a feature that has an FFE open?00:35
amrithsorry, s/freeze requirements/freeze client/00:36
dhellmannflwang : yes. If you can't, try
dhellmannamrith : it won't show up in the gate with the requirements frozen00:36
flwangdhellmann: i can, i mean based on my understand, i need to see a commit from Jenkins user with a tile like "Merge: xxxx" and use that commit id to do the release, right?00:37
dhellmannflwang : there won't always be a merge commit. What are you trying to do, find the SHA to use?00:37
amrithdhellmann, what do you suggest? server side of change is in and that's why we requested the FFE.00:37
flwangdhellmann: yes00:37
amrithclient side is not in00:37
amrithwon't be in by tonight.00:37
dhellmannflwang : I see your commit merged, and jenkins/gerrit didn't need to create a merge commit for that00:37
flwangdhellmann: ah, so that means i can use 5afb85a175945d5b1cbd571098604000ec92e868 as the SHA to release, right?00:38
dhellmannflwang : yes, that SHA matches your HEAD00:38
flwangdhellmann: so just double confirm, the commit id from "Merge: xxx" commit is not really necessary for release, right? I'm a little bit confused for the two commit ids00:39
dhellmannamrith : I suggest you get the service tagged, and make sure whatever you have for the client today is released, and then we can discuss another update00:39
dhellmannamrith : I'll need to discuss it with ttx tomorrow00:40
amrithdhellmann, one patch coming up00:40
dhellmannamrith : don't forget to update the constraints file and leave a comment on the release request with that url00:40
dhellmannamrith : where is the patch to add the change to the client?00:41
amrithdhellmann, I don't follow. one second. Currently my change(s) are.00:41
openstackgerritFei Long Wang proposed openstack/releases: Release Zaqar Mitaka-3
amrith1. tag trove for m300:41
amrith2. tag python-troveclient00:41
amrithboth of these are in the releases project00:41
dhellmannamrith : look at the instructions in the readme in the releases repo00:42
openstackgerritAlan Pevec proposed openstack/releases: Add Kilo 2015.1.3 stable point release
amrithok, thanks00:42
jrolldhellmann: fyi, I have an ironicclient release coming at some point today. and ironic 5.0 early next week at the latest, but possibly as early as today00:42
dhellmannjroll : ok00:42
*** thinrichs has joined #openstack-release00:43
thinrichsdhellmann: do I take care of the bugs/blueprints/launchpad release/tarball upload?  Or has that been automated?00:44
thinrichsdhellmann: (Once I've pushed to the openstack/release repo for Congress mitaka3)00:44
dhellmannthinrichs : the release artifact should be uploaded. If there were any commits with "Closes-Bug" in them, those bugs should have new comments with the release number. The release team doesn't do anything with blueprints, so if you're still using those you can update their status.00:45
dhellmannoh, I thought I already did congress...00:45
openstackgerritamrith proposed openstack/releases: Release Trove
dhellmannthinrichs : yeah, I've already processed congress00:45
dhellmannthinrichs : so everything should be done, except the blueprints00:46
thinrichsdhellmann: are we still using launchpad to track releases?  On launchpad, mitaka3 is still open.00:47
dhellmannthinrichs : no, we don't use launchpad any more.
openstackgerritamrith proposed openstack/releases: Release python-troveclient version 2.1.0
amrithdhellmann, those are the two changes to the openstack/releases project. Now will do the changes to constraints etc.,00:47
thinrichsdhellmann: Great!  Are people not using blueprints either?  Just specs?  Bugs are still on launchpad though.00:49
dhellmannthinrichs : some teams still use blueprints, but the release team doesn't manage them00:49
dhellmannthinrichs : and yes, bugs are still on LP. Those should end up as "fix released" when a fix merges, and then the release script adds a comment with the actual release version number00:49
dhellmannthinrichs :
thinrichsGot it.00:50
thinrichsdhellmann: I remember reading that email.  Thanks.00:52
amrithdhellmann, changes are:,,
dhellmannamrith : if you add a comment on the client release request linking to the constraint update, that will help me keep track (the release patches show up on my dashboard automatically)00:53
amrithI just did00:53
dhellmannamrith : excellent00:53
amrithsorry about that.00:53
amrithif you'd check that the three commits contain the things you require that'd be great. no change required to global-requirements.txt00:53
dhellmannand gerrit is timing out00:54
amrithsorry, I broke gerrit.00:55
amrithok, fixed it. should be up ;) I'm going to head to dinner. will check back after and see if there are any comments for me. thx dhellmann sorry about the delay. was on the road today and twitter was the only way I could think of to reach you ;)00:56
openstackgerritDoug Hellmann proposed openstack/releases: Release Zaqar Mitaka-3
openstackgerritMerged openstack/releases: Release Trove
openstackgerritMerged openstack/releases: Release python-troveclient version 2.1.0
*** thinrichs has quit IRC01:07
*** thinrichs1 has joined #openstack-release01:07
dhellmannflwang : the zaqar release patch keeps running into issues with git hanging. I don't think it has anything to do with your patch or repo. I'll keep trying to get it to land.01:11
openstackgerritDoug Hellmann proposed openstack/releases: Release Zaqar Mitaka-3
flwangdhellmann: thanks, the client release is coming soon01:13
openstackgerritMerged openstack/releases: Release Zaqar Mitaka-3
*** kzaitsev_mb has quit IRC01:22
dhellmannflwang : ok, your tag is in place and the tarball job is queued up. I'll check back in later for the client release request.01:26
flwangdhellmann: cool, thanks01:27
*** sdake has joined #openstack-release01:28
openstackgerritFei Long Wang proposed openstack/releases: Release python-zaqarclient 2.0.0
*** sdake has quit IRC01:35
openstackgerritFei Long Wang proposed openstack/releases: Release python-zaqarclient 1.0.0
openstackgerritJim Rollenhagen proposed openstack/releases: python-ironicclient 1.2.0
jrolldhellmann: that's ironicclient, ironic will be another day01:44
* jroll does u-c patch now01:44
dhellmannjroll : ok01:44
dhellmannflwang : don't forget the patch to update the constraints file in openstack/requirements for that zaqar client release01:44
flwangdhellmann: ah, yep, i will do that right now, thanks for the heads up01:45
jrolldhellmann: thank you as always for all the awesome work y'all do <301:45
flwangdhellmann: just posted the requirements change, pls revisit, thanks01:55
dhellmannflwang : processing it now01:55
dhellmannjroll : thanks for bearing with us during the rough patches01:55
jrolldhellmann: I honestly have no complaints :)01:56
openstackgerritMerged openstack/releases: Release python-zaqarclient 1.0.0
flwangdhellmann: thank you!!!02:01
dhellmannflwang : no problem, thank you!02:01
openstackgerritMerged openstack/releases: python-ironicclient 1.2.0
*** thinrichs1 has quit IRC02:19
*** sdake has joined #openstack-release02:39
*** sdake has quit IRC02:51
*** sdake has joined #openstack-release02:52
*** sdake has quit IRC02:52
*** amrith is now known as _amrith_03:15
*** dims has quit IRC03:40
*** dims has joined #openstack-release03:43
*** dims has quit IRC03:44
*** openstack has joined #openstack-release04:29
*** dtantsur|afk has quit IRC04:30
*** openstack has quit IRC04:30
*** openstack has joined #openstack-release04:32
*** dtantsur has joined #openstack-release04:32
*** openstack has quit IRC04:34
*** openstack has joined #openstack-release04:35
*** jokke_ has quit IRC04:36
*** openstack has quit IRC04:36
*** openstack has joined #openstack-release04:37
*** openstack has quit IRC04:39
*** openstack has joined #openstack-release14:07
jokke_I don't mind if it takes day or two to get it tagged as long as we don't tag at Fri, if looking like so then we can just overflow to the next week :)14:09
dhellmannredrobot : we need to tag a barbican release today. Where do things stand?14:10
*** mriedem has joined #openstack-release14:15
mriedemttx: dhellmann: in the stable meeting this week we talked about a possible summit session on stable branches and discussing how long to keep kilo/liberty around, was the release team having any session that could overlap with that?14:18
mriedemi'm torn a bit on actually devoting an entire session to just talking about how long we should keep kilo/liberty around14:18
mriedembut it does require stable/release/qa/infra people14:18
*** amotoki has quit IRC14:21
openstackgerritMerged openstack/releases: Add missing trove-dashboard mitaka-2 release
*** dansmith is now known as superdan14:29
openstackgerritamrith proposed openstack/releases: Release of trove-dashboard
*** openstackgerrit_ has quit IRC14:36
*** openstackgerrit_ has joined #openstack-release14:37
openstackgerritStéphane Albert proposed openstack/releases: Release python-cloudkittyclient 0.5.0
*** betherly has joined #openstack-release14:52
*** sheeprine has joined #openstack-release14:54
ttxI'll process trove-dashboard
*** tonyb has quit IRC15:01
dhellmannttx: ack15:01
ttxthen work on the M3 announcement15:01
*** tonyb has joined #openstack-release15:01
ttxdhellmann: can you chase down redrobot ?15:01
dhellmannyes, I'll work on that15:01
openstackgerritThierry Carrez proposed openstack/releases: Release of trove-dashboard
openstackgerritStéphane Albert proposed openstack/releases: Release python-cloudkittyclient 0.5.0
*** claudiub has joined #openstack-release15:16
claudiubdhellmann: dims: hello. when you have one free second, please review the os-win version bump in global requirements. :)
patchbotclaudiub: patch 288429 - requirements - Bumps os-win version to 0.2.315:17
dimsclaudiub : new features? can you please update the commit message with information?15:17
claudiub^ wow, that's a nifty bot we have here. :D15:17
claudiubdims: sure, will do. :)15:18
ttxdhellmann: M3 announcement email ready, waiting on barbican to hit or miss15:22
ttxprocessing trove-dashboard15:22
*** kzaitsev_mb has quit IRC15:26
dhellmannttx: ack. no response from redrobot yet, but it may be early (I don't know his tz)15:27
openstackgerritMerged openstack/releases: Release of trove-dashboard
dhellmannclaudiub : yeah, we've already made a short list of things to approve, and this isn't on it. if you really really need it, we need to know why15:29
dhellmannttx, dims : I'm going to -2 the other requirements patches, I think, to be safe.15:29
dimsdhellmann : sounds good15:30
*** markmcclain has joined #openstack-release15:31
dhellmannttx: markmcclain says astara should be ready for an m3 next week. should we ask them to go ahead and tag today, with the expectation that they may have feature work to wrap up before RC1?15:32
ttxdhellmann: depends how strongly we want to enforce the m3 deadline for non-managed projects15:33
ttxit's almost a trademark question15:33
ttxIn theory m3 is a moment in time, so there should not be any m3 next week15:34
ttxand yes, they can compensate by doing plenty of ffes15:34
dhellmannso we wouldn't use a 0b3 tag for them next week, and move right to rc1?15:34
*** david_lyle__ has joined #openstack-release15:34
ttxeither they tag now or they skip the 0b3 tag15:34
ttxthat would be my position15:34
dhellmannyeah, that makes sense15:35
ttxsame one we held for projects that missed 0b215:35
markmcclainok... guessing adam_g won't object15:35
dhellmannmarkmcclain: what do you think?15:35
ttxI don't feel extremely strongly about it15:35
dhellmannmarkmcclain : so it's a question of whether you want that b3 tag or not15:35
ttxit's just that if we start doing exceptions it will soon be a free-for-all15:35
dhellmannttx: I like the simplicity of the time-based rule. It's easy to not make lots of exceptions.15:35
claudiubdhellmann: dims: i see. I've updated the commit message. There are just a few commits added since 0.2.2. Basically, 0.2.3 is needed for the neutron-hyperv-agent to properly bind security group rules to ports.15:35
markmcclainttx, dhellmann: right skipping ahead makes the most sense15:36
dhellmannclaudiub : ok, I've added the os-win update to the list15:36
dhellmannmarkmcclain : ok, sounds good15:36
claudiubdhellmann: thanks. :)15:36
dimsdhellmann : the "good" list? :)15:36
dhellmanndims : yes15:37
*** david-lyle has quit IRC15:37
claudiubsooo... i guess there is a good list and a "good" list? :D15:37
dims+2 claudiub15:37
dhellmanndims : since os-win is an openstack project, you can +2a15:37
claudiubyeay, ty. :D15:37
dimsclaudiub : please watch the CI and recheck, may run into merge issues too, just ping us back if you do15:38
claudiubdims: yup, will do. :)15:38
dhellmannttx, dims : this etherpad is driving me nuts, I've created to make it easier to edit15:39
dimsdhellmann ++15:40
*** andreykurilin has left #openstack-release15:49
*** dims is now known as dimsum_15:53
*** mriedem is now known as mriedem_meeting15:55
dhellmannttx: it looks like there's a neutron client release to fix whatever issue 4.1.0 had. Do you want to handle that, or let me know when you're done with tagging and I'll do it?15:57
ttxdhellmann: I'm done with tagging15:59
dhellmannttx: ok, I'll do neutronclient and cloudkitty client15:59
openstackgerritMerged openstack/releases: python-neutronclient 4.1.1
openstackgerritMerged openstack/releases: Release python-cloudkittyclient 0.5.0
dhellmannsheeprine : where do things stand with the cloudkitty 0b3 tag? are you ready?16:13
sheeprinedhellmann: We're pretty much here. Some patches in review need to land in the code and then we'll tag the rc1. One week will be more than enough.16:16
openstackgerritDouglas Mendizábal proposed openstack/releases: Mitaka-3 milestone for Barbican deliverables
dhellmannsheeprine : we need you to decide if you want to tag a milestone 3 release today.16:17
*** david_lyle__ is now known as david_lyle16:17
dhellmannsheeprine : we're ready to announce the milestone and have heard from everyone else...16:18
sheeprineI can tag a milestone today, but it will be lacking some features that we need to review this week. They are written and ready but need review. Is it still fine for you?16:20
sheeprinedhellmann: ^16:20
dhellmannsheeprine : it would be better to go ahead and tag, then have a list of the FFEs that you're going to grant for that other work16:21
*** kzaitsev_mb has joined #openstack-release16:23
sheeprinedhellmann: If you think it's better to do it then I'll tag b3 with that we currently have and grant exceptions for pending features.16:24
dhellmannsheeprine : ok, sounds good. I'm looking at the barbican m3 tag right now, so I can do yours next if you submit that patch.16:24
sheeprinedhellmann: Working on it, will let you know when I'm done.16:25
ttxdhellmann: cloudkitty is cycle-with-intermediary16:26
dhellmannttx: ugh16:26
ttxso it won't do a 0b316:26
ttxit will do a full release16:26
dhellmannsheeprine : sorry, I mixed you up, see ^^16:27
ttxsheeprine: so you actually have a bit more time16:27
ttxa 0.5.0 or 1.0.016:27
dhellmannsheeprine : nevermind, go ahead with your plan to tag next week, sorry for the confusion16:27
sheeprineOkay, I was starting to get worried there, had mixed information ;)16:27
dhellmannyeah, I read my notes wrong, my mistake16:27
ttxdhellmann: I think I'll push the announcement now. No news of barbican ?16:28
sheeprineno worries, in the end we still got time to do a proper release :)16:28
ttxoh wait, I see it16:28
dhellmannttx: yeah, barbican is ready I'm just waiting on the jobs16:29
ttxdhellmann: I'll process it and send the announcement just after16:29
dhellmannttx: sounds good16:30
*** kzaitsev_mb has quit IRC16:30
ttxstuck in check queue for the moment16:30
*** daemontool__ has joined #openstack-release16:30
*** daemontool_ has quit IRC16:34
*** daemontool__ is now known as daemontool16:34
*** bobh has joined #openstack-release16:38
mesterydhellmann: A question for you. I am trying to release new version of "networking-calico", and the "announce-release" job fails:
mesteryI feel as if I'm missing something in the tag message, any ideas?16:39
dhellmannmestery : are you using the release scripts?16:40
*** mriedem_meeting is now known as mriedem16:40
mesterydhellmann: Negatory, though I feel like I should be as I read through them, they look quite nice :)16:40
dhellmannmestery : a while back we started adding specific metadata to the tag comment that the jobs expect to find16:40
dhellmannmestery : that job in particular won't work if you just tag something any more16:40
mesterydhellmann: I see that now, I'm looking and reading hte release-tools16:40
dhellmannso you could generate the announcement by hand in this case16:40
mesterydhellmann: let me read the in release-tools and come back with questions16:40
dhellmannand in the future I recommend using release.sh16:41
mesteryAh, I could16:41
dhellmannif not the releases repo16:41
mesteryOK, I'll do the announcement by hand now, and in the future run Thanks dhellmann!16:41
dhellmannmestery : np, thanks16:41
bobhdhellmann: I'd like to request an exception for adding heat-translator to requirements.txt  It is needed for the tosca-parser/heat-translator integration into Tacker for Mitaka16:41
dhellmannbobh : is the work for that already done?16:41
bobhdhellmann: yes - just waiting on the requirements change to get Jenkins to pass16:42
dhellmannbobh : ok16:43
bobhdhellmann: Thanks - let me know if I can provide any more info16:44
dhellmannbobh : you should keep an eye on that requirements patch and recheck as needed to get it to land16:44
*** spzala has joined #openstack-release16:44
dhellmannbobh : otherwise, I think you've given enough justification so you're good to go16:44
bobhdhellmann: Great - thanks again16:45
openstackgerritMerged openstack/releases: Mitaka-3 milestone for Barbican deliverables
ttx#success mitaka-3 is done16:49
openstackstatusttx: Added success to Success page16:49
ttxdhellmann: announcement sent16:49
*** kzaitsev_mb has joined #openstack-release16:55
dhellmannttx: \o/16:56
betherlyshould have ironic-ui ready for release soon now.16:57
betherlywith regard release procedure do i just follow 'tagging a release' ?16:57
dhellmannbetherly : have a look at the README.rst file in the openstack/releases repo16:59
betherlydhellmann: thanks :)17:00
dhellmannbetherly : I need to update the creator's guide to point there for official projects.17:00
*** sdake_ has joined #openstack-release17:02
*** sdake has quit IRC17:03
*** amotoki has joined #openstack-release17:03
*** sdake_ is now known as sdake17:07
betherlydhellmann: apologies if this is a silly q...where does the hash need to come from for the ironic-ui project?17:11
dhellmannbetherly : you should use the SHA for the commit that you would apply the tag to if you ran "git tag" yourself17:12
dhellmannthe validation job will do some checks to make sure it's on the right branch, etc. and then when I run the release script it will use that SHA for the tag that I'll apply17:13
betherlyok awesome thanks dhellmann :)17:16
*** thinrichs has joined #openstack-release17:20
*** thinrichs has quit IRC17:24
dimsum_mtreinish : tiny nit, mind switching it around? oldest on top and newest at the bottom?
patchbotdimsum_: patch 288575 - releases - Add tempest releases to releases.o.o17:29
*** sridhar_ram has joined #openstack-release17:29
*** thinrichs has joined #openstack-release17:31
*** dtantsur is now known as dtantsur|afk17:32
*** thinrichs has quit IRC17:35
*** daemontool_ has joined #openstack-release17:37
dhellmannttx: tacker isn't ready for a mitaka release of their client, so I proposed they do an independent release this cycle. thoughts?17:39
*** kzaitsev_mb has quit IRC17:40
*** daemontool has quit IRC17:41
*** thinrichs has joined #openstack-release17:42
mtreinishdimsum_: sure, will do17:46
*** bobh has quit IRC17:47
*** thinrichs1 has joined #openstack-release18:02
*** thinrichs has quit IRC18:02
*** yarkot_ has joined #openstack-release18:13
dimsum_dhellmann : was expecting more traffic here today with the release deadline and what not :)18:18
betherlystill waiting on these patches to merge then youll have more traffic from me ;)18:18
dimsum_betherly :)18:19
betherlythe gate is pretty slow too :/18:19
*** yarkot_ has quit IRC18:21
*** amotoki has quit IRC18:28
dhellmanndimsum_ : me, too, but we got most everyone tagged yesterday or early today18:39
dhellmannSergeyLukjanov : do we need a sahara-tests release for mitaka?18:40
dhellmannSergeyLukjanov : it's marked as cycle-with-intermediary, so ideally we would have one today to leave space for a bug fixes for rc118:41
*** pcaruana has quit IRC18:41
dimsum_dhellmann : ./ looks good -
dhellmanndimsum_ : looking good18:42
*** mriedem has quit IRC18:47
*** spzala has quit IRC18:48
*** mriedem has joined #openstack-release18:48
*** spzala has joined #openstack-release18:48
*** doug-fis_ is now known as doug-fish18:50
openstackgerritDoug Hellmann proposed openstack/releases: Add tempest releases to releases.o.o
SergeyLukjanovdhellmann hi, honestly it's still not finally clear could we or not release it for mitaka, I'll try to resolve this question asap18:58
dhellmannSergeyLukjanov : ok18:58
openstackgerritJim Rollenhagen proposed openstack/releases: ironic-ui 0.0.1
jrollbetherly: dhellmann ^19:04
openstackgerritDoug Hellmann proposed openstack/releases: merge pbr deliverable files into independent directory
dhellmannjroll : looking19:04
jrolldhellmann: note that this isn't really functional yet, if we can avoid the release email that would be cool19:04
dhellmannjroll : the release email is automatic19:05
jrollyeah, figured :)19:05
jrollno worries19:05
dhellmannwe could put a different address there, I guess19:05
jrolldhellmann: last thing, betherly has a few patches waiting to merge that DO make it functional, at which point I'm giving my blanket approval for her to release a 1.0.0 and switch it over to openstack-announce (as I'll be leaving in about two hours until thursday)19:06
jrolloh not a bad idea19:06
* jroll does that19:06
openstackgerritJim Rollenhagen proposed openstack/releases: ironic-ui 0.0.1
jrollthere we are ^19:07
betherlythanks jroll dhellmann :)19:08
jrollbetherly: so just edit the email in that file, and add another release stanza (the last four lines) when you're ready19:08
dhellmannjroll, betherly : I'll wait for the check jobs to run there and then I'll process the file as it is now. Then betherly can submit the update later, when ready19:09
betherlygreat thanks!19:09
jrolldhellmann: perfect, ty19:10
*** thinrichs1 has quit IRC19:21
*** thinrichs has joined #openstack-release19:21
*** sdague has quit IRC19:32
*** kzaitsev_mb has joined #openstack-release19:32
*** sdake has quit IRC19:36
openstackgerritDavanum Srinivas (dims) proposed openstack/releases: oslo.cache 1.5.0 for Mitaka
*** sdake has joined #openstack-release19:37
openstackgerritMerged openstack/releases: Add tempest releases to releases.o.o
*** kzaitsev_mb has quit IRC19:47
*** kzaitsev_mb has joined #openstack-release19:47
*** thinrichs has quit IRC19:56
*** kzaitsev_mb has quit IRC20:15
dimsum_dhellmann : oslo.cache is ready. can you please take a peek and i can cut the release20:35
patchbotdimsum_: patch 288702 - releases - oslo.cache 1.5.0 for Mitaka20:35
dimsum_dhellmann : requirements review is ready too
patchbotdimsum_: patch 288703 - requirements - Need a new minimum for oslo.cache in Mitaka20:35
dhellmanndimsum_ : +220:35
dhellmanndimsum_ : please let me know when you're done so I can handle the ironic-ui release20:36
dimsum_ack, merging the release review now20:36
*** sdake has quit IRC20:39
openstackgerritMerged openstack/releases: oslo.cache 1.5.0 for Mitaka
*** thinrichs has joined #openstack-release20:43
dimsum_dhellmann : oslo.cache 1.5.0 is on pypi.20:44
dimsum_dhellmann : look ok?20:45
patchbotdimsum_: patch 288703 - requirements - Need a new minimum for oslo.cache in Mitaka20:45
*** thinrichs has quit IRC21:04
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: dump a release tracking dashboard
*** cgalan has joined #openstack-release21:05
dhellmanndimsum_ : +2a on the requirements update21:05
*** sdake has joined #openstack-release21:05
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: dump a release tracking dashboard
dhellmanndimsum_ : is the other view21:10
dimsum_dhellmann : would it be useful to publish it as html somewhere? (
*** thinrichs has joined #openstack-release21:20
*** thinrichs has left #openstack-release21:22
*** johnma has left #openstack-release21:46
dhellmanndimsum_ : this is meant for us to edit as we do the release21:51
dhellmannI can't decide whether the spreadsheet or the etherpad is going to be better for that21:51
dimsum_dhellmann : the spread sheet will be better i think21:52
dimsum_we can try one and switch over next time :)21:53
betherlydhellmann: the patches are all now in workflow21:58
*** pcaruana has joined #openstack-release21:58
betherlythe gate is pretty slow - looks like about an hr to merge and then i have another that can only get workflowed to pass tests once they have merged21:58
betherlywill you still be around by then to help me merge the release?21:59
*** spzala has quit IRC22:01
dimsum_betherly : one of us will be around.22:02
betherlyok awesome thanks!!22:02
*** gordc has quit IRC22:17
openstackgerritMatt Riedemann proposed openstack/releases: liberty: release nova 12.0.2
*** devananda has quit IRC22:45
*** mriedem has quit IRC22:46
*** devananda has joined #openstack-release22:58
openstackgerritMerged openstack/releases: ironic-ui 0.0.1
*** cgalan has quit IRC23:07
betherlyugh merge conflict23:08
dhellmannbetherly : if I'm not around later, I'll check in early tomorrow23:08
*** bauwser is now known as bauzas23:09
betherlydhellmann: sorry about this :(23:09
betherly11:09pm and still trying to get these things merged. annoying friday evening lol23:09
dhellmannbetherly : no worries, keep working at it23:09
dhellmannoh, wow, isn't there someone on your team in a better tz?23:10
betherlyits just me and peter developing the plugin and im the main developer on it. hes offline now23:11
betherlyq re merge conflicts though...23:11
betherlynode details needs to go next but seems to be caught in merge conflict23:11
betherlyit hasnt been -1'd yet though. do you think it will go through ok ?23:11
betherlythen i will rebase the 'changed naming of ironic api files' one and resubmit that but i need node details to go through ok first23:11
dhellmannif there's a merge conflict, it probably won't go through23:18
dhellmannI would set up a branch with all of those patches in the order they should merge so you have the conflicts worked out when you resubmit them23:18
dhellmannbetherly : ^23:19
betherlyive done a rebase to master23:19
dhellmannah, I see 2 of them are in the same branch already23:20
betherlyi think it got confused early on with the other commit going through23:20
dhellmannyeah, so that should fix it23:20
dhellmannyeah, that has happened several times this week with patches that didn't seem confusing to me, but shrug23:20
dhellmannI guess the git diff couldn't safely determine how to do the merge23:20
dhellmannbetherly : I'm going to sign off for dinner. I'll check in tomorrow morning to see how things look. If you have questions, leave them here and I'll catch up when I come back online23:21
betherlyok awesome thanks dhellmann23:22
*** sdake has quit IRC23:25
*** sridhar_ram has quit IRC23:43
openstackgerritAdam Gandelman proposed openstack/releases: Astara mitaka-3 milestone release

Generated by 2.14.0 by Marius Gedminas - find it at!