Tuesday, 2016-05-17

*** Qiming has joined #openstack-release00:07
*** thinrichs has quit IRC00:21
*** thinrichs1 has joined #openstack-release00:21
*** doug-fish has quit IRC00:23
*** kzaitsev_mb has quit IRC00:25
*** sdake_ has joined #openstack-release00:27
*** sdake has quit IRC00:30
*** Qiming has quit IRC00:31
*** rhallisey has joined #openstack-release00:42
*** mriedem has joined #openstack-release00:47
*** kzaitsev_mb has joined #openstack-release00:50
*** thinrichs1 has quit IRC01:01
*** kzaitsev_mb has quit IRC01:16
*** cody-somerville has joined #openstack-release01:18
*** Qiming has joined #openstack-release01:21
*** bobh has quit IRC01:36
*** rhallisey has quit IRC01:41
*** bobh has joined #openstack-release01:49
*** sridhar_ram has quit IRC02:07
*** kzaitsev_mb has joined #openstack-release02:13
*** kzaitsev_mb has quit IRC02:18
*** mriedem has quit IRC02:28
*** bobh has quit IRC02:44
*** bobh has joined #openstack-release02:56
*** bobh has quit IRC03:02
*** kzaitsev_mb has joined #openstack-release03:14
*** kzaitsev_mb has quit IRC03:19
*** armax has quit IRC03:20
openstackgerritMerged openstack/releases: add keystone dates to release schedule  https://review.openstack.org/31477903:33
*** sdake has joined #openstack-release03:36
*** sdake_ has quit IRC03:38
*** kzaitsev_mb has joined #openstack-release04:15
*** sdake_ has joined #openstack-release04:19
*** sdake has quit IRC04:20
*** kzaitsev_mb has quit IRC04:20
*** dave-mccowan has quit IRC04:37
openstackgerritJoshua Harlow proposed openstack/releases: Add a yamlutils file and a reformatting command  https://review.openstack.org/30853304:46
openstackgerritJoshua Harlow proposed openstack/releases: Add a interactive-cmd to propose library releases  https://review.openstack.org/30802904:46
*** sdake_ has quit IRC04:56
*** kzaitsev_mb has joined #openstack-release05:17
*** kzaitsev_mb has quit IRC05:22
*** kzaitsev_mb has joined #openstack-release07:18
*** kzaitsev_mb has quit IRC07:24
*** shardy has joined #openstack-release08:03
*** kzaitsev_mb has joined #openstack-release08:20
*** kzaitsev_mb has quit IRC08:25
*** kzaitsev_mb has joined #openstack-release08:37
*** kzaitsev_mb has quit IRC08:42
*** kzaitsev_mb has joined #openstack-release08:46
*** kzaitsev_mb has quit IRC09:11
*** electrofelix has joined #openstack-release09:17
*** dtantsur|afk is now known as dtantsur09:21
*** ihrachys has joined #openstack-release09:34
*** dave-mccowan has joined #openstack-release09:35
*** amotoki has joined #openstack-release09:35
*** kzaitsev_mb has joined #openstack-release10:15
*** sdague has joined #openstack-release10:18
openstackgerritDmitry Tantsur proposed openstack/releases: Release python-ironic-inspector-client 1.7.0 for Newton  https://review.openstack.org/31675010:19
*** Qiming has quit IRC10:25
*** daemontool has quit IRC10:41
*** daemontool has joined #openstack-release10:45
*** dtantsur is now known as dtantsur|bbl10:55
*** TravT has quit IRC11:06
*** TravT has joined #openstack-release11:07
*** lucasagomes is now known as lucas-hungry11:07
*** amrith has quit IRC11:09
*** amrith has joined #openstack-release11:12
*** Qiming has joined #openstack-release11:20
*** rhallisey has joined #openstack-release11:26
*** gordc has joined #openstack-release11:36
*** Qiming has quit IRC11:37
*** Qiming has joined #openstack-release11:40
*** Qiming_ has joined #openstack-release11:43
*** rhallisey has quit IRC11:45
*** Qiming has quit IRC11:46
*** rhallisey has joined #openstack-release11:46
*** dave-mccowan has quit IRC11:47
*** TravT_ has joined #openstack-release11:49
*** TravT has quit IRC11:51
*** Qiming_ has quit IRC11:54
*** Qiming has joined #openstack-release11:57
*** Qiming has quit IRC11:58
*** Qiming has joined #openstack-release12:04
*** bobh has joined #openstack-release12:06
*** Qiming has quit IRC12:06
*** Qiming has joined #openstack-release12:07
*** dave-mccowan has joined #openstack-release12:13
*** lucas-hungry is now known as lucasagomes12:13
*** bdemers has quit IRC12:15
*** Qiming has quit IRC12:16
*** Qiming has joined #openstack-release12:16
*** bobh has quit IRC12:24
*** dtantsur|bbl is now known as dtantsur12:45
*** amrith is now known as _amrith_13:00
ttxdhellmann: o/13:01
dims_ttx : dhellmann : o/13:01
dhellmannttx, dims: good morning13:02
dhellmannsorry I'm running late, hardware issues here13:02
dhellmannshall we talk about golang?13:02
ttxwe shall13:02
dhellmannI made some notes in https://etherpad.openstack.org/p/relmgt-golang-notes13:02
ttxcatching up13:03
dhellmannI'm far from an expert on this, obviously, but what I found raised a lot of questions13:03
ttxso, from a pure release management perspective...13:04
ttxShipping Go is still about putting files in a tarball and assigning a version number to that artifact13:05
fungiohai, i'm around now13:05
fungi(was around earlier but sucked into other conversations)13:05
dhellmannhi, fungi13:05
ttxThey don't seem to require something like Pypi since you can point directly to a git repo / URL13:05
*** doug-fish has joined #openstack-release13:06
fungigranted, python doesn't "require" pypi either. we have plenty of python-based projects we don't upload there13:06
ttxIt can also support stable branches alright - just create a branch and all13:06
ttxwhere it gets fuzzy is when you start creating dependencies rather than "main" code13:06
dhellmannttx: that's easy for apps. it's not clear how that works for libs.13:06
ttxright13:06
ttxdo Go libraries use versioning at all ?13:07
fungii'm expecting we can reuse most of our existing release pipeline. we already have non-python tarball jobs for stuff that just needs to be "tarred up" with no build step13:07
dhellmannthat wasn't clear. it didn't seem like it.13:07
ttxit feels like Go is encouraging all-in-one with minimum library creation13:07
dhellmannfungi : that's good to know, I wasn't sure if we had a job like that13:08
ttxand then vendoring as the default dependency mechanism13:08
fungii'll dig up an example for the record13:08
ttxso as long as we don't create openstack go libraries (think oslo style), this is not really a release management issue13:08
dhellmannyeah, early on I wouldn't expect a lot of libraries anyway. as the code base grows, who knows.13:09
ttxif we have common code, we could use oslo-incubator style code copy as an alternate to pure fork/vendoring13:09
dhellmannbut that's my impression of their recommended practice, based on what I could find last week13:10
dhellmannthat would be one way, yes.13:10
ttxit feels like for "libraries" we would maintain a canonical version and the various main code users would copy the code from time to time, no versioning there13:10
ttxwould be interesting to see how hummingbird did it. Code copies ?13:11
* ttx looks13:11
fungiyeah, i'm noticing the vast majority of packages in debian starting with "golang-" end in "-dev" (implying they're used only when compiling a golang application) and many package versions like 0.0~git20150714.0.46b9627-113:13
dhellmannI don't really see anything that looks like a library in the hummingbird branch13:13
*** bobh has joined #openstack-release13:13
ttxdhellmann: feels like they don't have reproducible builds -- using go get to produce favor-of-the-month based on current state of deps13:13
ttxflavor13:13
*** mriedem has joined #openstack-release13:14
fungithere are _some_ goish upstreams using versioning. an obvious example is https://github.com/blang/semver13:14
dhellmannthere was a tool that helped track some of the dependencies for repeatable builds, but I think the way you make them repeatable is to check the dependencies into your local repo13:14
fungidhellmann: there are several of those now13:14
fungimordred has been amassing (and trying out) the list of them13:14
ttxdhellmann: arguably those are all infra/QA issues more than releasemanagement issues though13:15
dhellmanngodep records a json file with the path and revision hash13:15
fungihttps://etherpad.openstack.org/p/golang-infra-issues-to-solve is where we're starting to track infra-related stuff for this13:15
ttxi.e. we can still very much tag a repo and tarball up a repository and call it the "release"13:15
ttxwe don't make binary releases13:15
ttxonly source code releases13:15
fungiyeah, someone mentioned something else newer than godep which is apparently better, and then someone else mentioned something even newer than that thing which i heard was more betterer still13:16
ttxwhether that actually works once you pull the deps in is more of a QA / gate question13:16
fungiapparently the go tradition is to replace tools over and over until one becomes popular enough everyone switches to it13:16
dhellmannyeah, if we're only worried about building tarballs of source it sounds like we have the job for that already13:16
fungibut the ecosystem there seems to be evolving so quickly i'd hesitate to claim we're going to use one specific tool for this13:17
ttxdhellmann: same way we treat Javascript really13:17
dhellmannttx: right13:17
dhellmannfungi : yeah, I'm less concerned with picking one solution than ensuring that at least one exists for the go folks in our community to use13:17
ttxdhellmann: I'm still concerned, wearing my openstack TC hat -- but not so much wearing my RelMgt hat13:17
ttxbasically they could even vendor the code of the deps in and we'd still be able to ship that13:18
ttxthey can change over time and we don't really care either13:18
dhellmannttx: much the same. the treatment of libraries is a bit of a concern, but if the expectations are so low on that then I won't lose any sleep over it13:18
ttxIt's pretty clear that they use tags and branches13:18
ttxwhether those end up being usable in gate testing ins another story13:19
ttxI'm a bit concerned that they seem to discover the issue of dependency management as they go (pun)13:19
dhellmannI think a lot of that is coming from google's practice of having one massive source repository for everything.13:19
dhellmannmaybe not, but that was my impression13:20
fungihttp://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/javascript.yaml#n45 http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/openstackid.yaml#n26 http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/groups.yaml#n2813:20
fungithose are a few example non-python jobs that release tarballs13:20
ttxdhellmann: well yes, there is no canonical tool, so they are waiting for their pip. They will likely end up with a mess of tools like npm+grunt+bower13:20
ttxin the meantime Google just copies code around13:20
dhellmannfungi : thanks, noted13:21
ttxdhellmann: when they say "vendoring", are they getting binary artifacts (jar style) or source code copies ?13:21
dhellmannsource13:21
fungiwe'll still likely need a go-specific tarball job on the assumption that there's metadata somewhere we'll use for figuring out version numbers13:21
ttxMy understanding is that "go get" retrieve source code13:21
ttxright13:21
dhellmannthey check out the source upstream, and put the files in their local repo13:21
dhellmannfungi : wouldn't we use the tag for the version?13:22
ttxso in terms of ugliness, it's still slightly less ugly than the Java habit of shoving jars in lib/ subdirectories13:22
dhellmannyeah, at least it's not binary artifacts being vendored13:22
fungiyeah, the workflow, as it's been explained to me, is that you pull dependency sources into your local checkout and then run your build process to produce binaries, and you commit just a file (generated by godep or similar) to record the provenance of your deps rather than checking your deps in13:23
ttxfungi: in the review the propĂ´ser mentioned progress on the infra side. COuld you summarize that, and tell us whether the question of dependency management was tackled yet ?13:23
dhellmannfungi : ah, ok, that's different from what I was seeing so thanks for clarifying13:24
fungiyeah, https://etherpad.openstack.org/p/golang-infra-issues-to-solve mentions several dependency management tools in the go ecosystem with some changes implementing each to give us a side-by-side view13:25
fungigodep, govendor and glide are apparently the front-runners for this13:25
ttxfungi: that's the godep workflow, right ?13:25
ttxnot exactly the only option in town13:25
fungithat workflow is supposedly mirrored in later tools which aim to replace godep13:26
fungiemerging as the sane alternative to checking your deps into your source and carrying around forks of everything13:26
*** dtantsur has quit IRC13:27
ttxhmm, ok13:27
dhellmannsaving a reference is a lot more sane than all of the code, even if the reference isn't a version number but a sha13:27
fungiwhich is still i guess the enterprise/google way of doing things, because forgetting to fix security bugs in lots of random altered copies of a dependency is better than not being 100% sure you can reproduce exactly the same binary artifact13:28
ttxdhellmann: so with our relmgt hat on I think we can consider there is minimal effort to support "releasing" source code tarballs of Go stuff13:28
* ttx checks how much common practice it is to actually have signed tarballs in that world13:28
dhellmannttx: that's my conclusion, too13:28
fungiwell, tarball signing is going to be ubiquitous because the job for that will just operate on raw artifact files and create detached signatures, so completely language/platform agnostic13:29
fungiwhether their tools actually check signatures (and have some means for recording whose key should be signing them) is another question13:29
dhellmannright, I think the question is if anyone (other than us) would care if we produced them13:30
ttxhttp://kubernetes.io/docs/getting-started-guides/binary_release/ does not propose source code13:30
*** dtantsur has joined #openstack-release13:30
dhellmannor if everyone consuming the code would want to use the upstream git repo13:30
ttxdhellmann: in the case of Swift I'd expect them to keep both versions in the same tree13:30
ttxi.e. a mix of python and Go code13:30
fungifor perspective, pypi is dropping signed artifact support in the ui and dstufft is also not planning to implement it for warehouse (the pypi replacement)13:30
ttxlike the branch currently is13:30
dhellmannttx: ok, that would make the builds a bit more complex if we wanted to produce separate artifacts.13:31
fungimy expectation is that we'll end up only publishing signatures ourselves on tarballs.o.o (which is still useful for us to be able to perform toolchain vetting and post-mortem compromise detection)13:31
dhellmannright13:31
ttxdhellmann: so we start getting strongly impacted if we are expected to release binary versions13:32
fungiare go binaries completely platform-independent?13:32
dhellmannI don't think so13:32
mordredfungi: what did I do?13:32
fungii haven't really researched the binary distribution end of things there13:32
ttxI think distros still want tarballs13:32
dhellmannthey still use the underlying system libs, right?13:32
*** openstackgerrit has quit IRC13:32
fungimordred: just blaming you for the go research etherpad we have being full of useful info13:33
mordredawesome13:33
*** openstackgerrit has joined #openstack-release13:33
mordredbtw - I just wrote a patch to golang to grok git.openstack.org13:33
* ttx looks up a few go packages source13:33
*** doug-fish has quit IRC13:33
mordredhttps://go-review.googlesource.com/2313513:34
fungiunclean!13:35
fungigo really has specific domain names whitelisted for dependencies?13:35
fungioh, i bet it's because they don't encode full clone urls and expect to parameterize them?13:36
dhellmannttx: if we're done, I'm going to look at the release queue for this week13:36
mordredfungi: it's actually just so that they can infer vcs for common repo things13:36
fungioh, so you can still reference them explicitly if you want without that?13:37
mordredyes. if you look at https://review.openstack.org/#/c/315028/13:37
patchbotmordred: patch 315028 - swift (feature/hummingbird) - Update paths to point to git.openstack.org13:37
ttxew13:37
mordredlike here: https://review.openstack.org/#/c/315028/1/go/objectserver/auditor.go13:37
patchbotmordred: patch 315028 - swift (feature/hummingbird) - Update paths to point to git.openstack.org13:37
mordredyou'll see I had to append .git to the dependency name13:37
mordredto point it at our servers instead of github13:38
fungido any of the dependency vendoring tools support tarballs in place of git refs? just wondering if there's any reason to publish source tarballs at all13:38
mordredI do not think so, no13:38
mordredor, at least, if they did, I'm not sure that anyone in the go community would use them13:38
mordredhowever, I do think we shoudl publish source tarballs13:38
dhellmannfungi : I think the idea is to give distros a tarball of the app to be packaged, no?13:38
mordredbecause distros13:38
mordreddhellmann: ++13:38
ttxlooking a deb packaging now makes my eyes bleed13:38
mordrednormal go users will not care about tarballs13:39
ttxI guess it's something you really are glad to forget13:39
*** inc0 has joined #openstack-release13:39
fungidhellmann: well, debian package maintainers seem to be packaging arbitrary git refs (at least for go dependencies)13:39
fungialmost all the package version numbers are 0~git-somedate-somesha-packagerev13:39
dhellmannfungi : ok, so we may have even less work to do if that's how the distros want it13:39
*** bdemers has joined #openstack-release13:40
fungii see a handful with actual non-zero version numbers, and those still are probably being packaged from git, just from explicit tags or something13:40
ttxfungi: they have to given that the go practice seems to be to not release13:40
funginot that generating tarballs of this stuff would be in any way hard13:40
fungimordred: are go binaries completely platform-independent? if not, i'm assuming we'd just punt on compiled artifact publishing too13:41
mordredfungi: they are not13:42
ttxdhellmann: ok, so I think we can summarize our official view as "tagging and releasing source code tarballs made from Go code has minimal costs for the release management team. Unless we are expected to release binary versions, in which case it's actually very costly (and probably difficult until the Golang world comes to its senses)13:42
mordredfungi: and yes, I think we should totally punt on compiled binaries13:42
fungiwe need to compile them locally on workers to test, but i wouldn't expect to publish the compiled bits in that case unless it was for test evaluation purposes13:42
mordredalso, I do not think anyone expects them13:42
openstackgerritIhar Hrachyshka proposed openstack-infra/release-tools: Added tool to scan project repo for new bug fixes in master  https://review.openstack.org/29642013:42
mordredgolang is very VCS oriented - so us having source code in a git repo is pretty much all people expect13:42
funginobody expects the spanish inquisition13:42
ttxmordred: yeah, that is my read too13:43
mordredfungi: amongst its chief weaponry are such diverse elements as ...13:43
dhellmannttx: that sums it up well. I would add that I expect projects using golang to contribute to fixes to any release tools needed to make their projects work.13:43
fungiyep, we've been toeing that line for infra stuff too13:44
*** sdake has joined #openstack-release13:44
ttxdhellmann: then with our TC hat on we can voice our fear that repeatable builds testing and proper gating will probably be non-trivial to achieve13:46
dhellmannttx: I thought with the dep tools infra is evaluating that would be solved?13:46
fungifor some definitions of "repeatable"13:47
dhellmanndon't they all point to the sha to check out?13:47
fungithe moment some dependency author decides to force-push a non-ff update into their repo, all bets are off13:47
dhellmannoh, well, yeah13:47
fungior replace a git tag, or...13:47
openstackgerritIhar Hrachyshka proposed openstack-infra/release-tools: Added tool to filter out bugs of specified importance  https://review.openstack.org/29642113:48
fungiwe have similar challenges with python/pip/pypi too though13:48
*** sdake_ has joined #openstack-release13:48
fungiit's gotten better now that pip won't install things from off-pypi without coersion and now that pypi no longer allows you to upload a replacement for an already uploaded version even if you delete it13:48
*** sdake has quit IRC13:49
mordredfungi: there is a lot of work to support any of those go deps tools13:49
mordredfungi: for instance, someone is going to have to teach zuul-cloner to do the right things with it13:49
mordredbecause go expects a very specific filesystem layout13:49
fungia wrapper/shim could probably handle it13:49
mordredthe nice part is that it _will_ play nice with zuul-cloner plopping the source code into the right places13:49
mordredbut the work needs to be done13:50
fungisomething to generate an appropriate clonemap would suffice, right?13:50
mordredmaybe13:50
mordrednot 100% sure13:50
mordredbut I know it's a thing that will need to be designed and implemented13:50
mordredfungi: I've mostly been learning about this so that I know enough to review designs13:52
openstackgerritIhar Hrachyshka proposed openstack-infra/release-tools: Added tool to filter out bugs with specific tag  https://review.openstack.org/29645413:52
openstackgerritIhar Hrachyshka proposed openstack-infra/release-tools: Added tool to filter out bugs of specified importance  https://review.openstack.org/29642113:52
fungimordred: perfect. i'll likely not even review them until they have your +2 ;)13:53
*** sigmavirus24_awa is now known as sigmavirus2413:54
*** doug-fish has joined #openstack-release13:54
*** njohnsto- is now known as njohnston--13:56
openstackgerritIhar Hrachyshka proposed openstack-infra/release-tools: Add tool that annotates bug numbers with details from LP  https://review.openstack.org/29647013:56
*** doug-fis_ has joined #openstack-release13:56
*** bdemers has quit IRC13:59
*** doug-fish has quit IRC13:59
*** doug-fis_ has quit IRC14:01
ttxdhellmann: I'm looking forward to it being demonstrated in practice :)14:03
*** doug-fis_ has joined #openstack-release14:04
dhellmannheh14:06
*** daemontool has quit IRC14:09
openstackgerritMerged openstack/releases: Release os-vif 1.0.0  https://review.openstack.org/31242614:18
*** inc0 has quit IRC14:21
*** inc0 has joined #openstack-release14:21
*** amotoki has quit IRC14:23
dhellmanndims, ttx: I'm going to be traveling Friday so we should talk about whether we need a meeting or not.14:25
ttxdhellmann: ok, nothing jumps to mind, we have our N1 stuff prioritized and all14:27
dims_dhellmann : safe travels. we should be good14:28
dhellmannok, good, we can catch up monday14:28
dhellmannI'll announce that the meeting is cancelled14:28
dhellmanndims_ : I'm prepping the aodhclient release, can you remove your -2 from the constraints change? https://review.openstack.org/#/c/314822/14:31
patchbotdhellmann: patch 314822 - requirements - bump aodhclient upper-constraints to version 0.5.014:31
dims_done dhellmann14:32
*** _amrith_ is now known as amrith14:32
dhellmannthanks!14:32
openstackgerritMerged openstack/releases: python-aodhclient 0.5.0 release  https://review.openstack.org/31482114:34
*** thinrichs has joined #openstack-release14:37
*** thinrichs has quit IRC14:38
*** thinrichs has joined #openstack-release14:40
*** bdemers has joined #openstack-release14:52
*** abramley has quit IRC14:57
*** thinrichs has quit IRC14:57
*** dougshelley66 has quit IRC14:57
*** abramley has joined #openstack-release14:58
*** thinrichs has joined #openstack-release14:58
*** dougshelley66 has joined #openstack-release14:59
*** rhallisey has quit IRC14:59
*** rhallisey has joined #openstack-release14:59
*** cody-somerville has quit IRC15:00
*** Qiming has quit IRC15:02
*** sdake_ is now known as sdake15:06
dhellmannharlowja : what's up with the oslo releases in https://review.openstack.org/#/c/317111/ ? do you want those this week?15:06
patchbotdhellmann: patch 317111 - releases - Oslo releases for week of may 16th15:06
*** thinrichs has quit IRC15:08
*** amotoki has joined #openstack-release15:09
openstackgerritMerged openstack/releases: Release python-ironic-inspector-client 1.7.0 for Newton  https://review.openstack.org/31675015:11
jrolldhellmann: ^ this makes me curious when the "one liaison per project" goes into effect :P15:12
dhellmannjroll : d'oh15:12
jrollhehe, it's fine15:12
dhellmannjroll : that's not going to screw you up, is it?15:13
dhellmannok, good15:13
jrollnah, I trust dmitry for inspector things15:13
dhellmannok15:13
* dhellmann reprimands himself15:13
openstackgerritMerged openstack/reno: [Trivial] Remove executable privilege of doc/source/conf.py  https://review.openstack.org/31101015:15
*** thinrichs has joined #openstack-release15:23
*** TravT_ is now known as TravT15:25
openstackgerritIhar Hrachyshka proposed openstack/releases: networking-bgpvpn 4.0.0 (mitaka)  https://review.openstack.org/31758215:40
openstackgerritIhar Hrachyshka proposed openstack/releases: networking-bgpvpn 4.0.0 (mitaka)  https://review.openstack.org/31758215:40
*** sridhar_ram has joined #openstack-release15:46
*** thinrichs has quit IRC15:47
*** rhallisey has quit IRC15:48
*** hongbin has joined #openstack-release15:52
*** thinrichs has joined #openstack-release15:53
*** armax has joined #openstack-release15:57
openstackgerritIhar Hrachyshka proposed openstack-infra/release-tools: Added tool to reset backport-potential tags once backports are merged  https://review.openstack.org/29599315:58
*** cody-somerville has joined #openstack-release16:05
*** cody-somerville has quit IRC16:05
*** cody-somerville has joined #openstack-release16:05
*** sdague has quit IRC16:07
openstackgerritIhar Hrachyshka proposed openstack-infra/release-tools: Added tool to filter out bugs with specific tag  https://review.openstack.org/29645416:16
openstackgerritIhar Hrachyshka proposed openstack-infra/release-tools: Add tool that annotates bug numbers with details from LP  https://review.openstack.org/29647016:16
openstackgerritIhar Hrachyshka proposed openstack-infra/release-tools: Added tool to filter out bugs of specified importance  https://review.openstack.org/29642116:16
openstackgerritIhar Hrachyshka proposed openstack-infra/release-tools: Added tool to scan project repo for new bug fixes in master  https://review.openstack.org/29642016:16
*** rhallisey has joined #openstack-release16:17
notmynamettx: dhellmann: I saw some scrollback from my overnight about golang packaging/releases. anything specifically I should pay attention to?16:21
openstackgerritMaciej Szankin proposed openstack/releases: Fixed dates in releases  https://review.openstack.org/31761016:26
*** doug-fis_ has quit IRC16:28
*** hongbin_ has joined #openstack-release16:30
*** hongbin has quit IRC16:32
dhellmannnotmyname : we had a mini-meeting to discuss what changes might be needed from a release management perspective. The conclusion is that there might be a few minor tooling changes, and we want to see how the dependency management discussion plays out, but otherwise we don't expect it to be a big issue from a release management perspective.16:33
notmynameok, thanks for the summary16:33
notmyname"not a big issue" (unless we start delivering binaries) right?16:33
dhellmannyeah, if we need to package binaries in some way that'll big a bigger deal, but we didn't expect that to be a thing we started doing16:34
notmynameotherwise we've simply got a tag on a VCS repo which translates to a tarball of some text files16:34
dhellmannyeah, the bigger question for tagging was about libraries since it's not clear (a) that's a thing go developers care about or (b) how we will be managing dependencies in our build16:35
openstackgerritMerged openstack/releases: Release OpenStack-Ansible Kilo/11.2.16  https://review.openstack.org/31628116:36
notmynameis there such a thing as "things go developers care about" that is different than what any other developers care about?16:36
dhellmannnotmyname : it's not clear that go developers care about tagged versions of libraries existing16:36
dhellmannI'm far far far from an expert, though, so if I'm wrong please correct me16:36
clarkbdhellmann: some of the dep resolver tools can handle versions properly in addition to sha1s or other git refs. For those you probably do want to hvae proper version tags16:37
dhellmannok, in that case we could16:37
*** doug-fish has joined #openstack-release16:41
*** armax_ has joined #openstack-release16:52
*** armax has quit IRC16:54
*** armax_ is now known as armax16:54
harlowjadhellmann yes, just gotta do some reverts, so maybe tommorow?16:55
dhellmannharlowja : ok, just checking in16:56
*** hongbin_ has quit IRC17:01
*** hongbin has joined #openstack-release17:01
*** lucasagomes is now known as lucas-dinner17:02
*** dtantsur is now known as dtantsur|afk17:03
*** doug-fish has quit IRC17:03
*** doug-fish has joined #openstack-release17:04
openstackgerritMerged openstack/releases: remove instructions for submitting constraint update  https://review.openstack.org/31411317:07
*** doug-fis_ has joined #openstack-release17:07
*** doug-fish has quit IRC17:08
*** cody-somerville has quit IRC17:09
*** cody-somerville has joined #openstack-release17:10
*** cody-somerville has quit IRC17:10
*** cody-somerville has joined #openstack-release17:10
*** thinrichs has quit IRC17:10
*** doug-fis_ has quit IRC17:12
*** doug-fish has joined #openstack-release17:13
*** inc0 has quit IRC17:20
*** thinrichs has joined #openstack-release17:25
*** electrofelix has quit IRC17:27
*** amotoki has quit IRC17:39
*** cody-somerville has quit IRC17:56
*** ihrachys has quit IRC18:05
*** inc0 has joined #openstack-release18:12
*** kzaitsev_mb has quit IRC18:13
*** doug-fis_ has joined #openstack-release18:15
*** inc0 has quit IRC18:16
*** doug-fish has quit IRC18:18
*** inc0 has joined #openstack-release18:19
*** sridhar_ram has quit IRC18:25
*** cody-somerville has joined #openstack-release18:28
*** rhallisey has quit IRC18:35
*** rhallisey has joined #openstack-release18:36
*** rockyg has joined #openstack-release18:38
*** sdague has joined #openstack-release18:51
*** thinrichs has quit IRC18:57
*** sridhar_ram has joined #openstack-release18:59
*** doug-fis_ has quit IRC19:08
*** ihrachys has joined #openstack-release19:12
*** sdake has quit IRC19:15
*** doug-fish has joined #openstack-release19:16
*** sdake has joined #openstack-release19:20
*** sdake has quit IRC19:22
*** sdake has joined #openstack-release19:22
*** sdake has quit IRC19:23
*** sdake has joined #openstack-release19:26
*** sdake_ has joined #openstack-release19:32
*** sdake has quit IRC19:32
*** mriedem has quit IRC19:35
*** kzaitsev_mb has joined #openstack-release19:35
*** ihrachys has quit IRC19:39
*** mriedem has joined #openstack-release19:41
*** ihrachys has joined #openstack-release19:41
*** ihrachys has quit IRC19:52
*** ihrachys has joined #openstack-release19:52
*** sdake_ has quit IRC19:53
*** inc0 has quit IRC19:56
*** ihrachys has quit IRC19:57
*** sdake has joined #openstack-release19:58
*** doug-fis_ has joined #openstack-release20:00
*** doug-fi__ has joined #openstack-release20:03
*** doug-fish has quit IRC20:03
*** doug-fis_ has quit IRC20:04
*** inc0 has joined #openstack-release20:07
openstackgerritMerged openstack/releases: Fixed dates in releases  https://review.openstack.org/31761020:10
*** doug-fish has joined #openstack-release20:16
openstackgerritDoug Hellmann proposed openstack/releases: make it possible to have a series-specific yaml file for independent projects  https://review.openstack.org/31770320:17
openstackgerritDoug Hellmann proposed openstack/releases: update tag_history_from_git.py to work for newton  https://review.openstack.org/31770420:17
openstackgerritDoug Hellmann proposed openstack/releases: remove unofficial project doc8  https://review.openstack.org/31770520:17
openstackgerritDoug Hellmann proposed openstack/releases: add a tool to automate split of independent deliverable files  https://review.openstack.org/31770620:17
openstackgerritDoug Hellmann proposed openstack/releases: split doc team independent deliverables by series  https://review.openstack.org/31770720:17
openstackgerritDoug Hellmann proposed openstack/releases: split solum team independent deliverables by series  https://review.openstack.org/31770820:17
openstackgerritDoug Hellmann proposed openstack/releases: split ironic team independent deliverables into series  https://review.openstack.org/31770920:17
openstackgerritDoug Hellmann proposed openstack/releases: split magnum team independent deliverables across series  https://review.openstack.org/31771020:17
openstackgerritDoug Hellmann proposed openstack/releases: split the neutron team independent deliverables across series  https://review.openstack.org/31771120:17
openstackgerritDoug Hellmann proposed openstack/releases: split oslo team independent deliverables across series  https://review.openstack.org/31771220:17
openstackgerritDoug Hellmann proposed openstack/releases: split qa team independent deliverables across series  https://review.openstack.org/31771320:17
openstackgerritDoug Hellmann proposed openstack/releases: split the tripleo team independent deliverables across series  https://review.openstack.org/31771420:17
openstackgerritDoug Hellmann proposed openstack/releases: split the barbican team independent deliverables across series  https://review.openstack.org/31771520:17
openstackgerritDoug Hellmann proposed openstack/releases: split the telemetry team independent deliverables across series  https://review.openstack.org/31771620:17
openstackgerritDoug Hellmann proposed openstack/releases: split the cue team independent deliverables across series  https://review.openstack.org/31771720:17
openstackgerritDoug Hellmann proposed openstack/releases: split the rally team independent deliverables across series  https://review.openstack.org/31771820:17
openstackgerritDoug Hellmann proposed openstack/releases: split yaml2ical deliverable across series  https://review.openstack.org/31771920:17
openstackgerritDoug Hellmann proposed openstack/releases: split djanog-openstack-auth-kerberos independent releases across series  https://review.openstack.org/31772020:17
*** doug-fi__ has quit IRC20:18
*** kzaitsev_mb has quit IRC20:20
*** sridhar_ram has quit IRC20:32
*** sridhar_ram1 has joined #openstack-release20:32
*** thinrichs has joined #openstack-release20:34
*** kzaitsev_mb has joined #openstack-release20:36
*** rhallisey has quit IRC20:50
*** kzaitsev_mb has quit IRC20:50
*** shardy has quit IRC20:53
*** kzaitsev_mb has joined #openstack-release20:53
*** sdake_ has joined #openstack-release20:58
*** sridhar_ram1 has quit IRC21:00
*** sdake has quit IRC21:00
*** kzaitsev_mb has quit IRC21:02
*** bdemers has quit IRC21:03
*** inc0 has quit IRC21:05
*** amotoki has joined #openstack-release21:11
*** sdague has quit IRC21:14
*** daemontool has joined #openstack-release21:20
*** bobh has quit IRC21:21
*** kzaitsev_mb has joined #openstack-release21:22
*** doug-fis_ has joined #openstack-release21:22
*** doug-fish has quit IRC21:23
*** kzaitsev_mb has quit IRC21:28
*** kzaitsev_mb has joined #openstack-release21:33
stevemardhellmann: can you confirm that i can do: https://review.openstack.org/#/c/316342/ ?21:34
patchbotstevemar: patch 316342 - keystone - reorganize mitaka release notes21:34
stevemardhellmann: and they will be properly generated in http://docs.openstack.org/releasenotes/keystone/mitaka.html21:34
*** cody-somerville has quit IRC21:36
*** doug-fish has joined #openstack-release21:40
*** kzaitsev_mb has quit IRC21:41
*** doug-fis_ has quit IRC21:42
*** kzaitsev_mb has joined #openstack-release21:43
*** kzaitsev_mb has quit IRC21:48
*** sdake_ is now known as sdake21:54
*** mriedem has quit IRC21:55
dhellmannstevemar: are those files that were deleted part of an existing release?21:55
dhellmannI don't see the preface parts in http://docs-draft.openstack.org/42/316342/1/check/gate-keystone-releasenotes/1e2f3e1//releasenotes/build/html/unreleased.html21:56
dhellmannI wonder if that's a bug in the sphinx integration though21:57
*** bobh has joined #openstack-release21:58
*** daemontool has quit IRC22:03
*** doug-fish has quit IRC22:06
*** sigmavirus24 is now known as sigmavirus24_awa22:08
*** bobh has quit IRC22:12
*** rockyg has quit IRC22:19
*** thinrichs has quit IRC22:20
*** dansmith has quit IRC22:23
*** dansmith has joined #openstack-release22:23
*** dougshelley66 has quit IRC22:24
*** sridhar_ram has joined #openstack-release22:24
*** dougshelley66 has joined #openstack-release22:24
*** kzaitsev_mb has joined #openstack-release22:29
*** doug-fish has joined #openstack-release22:32
*** doug-fish has quit IRC22:36
*** doug-fish has joined #openstack-release22:39
*** doug-fish has quit IRC22:44
*** sdake_ has joined #openstack-release22:45
*** sdake has quit IRC22:48
*** kzaitsev_mb has quit IRC22:49
*** cody-somerville has joined #openstack-release22:52
*** sdake_ has quit IRC22:54
*** hongbin has quit IRC22:58
*** doug-fish has joined #openstack-release22:59
*** doug-fish has quit IRC23:03
*** kzaitsev_mb has joined #openstack-release23:09
*** gordc has quit IRC23:11
stevemardhellmann: yes, those deleted files would have been in stable/mitaka23:16
*** kzaitsev_mb has quit IRC23:17
openstackgerritJoshua Harlow proposed openstack/releases: Oslo releases for week of may 16th  https://review.openstack.org/31711123:18
*** kzaitsev_mb has joined #openstack-release23:19
openstackgerritJoshua Harlow proposed openstack/releases: Oslo releases for week of may 16th  https://review.openstack.org/31711123:19
*** sdake has joined #openstack-release23:24
*** kzaitsev_mb has quit IRC23:29
*** dansmith has quit IRC23:31
*** dansmith has joined #openstack-release23:32
*** kzaitsev_mb has joined #openstack-release23:36
*** armax_ has joined #openstack-release23:37
*** Qiming has joined #openstack-release23:39
*** armax has quit IRC23:39
*** armax_ is now known as armax23:39
*** cody-somerville has quit IRC23:43
dhellmannstevemar : ok, what's the motivation for deleting them now? that will make them not appear in the mitaka release notes any more.23:44
*** kzaitsev_mb has quit IRC23:46
*** kzaitsev_mb has joined #openstack-release23:54

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