Friday, 2016-09-09

*** devananda is now known as devananda|dinner00:04
*** kzaitsev_mb has joined #openstack-release00:49
*** mtreinish has quit IRC01:01
*** kzaitsev_mb has quit IRC01:02
*** mtreinish has joined #openstack-release01:05
*** spzala has joined #openstack-release01:21
*** spzala has quit IRC01:26
dimsEmilienM : i think we encourage it. we release an RC as soon as possible, everyone kicks the tires and we just use the same tag as the last rc as the final (if i remember the process right)01:53
EmilienMdims: ok01:54
dimsEmilienM : example language from last time "Unless release-critical issues are found that warrant a release candidate respin, this RC1 will be formally released as the final Mitaka Keystone release on April 7th. You are therefore strongly encouraged to test and validate this tarball!"01:58
*** kzaitsev_mb has joined #openstack-release01:59
stevemardims: pfft, making me look here unnecessarily :)01:59
dimsLOL stevemar01:59
stevemaryou know the magic word to make me look!01:59
stevemarstarts with a k, ends in eystone01:59
prometheanfirecan someone release oslo.db (again)? :P02:02
*** spzala has joined #openstack-release02:21
*** devananda|dinner has quit IRC02:32
*** mriedem has quit IRC02:46
*** spzala has quit IRC02:48
*** amotoki has quit IRC02:49
*** TravT has quit IRC02:56
*** devananda|dinner has joined #openstack-release02:59
*** myoung is now known as myoung|afk03:05
*** david-lyle_ has joined #openstack-release03:22
*** david-lyle_ has quit IRC03:22
*** armax has quit IRC03:24
*** TravT has joined #openstack-release03:48
*** amotoki has joined #openstack-release03:49
*** rhallisey has joined #openstack-release03:54
*** TravT has quit IRC03:58
*** kzaitsev_mb has quit IRC04:14
*** amotoki has quit IRC04:16
*** spzala has joined #openstack-release04:17
*** spzala has quit IRC04:17
*** rhallisey has quit IRC04:18
*** kzaitsev_mb has joined #openstack-release04:58
*** kzaitsev_mb has quit IRC05:04
*** claudiub|2 has joined #openstack-release05:19
*** claudiub has joined #openstack-release05:21
*** claudiub|2 has quit IRC05:25
*** gcb has joined #openstack-release05:38
*** amotoki has joined #openstack-release05:43
*** kzaitsev_mb has joined #openstack-release06:01
*** claudiub has quit IRC06:01
*** amotoki has quit IRC06:19
*** pcaruana has joined #openstack-release06:23
*** amotoki has joined #openstack-release06:28
ttxEmilienM: RC1 is only needed for milestone-driven projects. For those who don't follow that, you usually release final tags the week(s) before06:39
*** r1chardj0n3s is now known as r1chardj0n3s_afk06:47
*** amotoki has quit IRC06:48
*** amotoki has joined #openstack-release06:52
*** huats has quit IRC07:00
*** amotoki has quit IRC07:02
*** huats has joined #openstack-release07:03
*** gcb has quit IRC07:05
*** claudiub has joined #openstack-release07:13
*** amotoki has joined #openstack-release07:14
*** ihrachys has joined #openstack-release07:20
*** jpich has joined #openstack-release07:29
*** kzaitsev_mb has quit IRC07:48
odyssey4meit looks like we have an urgent release in the pipeline for oslo.db?
*** myoung|afk has quit IRC08:45
*** sdake has joined #openstack-release09:02
*** amotoki has quit IRC09:04
*** shardy has joined #openstack-release09:11
*** sdake_ has joined #openstack-release09:16
*** sdake has quit IRC09:18
ttxyes, we'll likely process it once dhellmann blesses it09:33
*** kzaitsev_mb has joined #openstack-release09:46
huatsdhellmann: hey09:55
huatsjust FYI I wanted to let you know that we still have some feature that we want to put in the newton release of cloudkitty09:56
huatsso we are working on it hard currently09:56
*** sdake has joined #openstack-release09:57
huatsbut we will defenitly have a release by Thursday (and then switch to Feature Freeze...)09:57
huatsI'll be more than happy to discuss that with you if you have any questions !09:57
huatsor comments/advices/...09:57
*** sdake_ has quit IRC10:00
*** shardy has quit IRC10:21
*** sdake_ has joined #openstack-release10:31
*** sdake has quit IRC10:33
*** rhallisey has joined #openstack-release10:39
*** rtheis has joined #openstack-release11:03
*** sdague has joined #openstack-release11:18
*** lucasagomes is now known as lucas-hungry11:55
*** trown|outtypewww is now known as trown12:01
openstackgerritSergey Slipushenko proposed openstack/releases: Release murano-pkg-check 0.0.1
EmilienMttx: we use trailing release, I guess it's the same as milestone + 2 weeks12:14
ttxEmilienM: in trailing you have the choice I'd say12:14
ttxYou can be trailing with a milestone/RC model of releasing, or trailing with direct releases12:15
openstackgerritSergey Slipushenko proposed openstack/releases: Release murano-pkg-check 0.0.1
EmilienMttx: ok, good clarification12:16
ttxEmilienM: it's a new thing though, so might be good to cross-check with dhellmann that I'm not saying crazy things12:16
* ttx is using "thing" too much those days. But then every time I name something I get hatemail12:17
EmilienMinternet of things!12:17
*** bobh has joined #openstack-release12:19
*** mriedem has joined #openstack-release12:26
*** gordc has joined #openstack-release12:30
*** bobh has quit IRC12:30
openstackgerritIhar Hrachyshka proposed openstack/releases: Use openstack-announce@ for all neutron stadium service announcements
ihrachysdhellmann: does send-announcements-to work for all deliverables tracked in openstack/releases? I can't find announcement for networking-sfc 2.0.012:37
ihrachysI would think something would trigger the email once the patch lands?12:38
EmilienMdhellmann: good morning, I have a doubt if I should propose rc1 (which would likely be the final) release for PuppetOpenStack or if I can wait until end of September12:41
*** sdake_ is now known as sdake12:47
odyssey4meihrachys yeah, you need to have a release jon in openstack-infra/project-config12:48
odyssey4meihrachys it's the announce-release job12:50
*** lucas-hungry is now known as lucasagomes12:51
* dhellmann notes lots of scrollback12:54
dhellmannhuats : at this point I strongly urge you to focus on finishing features that have been started, and not try to start anything completely new12:57
dhellmannodyssey4me , ttx: it's friday. do we still want the oslo.db release?12:58
huatsdhellmann: that is the case. We don't start new features, we are finishing them12:58
dhellmannEmilienM : if you're generally following milestone tagging patterns, it's better if you prepare an rc1, but if you're following the intermediary versioning then you don't need to12:59
ttxdhellmann: no idea what the urgency is12:59
dhellmannhuats : great!12:59
ttxdhellmann: does that trigger a requirements bump ?12:59
ttxdoes the unblock gate ?12:59
EmilienMdhellmann: ack12:59
odyssey4mesileht can you answer questions posed about ?13:00
dhellmannttx: a constraints bump at least. I don't know where we settled on the question of blocking older versions13:00
ttxwe'll want that constraints bump in before RC1, which means waiting for Monday pushes us back a bit13:01
ttxso I'm for it13:01
dhellmannI guess with the constraints in unit tests now we're safer13:02
* dhellmann wonders how many projects actually implemented that13:02
dhellmannok, approving13:02
silehtodyssey4me, I don't see any questions13:03
odyssey4mesileht it would appear that the ball is rolling, dhellmann and ttx had questions regarding the urgency13:04
*** sdake has quit IRC13:05
dhellmannttx: do we want independent projects announcing on openstack-announce?
openstackgerritRichard Theis proposed openstack/releases: networking-ovn Newton RC1 deliverable
huatsdhellmann: we have been looking the recommended way for wsgi service. We haven't found anything special, but ttx told me you might have an opinion. I'd be  really interested in knowing it, since we have received some patches for that (that use werkzeug)13:08
openstackgerritMerged openstack/releases: Release oslo.db 4.13.3 (newton)
huats(and I am not saying it will be included in our release, it is a question we had in the pipe for some time now...)13:09
ihrachysodyssey4me: oh. I would honestly expect that to work as is. seems duplicated.13:09
dhellmannhuats : you're building a new wsgi service? I think we have a significant number of projects using either pecan or flask, so I would start with one of those13:09
ihrachysodyssey4me: also, before we saw some announcements from dhellmann so we thought it's automated somehow13:09
*** claudiub has quit IRC13:10
dhellmannihrachys : you thought what was automated?13:10
ihrachysdhellmann: that when openstack/releases change lands, email is sent to designated mailing list about the new release13:10
ihrachysdhellmann: seems like unless I set some jobs in project-config, it does not work this way.13:11
ihrachysdhellmann: the way it is now, we have those addresses set in openstack/releases, but nothing happens.13:11
dhellmannihrachys : which project?13:11
ihrachysdhellmann: networking-sfc for one13:11
huatsdhellmann: no I was misunderstood. We already using pecan. The question is related to the application server (like uwsgi, gunicorn,.. or werkzeug like we have seen in ceilometer by instance)13:12
dhellmannihrachys: it should be automated, but it does depend on having the jobs and repo configured properly13:12
ihrachysdhellmann: we released 2.0.0 lately but did not have an announcement email. and now odyssey4me says it's as designed.13:12
ihrachysdhellmann: right. wouldn't it make sense to have a single job to handle all patches for openstack/releases?13:12
ihrachysdhellmann: assuming deliverable files are approved by release team, it seems twisted to have it approved by infra to be able to send an announcement.13:13
dhellmannhuats : ah, sorry, I misunderstood your question. I do not personally have a strong opinion on that. We've discussed the idea of moving devstack to deploying all projects behind apache, but if you're using wsgi then any of the compatible servers should work well. It would be a good question for the -dev mailing list.13:13
odyssey4meihrachys only the job needs to be set for the repo you want to have announcements for - that's a once off thing per repo, once that's in, the announcements are automated when a release is done13:13
dhellmannihrachys : the email is not triggered by landing a patch, it is triggered by the tag. The tag is triggered by landing a patch.13:14
huatsdhellmann: ok thanks !13:14
dhellmannihrachys : the job is attached to the repo actually being packaged13:14
ihrachysodyssey4me: you probably don't know how many repos stadium has :P13:14
odyssey4meihrachys sure, but we have many repositories too :)13:14
ihrachysdhellmann: ok I was under wrong impression it worked before by magic and not by you sending those emails manually :)13:15
dhellmannihrachys : give me a minute to look into it13:15
odyssey4meihrachys I expect that a job group/template is being used - so just add the job there, for example:
dhellmannihrachys : here are the logs from the release jobs:
dhellmannihrachys : the email was skipped because you tagged the release by hand and the script didn't have the metadata it needed:
dhellmannihrachys : this is why I want you to let us tag the releases.13:17
ihrachysdhellmann: I was told before that we should do it ourselves. now I am told that release folks should handle it. I am puzzled.13:18
ihrachysdhellmann: btw I am happy if release team handles all releases and tags, only expecting +1 from neutron release liaison.13:18
dhellmannihrachys : I was referring to our conversation from a day or two ago13:19
ihrachysdhellmann: we also have some internal instructions for neutron-release team members on how to tag releases, and we follow those. apparently it's not enough. if release team is ok with doing tagging, we can just clean up all those intructions we have.13:19
dhellmannnow that we have the automation in place, we're able to take more of the independent projects on13:19
ihrachysdhellmann: can you handle all networking-* (in-stadium) neutron projects for us?13:20
dhellmannthe automation is being built under the assumption that folks doing tagging themselves are less interested in the automation13:20
dhellmannihrachys : sure, now that it's just a matter of clicking +2a13:20
ihrachysdhellmann: ok, I was not aware of the change in the ease of the process.13:20
ihrachyswe are glad to offload it ;)13:20
dhellmannihrachys : it only happened a week ago :-)13:20
*** mriedem has quit IRC13:20
ihrachyslemme update our internal instructions then and send an email for all neutrinos on the change to the process.13:21
dhellmannihrachys : cool. we'll still want the  +1 from the liaison or ptl, as we discussed the other day13:21
ihrachysbut no more tag -s13:21
*** mriedem has joined #openstack-release13:22
ihrachyswe then probably should remove permissions to do it from neutron-release team?13:22
dhellmannihrachys : yes, if you delete those stanzas from the gerrit acl files the permission will default to the release managers and the bot13:24
* dhellmann has to drop off to attend a meeting13:24
ihrachysdhellmann: what about branches?13:24
dhellmannihrachys : branch and tag acls are different. maybe leave branch acls alone for now, and we can handle those next cycle if we get the automation working?13:25
ihrachysthanks a lot!13:25
*** mriedem has quit IRC13:26
*** sdake has joined #openstack-release13:30
openstackgerritMerged openstack/releases: add example shell commands for batch branching
openstackgerritMerged openstack/releases: increase allowed line length before emitting a warning
openstackgerritMerged openstack/releases: try to print a warning when a non-milestone project uses a pre-release
openstackgerritMerged openstack/releases: add instructions for updating the default series name
openstackgerritMerged openstack/releases: configure tox to always reinstall the tools
openstackgerritMerged openstack/releases: add a command to look for missing releases
openstackgerritMerged openstack/releases: add steps about updating devstack-gate
openstackgerritMerged openstack/releases: Document when to add new branch jobs
openstackgerritMerged openstack/releases: Add branch order details on devstack and grenade
*** rhallisey has quit IRC13:43
*** rhallisey has joined #openstack-release13:44
*** sdague has quit IRC13:50
*** dansmith is now known as superdan13:50
*** mriedem has joined #openstack-release13:59
dhellmannttx: I'm on a call, we'll start the meeting a few minutes late14:01
*** bobh has joined #openstack-release14:01
dhellmannwell, we wrapped because the other party had a meeting, too14:01
*** mriedem1 has joined #openstack-release14:03
*** mriedem has quit IRC14:04
*** inc0 has joined #openstack-release14:04
*** bobh has quit IRC14:06
*** mriedem1 is now known as mriedem14:06
*** TravT has joined #openstack-release14:07
*** TravT has quit IRC14:08
*** myoung has joined #openstack-release14:09
*** TravT has joined #openstack-release14:10
*** myoung is now known as myoung|bbl14:12
*** bobh has joined #openstack-release14:14
*** spzala has joined #openstack-release14:15
openstackgerritMerged openstack/releases: Use openstack-announce@ for all neutron stadium service announcements
openstackgerritDean Troyer proposed openstack/releases: Release python-openstackclient 3.3.0
*** vgridnev has quit IRC14:22
*** askb has quit IRC14:25
*** kzaitsev_mb has quit IRC14:27
openstackgerritMerged openstack/releases: proposed ocata schedule
openstackgerritMehdi Abaakouk (sileht) proposed openstack/releases: Release aodh 2.0.5 for mitaka
*** myoung|bbl is now known as myoung14:56
openstackgerritamrith proposed openstack/releases: update ocata schedule with trove specific stuff
*** huats has quit IRC14:59
fungidhellmann: ttx: at least for infra, i doubt we'd have release cycle stewards separate from the active ptl15:00
fungibut i'll grant we're probably an exception15:01
ttxyou don't do cycle-based release stuff anyway15:01
dhellmannfungi : yeah, it would be less important for infra15:01
fungiright, exactly15:01
*** armax has joined #openstack-release15:02
fungithat's not to say the coordinated release cycle doesn't affect us and our scheduling of things, but for us it's more the cadence and not activities for a specific release vs another release15:02
ihrachysttx: you said 'someone should propose it'. I was thinking you are in better position to do it, but if not, I could try to craft something, but on Mon only. And honestly I am not proficient in all those governance repos so it may take more of my time, or I can screw15:03
ihrachysbut I can try15:03
openstackgerritamrith proposed openstack/releases: Update Ocata schedule with Trove specific stuff
*** huats has joined #openstack-release15:05
fungii have a feeling teams like app catalog, ui/ux, qa, refstack and security are similarly not release-tracking teams that would need per-release stewards (or maybe not qa because of devstack and grenade having stable branches)15:08
*** pcaruana has quit IRC15:08
*** ihrachys has quit IRC15:08
*** kzaitsev_mb has joined #openstack-release15:09
ttxihrachys: the trick is, it looks like a small change from your perspective, but the ramifications (for the elected people) are significant. If the next election run happen in January/February compared to April, their term is pretty short15:09
ttxso some people might oppose it15:10
ttxPersonally I don't think the change is necessary, so I'd rather not drive it15:10
ttxespecially since people seem to like to oppose things I push15:10
ttxIn all cases it would kick in after the election period anyway15:11
ttxsince the elections run from data that was tagged last week15:11
ttxoh wait15:12
ttxthe wording actually uses "design summit" in some places. Since that's dissolved, there *is* clarification needed15:13
ttx(fater we do the Barcelona one)15:13
ttxdhellmann: ^15:21
*** amotoki has joined #openstack-release15:27
*** openstackgerrit has quit IRC15:49
*** openstackgerrit has joined #openstack-release15:49
-openstackstatus- NOTICE: New setuptools release appears to have a circular import which is breaking many jobs - check for ImportError: cannot import name monkey.15:54
*** ChanServ changes topic to "New setuptools release appears to have a circular import which is breaking many jobs - check for ImportError: cannot import name monkey."15:54
*** dtantsur is now known as dtantsur|afk15:59
*** amotoki_ has joined #openstack-release16:02
*** amotoki_ has quit IRC16:03
*** amotoki has quit IRC16:05
*** spzala has quit IRC16:21
*** spzala has joined #openstack-release16:22
*** sdake has quit IRC16:28
*** kzaitsev_mb has quit IRC16:41
*** lucasagomes is now known as lucas-afk16:44
*** jpich has quit IRC16:52
*** trown is now known as trown|lunch16:56
*** ChanServ changes topic to "OpenStack Release Managers office - Where weekly 1:1 sync points between release manager and PTLs happen - Logged at"16:58
-openstackstatus- NOTICE: setuptools 27.1.2 addresses the circular import16:58
*** kzaitsev_mb has joined #openstack-release17:04
openstackgerritamrith proposed openstack/releases: Update Ocata schedule with Trove specific stuff
amrithdhellmann, done ^^17:13
*** kzaitsev_mb has quit IRC17:17
*** bnemec is now known as beekneemech17:28
*** devananda|dinner is now known as devananda17:32
dhellmannttx: what is the new summit called? just "summit"?17:54
dhellmann(no "design")17:54
*** trown|lunch is now known as trown17:55
clarkbdhellmann: I think ttx has left for the weekend but I am trying to get you an answer17:56
dhellmannclarkb : ok, thanks. It can wait for next week. I'm not prepared to try to rewrite the election rules on my own on a friday afternoon. :-)17:56
*** TravT has quit IRC18:41
clarkbdhellmann: "Forum" is what I am told is in current use18:54
dhellmannhmm, ok. I thought that was just a part of the event, but I may have misunderstood18:54
dhellmannI thought jbryce wanted to keep the summit branding. Maybe he was talked out of that.18:54
*** sdague has joined #openstack-release18:57
openstackgerritMerged openstack/releases: move the step for creating the dashboard earlier in the process
sigmavirusdhellmann: but think, you could tell someone that a funny thing happened on the way to the forum!19:06
*** kzaitsev_mb has joined #openstack-release19:16
*** spzala has quit IRC19:17
openstackgerritDoug Hellmann proposed openstack-infra/release-tools: teach latest-deliverable-versions to diff against the dashboard
*** sdake has joined #openstack-release19:38
dhellmannsigmavirus : we should definitely try to get someone to stage that in boston19:38
*** sdake has quit IRC19:42
*** sdake has joined #openstack-release19:44
sigmavirusdhellmann: agreed19:45
*** huats has quit IRC20:25
*** superdan is now known as dansmith20:27
openstackgerritSergey Slipushenko proposed openstack/releases: Release murano-pkg-check 0.0.1
*** askb has joined #openstack-release20:44
*** huats has joined #openstack-release20:54
clarkbdhellmann: apparently more clarity and the Summit is still the Summit and will have the Forum in it20:56
dhellmannclarkb : ok, that was my understanding from the way ttx had talked about it in the past20:57
dhellmannclarkb : thank you for confirming20:57
*** openstackstatus has quit IRC20:57
*** openstackstatus has joined #openstack-release20:59
*** ChanServ sets mode: +v openstackstatus20:59
*** inc0 has quit IRC21:16
*** trown is now known as trown|outtypewww21:21
*** bobh has quit IRC21:40
*** rtheis has quit IRC21:43
*** rakhmerov has quit IRC21:44
*** kzaitsev_ws has quit IRC21:45
*** gordc has quit IRC21:46
*** kzaitsev_ws has joined #openstack-release21:47
*** rakhmerov has joined #openstack-release21:47
*** huats has quit IRC22:00
*** huats has joined #openstack-release22:06
*** mriedem has quit IRC22:11
*** huats has quit IRC22:16
*** huats has joined #openstack-release22:17
*** inc0 has joined #openstack-release22:24
*** huats has quit IRC22:36
*** sdague has quit IRC22:38
*** huats has joined #openstack-release22:38
*** sdake has quit IRC22:40
*** inc0 has quit IRC22:50
*** bobh has joined #openstack-release22:54
*** bobh has quit IRC22:57
*** hongbin has quit IRC22:58
*** armax has quit IRC23:20
*** sdake has joined #openstack-release23:22
*** armax has joined #openstack-release23:44
*** kzaitsev_mb has quit IRC23:48

Generated by 2.14.0 by Marius Gedminas - find it at!