| *** mriedem has joined #openstack-release | 00:01 | |
| *** sdake has quit IRC | 00:01 | |
| *** dims has joined #openstack-release | 00:08 | |
| *** sdake_ has quit IRC | 00:08 | |
| *** sdake has joined #openstack-release | 00:11 | |
| *** armax has joined #openstack-release | 00:14 | |
| *** sdague has joined #openstack-release | 00:22 | |
| *** openstack has joined #openstack-release | 00:24 | |
| *** sdague has quit IRC | 00:26 | |
| *** sheeprine has quit IRC | 00:30 | |
| *** sheeprine has joined #openstack-release | 00:34 | |
| *** dims has joined #openstack-release | 00:45 | |
| *** david-lyle has joined #openstack-release | 01:04 | |
| *** dims has quit IRC | 01:07 | |
| *** dims has joined #openstack-release | 01:12 | |
| *** dims has quit IRC | 01:29 | |
| *** dims has joined #openstack-release | 01:29 | |
| *** mriedem has quit IRC | 01:42 | |
| *** dims has quit IRC | 01:52 | |
| *** dims has joined #openstack-release | 01:56 | |
| *** dims has quit IRC | 02:03 | |
| *** dims has joined #openstack-release | 02:05 | |
| *** amrith is now known as _amrith_ | 02:24 | |
| *** sridhar_ram has joined #openstack-release | 02:31 | |
| *** sridhar_ram has quit IRC | 02:41 | |
| *** dims has quit IRC | 03:37 | |
| *** cody-somerville has quit IRC | 03:46 | |
| *** cody-somerville has joined #openstack-release | 04:01 | |
| *** cody-somerville has quit IRC | 04:01 | |
| *** cody-somerville has joined #openstack-release | 04:01 | |
| *** sdake has quit IRC | 04:50 | |
| openstackgerrit | Tony Breeds proposed openstack-infra/release-tools: add convenience script for finding unreleased stable branch changes https://review.openstack.org/270273 | 05:03 |
|---|---|---|
| *** sridhar_ram has joined #openstack-release | 05:31 | |
| openstackgerrit | Merged openstack-infra/release-tools: Actually use the URL specific in --project-list https://review.openstack.org/292657 | 05:39 |
| *** sridhar_ram has quit IRC | 05:42 | |
| *** david-lyle has quit IRC | 05:45 | |
| *** david-lyle has joined #openstack-release | 05:45 | |
| skraynev | ttx: hi. I can not find a tag stable-mitaka-backport potential. will it be added after creating stable branch or you can do it before? I just wanted to move out some bugs from rc1 with marking them with this tag. Also I am wondering about creating mitaka-rc1, Do we need do some patch to releases repo for it? | 06:17 |
| *** ihrachys has joined #openstack-release | 07:04 | |
| openstackgerrit | Ihar Hrachyshka proposed openstack/releases: Neutron Mitaka RC1 deliverables https://review.openstack.org/292445 | 07:05 |
| *** ihrachys has quit IRC | 07:06 | |
| *** AJaeger has joined #openstack-release | 07:21 | |
| AJaeger | release team, https://jenkins.openstack.org/job/propose-requirements-updates/853/consoleFull reports an error with with freezer-web-ui with incompatible requirements... | 07:22 |
| ttx | dhellmann: yes | 07:38 |
| ttx | skraynev: Launchpad tags can be freely added | 07:39 |
| ttx | i.e. you can put anything you want and ignore autocompletion | 07:40 |
| ttx | but if you want it to appear in autocompletion you should add it to teh heat official tags: | 07:40 |
| ttx | https://bugs.launchpad.net/heat/+manage-official-tags | 07:40 |
| ttx | Heat drivers group in Launchpad should have the rights to update those | 07:41 |
| *** amotoki has joined #openstack-release | 07:46 | |
| *** ihrachys has joined #openstack-release | 08:04 | |
| skraynev | ttx: got it. thank you for the link. | 08:07 |
| openstackgerrit | Ihar Hrachyshka proposed openstack/releases: Neutron Mitaka RC1 deliverables https://review.openstack.org/292445 | 08:08 |
| skraynev | ttx: what about rc1 related question? do we need propose patch to releases repo? | 08:08 |
| openstackgerrit | Ihar Hrachyshka proposed openstack/releases: Neutron Mitaka RC1 deliverables https://review.openstack.org/292445 | 08:09 |
| ttx | skraynev: you mean the Launchpad milestone ? | 08:09 |
| ttx | you can create it yourself too | 08:09 |
| ttx | If you mean the *git* tag, then yes it requires a change to openstack/releases and we'll handle it | 08:10 |
| ttx | but you can create the "mitaka-rc1" milestone on launchpad.net/heat alright | 08:11 |
| skraynev | ttx: I meant the second, i.e. "git" tag. Is the last date for this is tomorrow? So if I propose patch today's evening or tomorrow's morning, it's ok ? | 08:12 |
| ttx | skraynev: the target date is this week, yes. But if it's not ready and you still have release-critical bugs, you could delay | 08:15 |
| ttx | There is no point in tagging the RC1 if you know it's broken | 08:15 |
| ttx | and request a RC2 Monday | 08:15 |
| ttx | but if you covered all the release-critical stuf, yes, tagging tomorrow is fine | 08:16 |
| skraynev | ttx: I thought, that we may propose rc1 on this week and if it will be necessary do rc2 on the next or it's wrong approach? | 08:21 |
| ttx | sure that is fine | 08:21 |
| ttx | everything is in the "if it will be necessary" | 08:22 |
| ttx | if you already know it will be necessary to do RC2 next week there is little point in doing a RC1 this week | 08:22 |
| ttx | But if you think the RC1 is looking good enough for now, then yes tag this week! | 08:22 |
| ttx | And tag RC2 next week if necessary | 08:23 |
| ttx | hoping I make sense | 08:23 |
| ttx | skraynev: ^ | 08:25 |
| skraynev | ttx: more than need ;) thank you very much for detailed explanation. it is that I wanted to hear | 08:34 |
| *** ig0r_ has quit IRC | 08:39 | |
| *** kzaitsev_mb has joined #openstack-release | 09:24 | |
| *** dtantsur|afk is now known as dtantsur | 09:42 | |
| *** sdague has joined #openstack-release | 09:43 | |
| *** amotoki has quit IRC | 09:43 | |
| *** dims has joined #openstack-release | 09:51 | |
| *** openstackgerrit has quit IRC | 09:53 | |
| *** openstackgerrit_ is now known as openstackgerrit | 09:53 | |
| *** openstackgerrit has quit IRC | 09:53 | |
| *** openstackgerrit_ has joined #openstack-release | 09:53 | |
| *** openstackgerrit_ is now known as openstackgerrit | 09:54 | |
| *** openstackgerrit_ has joined #openstack-release | 09:55 | |
| *** openstackgerrit has quit IRC | 09:55 | |
| *** openstackgerrit has joined #openstack-release | 09:56 | |
| *** sdague has quit IRC | 10:00 | |
| *** sdague has joined #openstack-release | 10:03 | |
| *** sdague has quit IRC | 10:11 | |
| *** sdague has joined #openstack-release | 10:11 | |
| *** daemontool has joined #openstack-release | 10:28 | |
| dims | ttx : +10000 to "In an ideal world you'd either grow the resources / bandwidth" | 10:36 |
| *** dims has quit IRC | 10:53 | |
| *** dims has joined #openstack-release | 10:59 | |
| *** kzaitsev_mb has quit IRC | 10:59 | |
| *** _amrith_ is now known as amrith | 11:16 | |
| *** openstackgerrit has quit IRC | 11:18 | |
| *** openstackgerrit has joined #openstack-release | 11:18 | |
| *** dtantsur is now known as dtantsur|brb | 11:34 | |
| *** ihrachys has quit IRC | 11:42 | |
| *** gordc has joined #openstack-release | 11:44 | |
| *** kzaitsev_mb has joined #openstack-release | 11:44 | |
| sdague | I want to live in theory, everything works in theory :) | 11:50 |
| dims | LOL sdague | 11:51 |
| *** dtantsur|brb is now known as dtantsur | 12:01 | |
| *** kzaitsev_mb has quit IRC | 12:24 | |
| *** kzaitsev_mb has joined #openstack-release | 12:25 | |
| *** pcaruana has quit IRC | 12:28 | |
| ttx | Theoryland | 12:44 |
| dims | Thierryland? :) | 12:46 |
| ttx | yep sounds a lot like that | 12:46 |
| ttx | The land where devs have no idea what to do next and look up wishlist bugs list for inspiration | 12:47 |
| dims | :) | 12:47 |
| ttx | dhellmann: we have the ACLs merged, so processing RC1s is a go | 12:54 |
| ttx | happy to help in the coming hours | 12:54 |
| dhellmann | ttx: sounds good. I'm just getting started, do you want to do the neutron tag? they were a bit impatient to have their branch created so they could sprint on something. | 12:57 |
| ttx | dhellmann: anything special I should watch for ? Just planned on running the tag (from_yaml) and then create stable branch | 12:59 |
| ttx | ./release_from_yaml.sh and ./make_stable_branch.sh | 13:00 |
| dhellmann | ttx: that should do it | 13:00 |
| ttx | alright let's try | 13:00 |
| dhellmann | it'll be interesting to see how make_stable_branch.sh works for you | 13:00 |
| dhellmann | I'm not sure anyone else has run that yet | 13:00 |
| dhellmann | since we added the reno patch logic | 13:00 |
| ttx | hmm, we might want armax or mestery to sign off on Ihar's SHAs | 13:02 |
| ttx | dhellmann: or are you comfortable with those ? | 13:02 |
| ttx | https://review.openstack.org/#/c/292445/ | 13:02 |
| patchbot | ttx: patch 292445 - releases - Neutron Mitaka RC1 deliverables | 13:02 |
| ttx | doing glance in the mean time | 13:02 |
| dhellmann | oh, I hadn't noticed ihar had updated the patch, yeah, we should probably get mestery to sign off | 13:03 |
| ttx | dhellmann: for make_stable_branches, I should run something like ./make_stable_branches.sh mitaka openstack/glance 12.0.0.0rc1 ? | 13:05 |
| dhellmann | ttx: yes, that's right | 13:05 |
| dhellmann | well, "branch" not "branches" | 13:05 |
| ttx | right | 13:05 |
| ttx | ok, let's see how it goes | 13:05 |
| dhellmann | and you have to run it for all the repos, so neutron will need 4 calls -- we should write a make-branches-from-yaml script | 13:06 |
| ttx | dhellmann: haven't reviewed the reno cache stuff yet, wanted to give it review justice | 13:07 |
| *** bdemers has joined #openstack-release | 13:11 | |
| dhellmann | ttx: sure. it needs more tests, I'll try to get back to that later this week | 13:12 |
| *** kro_sinus_hell is now known as krot_sinus_purga | 13:15 | |
| *** krot_sinus_purga is now known as kro_sniffles | 13:15 | |
| *** smcginnis_away is now known as smcginnis | 13:15 | |
| openstackgerrit | Merged openstack/releases: Tag Glance Mitaka RC1 https://review.openstack.org/293137 | 13:15 |
| openstackgerrit | Merged openstack-infra/release-tools: Add update_reviews tool https://review.openstack.org/290853 | 13:16 |
| ttx | dhellmann: worked alright. Maybe an extra space in https://review.openstack.org/#/c/293415/1/releasenotes/source/index.rst | 13:20 |
| patchbot | ttx: patch 293415 - glance - Update reno for stable/mitaka | 13:20 |
| ttx | also maybe would make sense to place mitaka first in that file | 13:21 |
| *** ig0r_ has joined #openstack-release | 13:24 | |
| ttx | additionally I'll manually send a "RC1, master now open for newton" canned email for the things I process today | 13:24 |
| dhellmann | yeah, every project has different whitespace there, so that's going to need to be made much smarter | 13:24 |
| ttx | does the order matter ? | 13:25 |
| dhellmann | not really | 13:25 |
| ttx | ok good, also I epect the extra space to not hurt, just look ugly | 13:25 |
| ttx | expect | 13:25 |
| dhellmann | the extra space will actually cause it to fail to parse, so we'll have to fix those | 13:26 |
| ttx | ah, will manually fix | 13:26 |
| dhellmann | yeah, for the libraries I asked the owning project liaisons to fix them but we have a lot fewer of these so we should be able to fix them ourselves to make them land more quickly | 13:27 |
| *** mriedem has joined #openstack-release | 13:28 | |
| *** sdake has joined #openstack-release | 13:33 | |
| dhellmann | ttx: https://review.openstack.org/#/c/293425 via stevemar in -infra | 13:34 |
| dhellmann | it seems to me like we have a hole in the test jobs for that repo if we can land a constraint that doesn't match the requirement spec | 13:34 |
| ttx | ew | 13:34 |
| dhellmann | like we're not actually trying to install everything, and just relying on the dsvm job to do that | 13:34 |
| ttx | goo thing nobody uses that | 13:34 |
| ttx | +d | 13:34 |
| dhellmann | apparently it broke something, discussion in -infra | 13:35 |
| ttx | looking | 13:36 |
| *** doug-fish has quit IRC | 13:39 | |
| *** doug-fish has joined #openstack-release | 13:42 | |
| dhellmann | ttx: I'm going to self-approve the reno fix for deleted notes so we can release that today | 13:45 |
| *** doug-fish has quit IRC | 13:46 | |
| openstackgerrit | Merged openstack/reno: handle deleted notes properly https://review.openstack.org/293078 | 13:50 |
| openstackgerrit | Matt Riedemann proposed openstack-infra/release-tools: add convenience script for finding unreleased stable branch changes https://review.openstack.org/270273 | 13:54 |
| *** mriedem is now known as mriedem_meeting | 13:54 | |
| *** armax has joined #openstack-release | 13:54 | |
| armax | dhellmann: ping | 13:58 |
| dhellmann | armax : pong | 13:58 |
| dhellmann | armax : I see you've +1ed the rc1 tag patch, we were waiting for that before processing it | 13:59 |
| armax | dhellmann: re https://review.openstack.org/#/c/292445/ | 13:59 |
| patchbot | armax: patch 292445 - releases - Neutron Mitaka RC1 deliverables | 13:59 |
| armax | dhellmann: yes | 13:59 |
| armax | dhellmann: we still have one or two fixes we’d like to land | 14:00 |
| dhellmann | armax : do you want to hold rc1, or are you planning an rc2? | 14:00 |
| *** doug-fish has joined #openstack-release | 14:00 | |
| armax | dhellmann: that’s the part I am unsure of, whether we have a little extra time to pull the trigger on rc1 | 14:00 |
| armax | dhellmann: or we can simply go ahead with this one, but plan for an rc2 | 14:00 |
| *** doug-fish has quit IRC | 14:01 | |
| *** doug-fish has joined #openstack-release | 14:01 | |
| dhellmann | armax : you have this week, so if you have the fixes in the queue you could wait | 14:01 |
| armax | wait and bump the hash for rc1 you mean? | 14:02 |
| dhellmann | yes | 14:02 |
| ttx | armax: better wait totag rather than tag already knowing you'll do an rc2 the next day | 14:02 |
| armax | ttx: fair point | 14:02 |
| armax | I was not sure if you guys rather tagged mid week than later in the week | 14:02 |
| ttx | it's supposed to be a release candiadte. Even if it's extremely likely that you'll do another RC, it should be < 100% | 14:03 |
| armax | but ideally I’d open master if I can | 14:03 |
| dhellmann | ttx: is it better to get a tag this week, or wait until next week? | 14:03 |
| ttx | dhellmann: it's a bit of a trade-off. You don't want to communicate that RCs are useless | 14:03 |
| dhellmann | true | 14:04 |
| ttx | since you kinda want people to test and package them | 14:04 |
| ttx | but on the other hand you want a RC1 asap | 14:04 |
| dhellmann | ok, so the deadline for an rc isn't as firm as I had been treating it | 14:04 |
| dhellmann | right | 14:04 |
| ttx | yes, this week is a target week | 14:04 |
| dhellmann | "target" not "deadline" | 14:04 |
| ttx | if some projects miss it and are not ready, it's not that bad | 14:04 |
| dhellmann | ok, that makes sense | 14:04 |
| ttx | different from the mitaka-3 deadline where we define a point in time | 14:04 |
| dhellmann | right | 14:04 |
| ttx | here we define readiness | 14:04 |
| ttx | but it's still good to be firm and for people missing the target date to be seen as a problem, otherwise you just give procrastinators an extra week | 14:05 |
| ttx | so it's a bit of a balancing act | 14:05 |
| * dhellmann feels wobbly | 14:06 | |
| dhellmann | ok, armax please -1 the proposed rc1 if you want to hold off. I'm going to step away for a bit but I'll check back in shortly. | 14:06 |
| *** sigmavirus24_awa is now known as sigmavirus24 | 14:06 | |
| armax | ttx, dhellmann: this is a bit of a moving target and knowing when to shoot it down it’s the fine balance we need to strike | 14:06 |
| ttx | dhellmann: in previous cycles we had extra legroom because we could cut the branch before th RC1, but we decided that was extra complexity | 14:06 |
| ttx | and it can be counterproductive, since "opening newton" is the carrot we have to encourage people to finish rc1 | 14:07 |
| dhellmann | right | 14:07 |
| ttx | so I'm fine tagging RC1 as soon as there is a remote possibility that RC1 could be the end release. Because after all, we'll promote the RC1 if that is the only thing we have on release day | 14:08 |
| ttx | remote can be 1% | 14:08 |
| ttx | but as long as it's 0.00% I think we should wait | 14:08 |
| ttx | otherwise we are wasting everyone's time | 14:08 |
| armax | dhellmann, ttx as far as I am aware, our RC1 is sound, the patch we want to land fixes a performance issue | 14:09 |
| ttx | armax: so you could tag RC1 and include that patch in a future RC if one ends up being desirable | 14:09 |
| armax | something we’ll have to backport even if it didn’t make it | 14:09 |
| armax | ttx: right, I was operating under that assumption | 14:09 |
| ttx | i.e. not consider that patch a release critical issue, but include it together with the next release-critical issue you find | 14:10 |
| ttx | all depends on what you call release-critical obviously | 14:10 |
| armax | ttx: that we could give ourselves the chance to land that in an RC2 if some other catastrophic issue shows up | 14:10 |
| ttx | which will happen in 99% of the cases | 14:10 |
| ttx | based on history | 14:10 |
| armax | yup | 14:10 |
| ttx | armax: so yeah, you decide | 14:11 |
| ttx | depends a lot on how usable the thing is without the patch | 14:11 |
| armax | ttx: ok, I give myself the end of today | 14:11 |
| armax | what’s in is in, what’s out is out | 14:11 |
| * ttx holds on | 14:11 | |
| ttx | dhellmann: I'll send the Glance RC1 manual announce then, might trigger others | 14:12 |
| armax | dhellmann, ttx thanks for the clarifying comments | 14:13 |
| ttx | #success Glance is the first project to issue a RC1 ! | 14:18 |
| openstackstatus | ttx: Added success to Success page | 14:18 |
| dims | go glance! | 14:19 |
| *** sdake has quit IRC | 14:27 | |
| openstackgerrit | Sergey Kraynev proposed openstack/releases: Tag Heat RC1 Mitaka https://review.openstack.org/293473 | 14:42 |
| *** mriedem_meeting is now known as mriedem | 14:56 | |
| ttx | skraynev: alright, on its way ! | 15:07 |
| skraynev | ttx: we decided to move 5 bugs to rc2. | 15:08 |
| dhellmann | ttx: when you're done, I'll do the tacker liberty release | 15:08 |
| ttx | dhellmann: ack | 15:08 |
| openstackgerrit | Merged openstack/releases: Tag Heat RC1 Mitaka https://review.openstack.org/293473 | 15:12 |
| *** david-lyle has quit IRC | 15:15 | |
| *** david-lyle has joined #openstack-release | 15:15 | |
| ttx | dhellmann: ew. https://review.openstack.org/#/c/293496/1/releasenotes/source/index.rst :) | 15:16 |
| patchbot | ttx: patch 293496 - heat - Update reno for stable/mitaka | 15:16 |
| ttx | dhellmann: all done for heat RC1 | 15:17 |
| dhellmann | ttx: yeah, my bash patch logic is pretty dumb. :-/ | 15:17 |
| ttx | dhellmann: not blaming or anything, just another case to handle | 15:17 |
| dhellmann | yeah, that's all going to have to be rewritten to be much smarter | 15:17 |
| ttx | looks like we have a wide variety of those | 15:18 |
| * dhellmann starts the tacker 0.2.0 release | 15:18 | |
| openstackgerrit | Merged openstack/releases: Release tacker 0.2.0 for liberty https://review.openstack.org/292621 | 15:23 |
| openstackgerrit | Doug Hellmann proposed openstack/releases: reno 1.6.1 https://review.openstack.org/293502 | 15:24 |
| *** sdake has joined #openstack-release | 15:25 | |
| * dhellmann steps away for a bit | 15:28 | |
| *** david-lyle_ has joined #openstack-release | 15:34 | |
| *** david-lyle has quit IRC | 15:34 | |
| *** jroll has quit IRC | 15:41 | |
| *** jroll has joined #openstack-release | 15:41 | |
| *** jroll has quit IRC | 15:41 | |
| *** jroll has joined #openstack-release | 15:41 | |
| *** sridhar_ram has joined #openstack-release | 16:03 | |
| * dhellmann returns | 16:11 | |
| amrith | dhellmann, just replied to your question in https://review.openstack.org/#/c/292650/1. Sorry I didn't see it till now. | 16:15 |
| patchbot | amrith: patch 292650 - releases - Please tag python-troveclient v2.2.0 | 16:15 |
| openstackgerrit | Armando Migliaccio proposed openstack/releases: Neutron Mitaka RC1 deliverables https://review.openstack.org/292445 | 16:15 |
| *** david-lyle_ is now known as david-lyle | 16:20 | |
| dhellmann | amrith : I see changes to existing stuff in http://git.openstack.org/cgit/openstack/python-troveclient/commit/?id=457360c69f651aea92769c9e543492d770b84595 | 16:22 |
| amrith | dhellmann, the meat of the change is in troveclient/v1/instances.py, modules.py and shell.py. They add new capabilities. There are new tests proposed, a new utility function proposed in utils.py, and a new parameter with a default of None to an exception that existed below. | 16:25 |
| amrith | yes, some existing files are being modified | 16:25 |
| dhellmann | amrith : I'm sorry. The freeze is an important part of stabilizing things, and we've told other projects with a similar situation "no" as well. Your best course for now is to finish the mitaka work on the service, prepare a release candidate, and put the client changes off until newton opens. | 16:26 |
| amrith | but the API's (adding modules to create with a None, for example) are not compatibility issues. I think. | 16:26 |
| amrith | dhellmann, this was something we'd specifically requested as part of the FFE earlier. why does the client change have to wait for newton, can't we request a new client once rc1 is frozen? | 16:27 |
| amrith | oh, sorry | 16:27 |
| amrith | you said newton opens | 16:27 |
| dhellmann | we treat all libraries the same way during this period: critical issues only for releases | 16:27 |
| amrith | OK, I think we can live with that. Not ideal, but I don't think that's as bad as it sounded when I first read. | 16:27 |
| amrith | understood. I'll remember for next time that FFE's don't extend to the client side. That freeze is a hard freeze. | 16:28 |
| amrith | thanks, I think we can make taht work. | 16:28 |
| dhellmann | yeah, you're not the only project in this state so we'll be doing more next cycle to communicate about the freeze | 16:28 |
| dhellmann | thanks | 16:28 |
| amrith | ok to keep the review around and just request it again once newton is open? | 16:28 |
| amrith | I'll -2 it for now ... | 16:28 |
| amrith | well, I can't -2 it, I'll wf -1 it. | 16:29 |
| dhellmann | amrith : you'll need to update it to move the file to the newton directory, since the new release will be part of newton not mitaka | 16:29 |
| dhellmann | well, not move the file, but make a new file with this request in it | 16:29 |
| amrith | can I request upper-constraints be increased for mitaka at a later time? | 16:29 |
| amrith | right now, upper-constraints for mitaka says 2.1.1 | 16:30 |
| dhellmann | amrith : no, that's going to be frozen, too, at least until we sort out backwards-compatibility testing | 16:30 |
| amrith | that means that if we have even a bugfix, then we can't release it for mitaka. | 16:30 |
| dhellmann | well, bug fixes will be allowed, but not feature releases | 16:30 |
| dhellmann | I thought you were asking specifically about allowing this new feature into mitaka | 16:30 |
| amrith | the feature is partially in mitaka | 16:31 |
| amrith | (the server side) | 16:31 |
| amrith | you could get to it on the REST API | 16:31 |
| amrith | all that we're asking here is for the client side of that change | 16:31 |
| dhellmann | that's fine | 16:31 |
| dhellmann | no, you're asking me to break the rules all of the other projects are following | 16:31 |
| amrith | because when we FFE'ed this, we assumed that the FFE extended to the client. | 16:31 |
| dhellmann | well, I thought I made clear that client libraries were frozen | 16:32 |
| amrith | sorry, no. I agree, I don't want to talk about this FFE'ed new feature in Mitaka client. | 16:32 |
| amrith | that, we agree about. | 16:32 |
| amrith | my question is about a bug fix in Mitaka. | 16:32 |
| amrith | suppose we need a 2.1.2 | 16:32 |
| amrith | what then? | 16:32 |
| amrith | that, I hope would be OK | 16:32 |
| amrith | not this FFE'ed feature. I agree, 2.2.0 is a newton thing. | 16:32 |
| dhellmann | after the stable branch is created for the requirements repo, we will allow updates for bug-fix releases from mitaka branches of libraries to go into the constraints file. we won't raise the constraints to include new features until we have better backwards-compatibility testing in place. we won't be applying automatically-generated updates to the constraints file. | 16:33 |
| amrith | OK, all good then. Thanks. I'll -1 the changes and resubmit once newton opens. | 16:34 |
| dhellmann | ok. we should go ahead and create your stable/mitaka branch for the client from the latest release, then | 16:34 |
| dhellmann | I have that recorded as 2.1.1, is that right? | 16:34 |
| dhellmann | amrith : ^^ | 16:37 |
| amrith | that is correct dhellmann | 16:37 |
| amrith | 2.1.1 is python-troveclient stable/mitaka. | 16:37 |
| dhellmann | amrith : ok, I'll go ahead and create your branch now | 16:37 |
| amrith | I sent you the version for trove-dashboard as well. | 16:38 |
| amrith | I will be merging final changes for openstack/trove today and should be able to tag the server side as well. | 16:38 |
| dhellmann | amrith : https://review.openstack.org/293552 | 16:38 |
| amrith | +2'ed | 16:39 |
| ttx | dhellmann: looks like I can process neutron now | 16:40 |
| ttx | dhellmann: if you don't use the baton | 16:40 |
| amrith | dhellmann, trove-dashboard is 6.0.0.0b3 | 16:41 |
| amrith | thx | 16:41 |
| ttx | https://review.openstack.org/#/c/292445/ | 16:41 |
| patchbot | ttx: patch 292445 - releases - Neutron Mitaka RC1 deliverables | 16:41 |
| dhellmann | amrith : we will cut branches from the rc1 tags for projects following the milestone system, so you can submit the request for trove-dashboard and we'll create the branch when we process it | 16:41 |
| dhellmann | ttx: I'm just about to do a reno release, give me a couple of minutes? | 16:42 |
| *** kzaitsev_mb has quit IRC | 16:42 | |
| ttx | dhellmann: standing by | 16:43 |
| openstackgerrit | Merged openstack/releases: reno 1.6.1 https://review.openstack.org/293502 | 16:43 |
| * dhellmann passes the baton to ttx | 16:44 | |
| amrith | dhellmann, thanks. If I understand that correctly, trove and trove-dashboard, submit change in openstack/releases/ (deliverables/trove.yaml and deliverables/trove-dashboard.yaml) with ...rc1 and an appropriate hash. yes? | 16:44 |
| * ttx catches | 16:44 | |
| dhellmann | amrith : yes | 16:44 |
| amrith | thx, wilco | 16:44 |
| sridhar_ram | dhellmann: thanks for merging tacker 0.2.0. The next item in the tacker series is tackerclient 0.2.1 https://review.openstack.org/#/c/291879/ - please review when you get a chance. | 16:46 |
| patchbot | sridhar_ram: patch 291879 - releases - Release tackerclient 0.2.1 for liberty | 16:46 |
| openstackgerrit | John Garbutt proposed openstack/releases: Tag Nova Mitaka RC1 https://review.openstack.org/293562 | 16:50 |
| openstackgerrit | Merged openstack/releases: Neutron Mitaka RC1 deliverables https://review.openstack.org/292445 | 16:51 |
| johnthetubaguy | dhellmann: ttx: can I quickly check about how master opens for newton, now setup.cfg doesn't have a version number in it, and the last tag will still be mitaka? | 16:54 |
| dhellmann | johnthetubaguy : sure, let me explain | 16:54 |
| dhellmann | johnthetubaguy : we will create the stable/mitaka branch from the rc1 tag | 16:55 |
| dhellmann | after that, patches to master need to be backported | 16:55 |
| johnthetubaguy | yep, that bits fine, thats normal | 16:55 |
| *** kzaitsev_mb has joined #openstack-release | 16:55 | |
| dhellmann | we'll tag something on stable/mitaka as your final (either rc1, rc2, etc.) | 16:55 |
| dhellmann | the version # comes from the tag, via pbr | 16:55 |
| johnthetubaguy | I just just wondering how we know masters is generating 14.x versions | 16:55 |
| dhellmann | the work we did at the beginning of this cycle ensures that will all work properly | 16:56 |
| johnthetubaguy | I guess it doesn't till we do the first tag? | 16:56 |
| dhellmann | master and stable will have the same versions for some small period, but we decided that doesn't matter because CD folks should only one branch or the other | 16:56 |
| dhellmann | and it will be addressed more directly when we tag b1 for newton on master | 16:57 |
| johnthetubaguy | yeah, thats true, it doesn't matter too much | 16:57 |
| johnthetubaguy | OK, thanks, I am clear whats happening now | 16:57 |
| dhellmann | yep, thanks for checking in | 16:58 |
| dhellmann | ttx, dims, sdague : https://review.openstack.org/293570 | 16:58 |
| *** sigmavirus24 is now known as sigmavirus24_awa | 17:02 | |
| *** kzaitsev_mb has quit IRC | 17:14 | |
| dims | dhellmann : +1 | 17:16 |
| ttx | so the two things I do in addition to running the scripts is to check the tarball link on the releases page once it's built, and fixing the generated reno/mitaka review | 17:18 |
| ttx | and send the manual canned announcement replacing $project. That makes 3 | 17:19 |
| *** dtantsur is now known as dtantsur|afk | 17:20 | |
| *** sridhar_ram1 has joined #openstack-release | 17:21 | |
| *** sridhar_ram has quit IRC | 17:22 | |
| ttx | we should probably approve the stable/mitaka .gitreview bumps ourselves since they end up in a release-controlled branch | 17:34 |
| ttx | https://review.openstack.org/#/q/status:open+topic:create-mitaka | 17:35 |
| ttx | arh, nova | 17:35 |
| ttx | dhellmann: shall I do nova or you'll handle it ? | 17:36 |
| dhellmann | ttx: go for it, I'm on a call | 17:36 |
| ttx | ack | 17:36 |
| dims | ttx : go to those review and do a +2A? i can help | 17:37 |
| *** armax has quit IRC | 17:37 | |
| ttx | dims: thx | 17:37 |
| *** johnthetubaguy_ has joined #openstack-release | 17:39 | |
| *** johnthetubaguy has quit IRC | 17:41 | |
| *** johnthetubaguy_ is now known as johnthetubaguy | 17:41 | |
| dims | ttx : 3 reviews i did not see a +2 button https://review.openstack.org/#/c/291338/ https://review.openstack.org/#/c/291799/ https://review.openstack.org/#/c/291328/ | 17:42 |
| patchbot | dims: patch 291338 - python-muranoclient (stable/mitaka) - Update .gitreview for stable/mitaka | 17:42 |
| patchbot | dims: patch 291799 - python-brick-cinderclient-ext (stable/mitaka) - Update .gitreview for stable/mitaka | 17:42 |
| patchbot | dims: patch 291328 - django_openstack_auth (stable/mitaka) - Update .gitreview for stable/mitaka | 17:42 |
| dims | sorry 2 reviews | 17:43 |
| dims | openstack/python-brick-cinderclient-ext and openstack/python-muranoclient | 17:43 |
| ttx | oh, that would be non-releae-controlled ones | 17:44 |
| dims | cool | 17:44 |
| ttx | dims: we only control the milestones/managed stuff | 17:44 |
| ttx | so not a big deal if we don't push the others | 17:44 |
| *** kzaitsev_ip_ has joined #openstack-release | 17:45 | |
| *** sdague has quit IRC | 17:46 | |
| johnsom | ttx Has the clock run out on: https://review.openstack.org/#/c/290735/ | 17:46 |
| patchbot | johnsom: patch 290735 - governance - Update lbaas dashboard repo to be similar to octav... | 17:46 |
| dims | ttx done | 17:47 |
| ttx | johnsom: close enough :) | 17:48 |
| johnsom | Excellent. Thanks | 17:49 |
| ttx | johnsom: approved | 17:49 |
| *** kzaitsev_ip_ has quit IRC | 17:49 | |
| *** sdague has joined #openstack-release | 17:52 | |
| *** kzaitsev_ip_ has joined #openstack-release | 17:54 | |
| *** kzaitsev_ip_ has quit IRC | 17:57 | |
| openstackgerrit | Sridhar Ramaswamy proposed openstack/releases: Release tacker 0.2.1 for liberty https://review.openstack.org/293623 | 17:58 |
| *** sigmavirus24_awa is now known as sigmavirus24 | 18:07 | |
| *** kzaitsev_mb has joined #openstack-release | 18:10 | |
| ttx | dammit cloning nova takes forever with my 7pm bandwidth. I should really set up caching | 18:13 |
| lifeless | ttx: or keep a cached copy? | 18:15 |
| lifeless | ttx: e.g. ~/src/nova ? | 18:15 |
| ttx | lifeless: I mean for the release script. Enable zuul-cloner cache directory | 18:16 |
| lifeless | ack | 18:17 |
| ttx | it's probably just an env variable away | 18:17 |
| ttx | dhellmann: nova done. | 18:19 |
| * ttx closes shop for today | 18:19 | |
| dims | good night ttx | 18:20 |
| dims | i +2A'ed the .gitreview | 18:20 |
| AJaeger | dims, dhellmann: So, do we have stable/mitaka now? In that case we should setup translations for stable/mitaka. right now the jobs only propose to master and we need to setup the branch in zanata... | 18:29 |
| *** mriedem has quit IRC | 18:35 | |
| *** mriedem has joined #openstack-release | 18:38 | |
| stevemar | dhellmann: ttx dims you'll have a keystone rc1 release request in a few hours, the last few patches are merging | 18:40 |
| dims | AJaeger : https://review.openstack.org/#/q/status:open+topic:create-mitaka | 18:41 |
| dims | AJaeger : oops, https://review.openstack.org/#/q/topic:create-mitaka | 18:42 |
| AJaeger | dims, ok, time for translation setup for these projects... | 18:42 |
| dims | stevemar : ack. i still haven't made any server releases, so dhellmann is the one you need as ttx has wrapped up for the day | 18:43 |
| dhellmann | AJaeger : we should talk about adding that to the branch script so it happens automatically | 18:44 |
| dhellmann | stevemar : are you ready for mitaka? | 18:45 |
| sdague | dhellmann: when do we branch requirements for stable/mitaka | 18:45 |
| dhellmann | stevemar : nevermind, I see your comment in the scrollback now | 18:45 |
| stevemar | dhellmann: soon, got 4 patches going through merge | 18:45 |
| stevemar | :) | 18:45 |
| dhellmann | sdague : I think in the past we've done that after all of the server projects have branched, haven't we? | 18:45 |
| AJaeger | dhellmann: best talk with StevenK and Daisy how to do this on the Zanata side | 18:46 |
| dhellmann | AJaeger : ack, I'll put it on the summit topic list | 18:47 |
| dims | nice catch AJaeger | 18:47 |
| AJaeger | do you have a complete list of projects you create branches for? That might be easier for me to parse than the review list... | 18:49 |
| dhellmann | AJaeger : see the top section of https://docs.google.com/spreadsheets/d/1BLUDgediqgOzLZMMe8a3EAPOtyINAg2rpMtSyWjhC4o/edit#gid=0 | 18:49 |
| dhellmann | AJaeger : the ones with the "Stable" column filled in have branches | 18:50 |
| AJaeger | dhellmann: thanks | 18:54 |
| dhellmann | sridhar_ram1 : there are an uncomfortable number of requirements changes in those liberty releases. in the future, you're going to want to be careful if you want to actually claim support for the stable process | 18:57 |
| sdague | dhellmann: I believe so as well, I'm just trying to get a sense because I think we need to wait for requirements before the devstack / grenade branching to be safe | 19:05 |
| sdague | and that gives us an upgrade testing exposure until that's in play | 19:05 |
| dhellmann | I guess with everything frozen we could technically branch requirements now | 19:06 |
| * dhellmann resolves to write this down when we figure it out | 19:06 | |
| dhellmann | mriedem, ttx: thoughts? ^^ | 19:06 |
| dims | dhellmann : sdague : congressclient is still merging https://review.openstack.org/#/c/293441/ | 19:07 |
| patchbot | dims: patch 293441 - requirements - prevent installing old releases of congressclient | 19:07 |
| dhellmann | dims : oh, thanks | 19:08 |
| sdague | dhellmann: we also need the projects in the main jobs so swift, keystone, cinder still also need branches | 19:08 |
| dims | dhellmann : mriedem : i lost track of the upper-constaints for python-troveclient | 19:08 |
| dims | dhellmann : mriedem : https://review.openstack.org/#/c/292652/ | 19:08 |
| patchbot | dims: patch 292652 - requirements - Update upper-constraints for python-troveclient v2... | 19:08 |
| dhellmann | dims : yeah, we're not releasing 2.2.0 as part of mitaka | 19:09 |
| sdague | and horizon | 19:10 |
| mriedem | dhellmann: seems right to wait to branch the requirements repo until the server projects have | 19:10 |
| dhellmann | ok | 19:10 |
| dhellmann | sdague, mriedem, dims, ttx: I'm starting to add steps in order under the RC1 section of https://etherpad.openstack.org/p/mitaka-release-tracking | 19:11 |
| mriedem | i guess the point being, leave it open in case of last minute changes that a server project needs for it's rc1 right? | 19:11 |
| sdague | mriedem: right, the risk is more backporting work basically | 19:11 |
| sdague | dhellmann: ok, I put the thing under R-2 | 19:13 |
| sdague | I am fine if this is a next week thing, right after the requirements unfreeze | 19:14 |
| sdague | it was just close enough that I figured it was time to poke my head up and allocate a chunk of a day somewhere to do the flips (which should be uneventful), but build in buffer time in case there was any fallout | 19:15 |
| sdague | feel free to move that bit around to wherever is appropriate in your list | 19:16 |
| dhellmann | makes sense, and I like the idea of putting things in the calendar so I've moved the other todo items down | 19:16 |
| sdague | cool | 19:17 |
| *** sridhar_ram1 has quit IRC | 19:24 | |
| *** kro_sniffles is now known as kro_mnckn_doc | 19:27 | |
| *** daemontool has quit IRC | 19:28 | |
| jokke_ | dhellmann: around? | 19:33 |
| dhellmann | jokke_ : here | 19:35 |
| jokke_ | left a question for you into the Liberty libs release requests | 19:35 |
| jokke_ | didn't really get what you are looking for there | 19:36 |
| dhellmann | jokke_ : mriedem has been reviewing liberty releases. frankly, those are not going to be a priority this week | 19:36 |
| dhellmann | we're dealing with rc1 this week | 19:36 |
| jokke_ | dhellmann: was expecting so, that's why they werethere last week like agreed ;) | 19:37 |
| dhellmann | jokke_ : yep. just need the stable team to approve | 19:38 |
| jokke_ | dhellmann: just did not know that we're waiting mriedem for it | 19:38 |
| jokke_ | dhellmann: so flaper87 wasn't enough | 19:38 |
| jokke_ | ? | 19:38 |
| jokke_ | that's why I was wondering | 19:39 |
| mriedem | jokke_: link? | 19:39 |
| jokke_ | https://review.openstack.org/#/c/290774/ | 19:39 |
| patchbot | jokke_: patch 290774 - releases - Release python-glanceclient 1.1.1 Liberty | 19:39 |
| jokke_ | https://review.openstack.org/#/c/290524/ | 19:39 |
| patchbot | jokke_: patch 290524 - releases - Release glance-store 0.9.2 Liberty | 19:39 |
| AJaeger | dhellmann: I suggest to toggle the +A on https://review.openstack.org/#/c/290746/ , it has not merged for a day... | 19:40 |
| patchbot | AJaeger: patch 290746 - glance_store (stable/mitaka) - Update .gitreview for stable/mitaka | 19:40 |
| AJaeger | dhellmann: wait - it has unfullfilled dependencies ;( | 19:40 |
| dhellmann | AJaeger : does that need a rebase? | 19:42 |
| dhellmann | AJaeger : it should have been the first patch on the new branch | 19:42 |
| AJaeger | dhellmann: I don't understand the message and can't help there, just noticed it and wanted to point it out | 19:42 |
| dhellmann | AJaeger : thanks, I'll try rebasing ti | 19:42 |
| *** kzaitsev_mb has quit IRC | 19:50 | |
| *** ig0r_ has quit IRC | 19:55 | |
| *** rockyg has joined #openstack-release | 19:56 | |
| mriedem | jokke_: +1 on the glanceclient release request | 19:57 |
| *** rockyg has quit IRC | 19:57 | |
| mriedem | jokke_: comment in glance-store https://review.openstack.org/#/c/290524/ | 19:57 |
| patchbot | mriedem: patch 290524 - releases - Release glance-store 0.9.2 Liberty | 19:57 |
| *** rockyg has joined #openstack-release | 19:57 | |
| openstackgerrit | Steve Martinelli proposed openstack/releases: release keystone rc1 for mitaka https://review.openstack.org/293689 | 20:05 |
| stevemar | dims: dhellmann ^ | 20:05 |
| dims | stevemar : stray whitespace | 20:06 |
| stevemar | dims: noooo | 20:06 |
| openstackgerrit | Steve Martinelli proposed openstack/releases: release keystone rc1 for mitaka https://review.openstack.org/293689 | 20:07 |
| dhellmann | stevemar : ack, I'll process that after the check jobs run | 20:07 |
| dims | dhellmann : what exactly do you run? | 20:08 |
| dhellmann | dims : release_from_yaml.sh and then make_stable_branch.sh | 20:08 |
| dims | ah ok | 20:08 |
| dims | dhellmann : i had added those 2 to the bottom of the page - https://etherpad.openstack.org/p/mitaka-release-tracking - just wanted to be sure | 20:09 |
| stevemar | dhellmann: thank you kindly sir | 20:09 |
| dhellmann | dims : yep. you know you don't need to specify the yaml filename in that first command, right? the script detects the yaml files updated in the latest commit | 20:09 |
| dims | dhellmann : yep | 20:10 |
| *** kzaitsev_mb has joined #openstack-release | 20:16 | |
| *** AJaeger has left #openstack-release | 20:17 | |
| jokke_ | mriedem: thnx | 20:21 |
| openstackgerrit | Merged openstack/releases: release keystone rc1 for mitaka https://review.openstack.org/293689 | 20:28 |
| stevemar | \o/ | 20:35 |
| dhellmann | stevemar : processing now, was on a call when that finally merged | 20:39 |
| dhellmann | stevemar : https://review.openstack.org/293701 and https://review.openstack.org/293702 | 20:43 |
| *** sridhar_ram has joined #openstack-release | 20:44 | |
| stevemar | dhellmann: and 2x +2/A for you | 20:44 |
| dhellmann | #success keystone's mitaka 9.0.0.0rc1 release is ready | 20:48 |
| openstackstatus | dhellmann: Added success to Success page | 20:48 |
| stevemar | dhellmann: \o/ | 20:48 |
| openstackgerrit | Merged openstack/releases: Release python-glanceclient 1.1.1 Liberty https://review.openstack.org/290774 | 20:55 |
| *** mattoliverau has quit IRC | 20:59 | |
| *** matt6434 has joined #openstack-release | 20:59 | |
| *** matt6434 is now known as mattoliverau | 21:00 | |
| rockyg | dhellmann, did I miss the log_wg? DST is messing me up! | 21:05 |
| jokke_ | rockyg: 2205 UTC now | 21:05 |
| rockyg | Also, I'd love to get some input for the roadmap from you on release -- mitaka and beyond. I know you already put out some mail, but, like to get a little more and some focus | 21:06 |
| *** doug-fish has quit IRC | 21:11 | |
| *** doug-fish has joined #openstack-release | 21:12 | |
| *** kro_mnckn_doc has quit IRC | 21:19 | |
| sridhar_ram | dhellmann: to your earlier point on too many requirements changes in liberty release - point well taken. The liberty 0.2.1 release is an one time anomaly as we hooked up ourselves to pick up requirements automatically after 0.2.0. | 21:20 |
| *** dtantsur|afk has quit IRC | 21:31 | |
| johnsom | Is this the right place to request a gerrit permissions fix for a project? | 21:35 |
| johnsom | openstack/neutron-lbaas-dashboard is missing to permissions for the neutron-release group | 21:35 |
| johnsom | s/to/two | 21:37 |
| *** dtantsur has joined #openstack-release | 21:37 | |
| *** sigmavirus24 is now known as sigmavirus24_awa | 21:48 | |
| *** rockyg has quit IRC | 21:53 | |
| johnsom | Nevermind, I found it. | 21:54 |
| *** mriedem has quit IRC | 21:57 | |
| *** sridhar_ram1 has joined #openstack-release | 22:00 | |
| *** sridhar_ram has quit IRC | 22:01 | |
| *** odyssey4me has quit IRC | 22:09 | |
| *** odyssey4me has joined #openstack-release | 22:09 | |
| *** SergeyLukjanov2 has joined #openstack-release | 22:15 | |
| *** SergeyLukjanov has quit IRC | 22:16 | |
| *** SergeyLukjanov2 is now known as SergeyLukjanov | 22:16 | |
| *** dims_ has joined #openstack-release | 22:16 | |
| *** gordc has quit IRC | 22:18 | |
| *** dims has quit IRC | 22:18 | |
| *** sridhar_ram1 has quit IRC | 22:41 | |
| *** doug-fis_ has joined #openstack-release | 22:47 | |
| *** doug-fish has quit IRC | 22:50 | |
| *** doug-fis_ has quit IRC | 22:51 | |
| *** mriedem has joined #openstack-release | 22:57 | |
| *** sridhar_ram has joined #openstack-release | 23:09 | |
| *** krotscheck has joined #openstack-release | 23:11 | |
| *** sdague has quit IRC | 23:14 | |
| *** mriedem1 has joined #openstack-release | 23:35 | |
| *** mriedem has quit IRC | 23:37 | |
| *** doug-fish has joined #openstack-release | 23:43 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!