Wednesday, 2018-06-20

*** bobh has quit IRC00:00
*** mriedem is now known as mriedem_vacay00:03
*** yamamoto has joined #openstack-release00:48
*** yamamoto has quit IRC00:53
*** yamahata has quit IRC01:05
*** sree has quit IRC01:17
*** ricolin has joined #openstack-release01:24
*** gcb has joined #openstack-release01:28
*** bobh has joined #openstack-release01:33
*** yamamoto has joined #openstack-release01:49
*** yamamoto has quit IRC01:56
*** ekcs has quit IRC01:56
*** otherwiseguy has quit IRC01:59
*** ricolin has quit IRC02:13
*** otherwiseguy has joined #openstack-release02:14
*** ricolin has joined #openstack-release02:14
*** lifeless_ has quit IRC02:15
*** bobh has quit IRC02:17
*** ianychoi_ has quit IRC02:27
*** ianychoi has joined #openstack-release02:30
*** yamamoto has joined #openstack-release02:51
*** yamamoto has quit IRC02:57
*** ricolin_ has joined #openstack-release03:01
*** ricolin has quit IRC03:04
*** annabelleB has joined #openstack-release03:07
*** annabelleB has quit IRC03:12
*** mriedem_vacay has quit IRC03:12
*** lifeless has joined #openstack-release03:18
*** bobh has joined #openstack-release03:31
*** udesale has joined #openstack-release03:40
*** jungleboyj has quit IRC03:41
*** mnaser has quit IRC03:42
*** samueldmq has quit IRC03:43
*** gmann has quit IRC03:44
*** beisner has quit IRC03:44
*** mnaser has joined #openstack-release03:45
*** jungleboyj has joined #openstack-release03:45
*** ykarel has joined #openstack-release03:46
*** samueldmq has joined #openstack-release03:46
*** gmann has joined #openstack-release03:46
*** beisner has joined #openstack-release03:46
*** ekcs_ has quit IRC03:47
*** zhongjun_ has quit IRC03:48
*** mwhahaha has quit IRC03:48
*** robcresswell has quit IRC03:49
*** spsurya has quit IRC03:49
*** ajo has quit IRC03:49
*** ying_zuo_ has quit IRC03:49
*** portdirect has quit IRC03:50
*** johnsom has quit IRC03:50
*** jungleboyj has quit IRC03:50
*** dirk has quit IRC03:50
*** vdrok has quit IRC03:50
*** TheJulia has quit IRC03:50
*** samueldmq has quit IRC03:51
*** beisner has quit IRC03:51
*** mnaser has quit IRC03:51
*** gmann has quit IRC03:51
*** lxkong has quit IRC03:51
*** coreycb has quit IRC03:51
*** zhenguo has quit IRC03:51
*** kmalloc has quit IRC03:51
*** betherly has quit IRC03:52
*** yamamoto has joined #openstack-release03:53
*** yamamoto has quit IRC03:59
*** radeks_ has joined #openstack-release04:04
*** bobh has quit IRC04:06
*** sree has joined #openstack-release04:10
*** annabelleB has joined #openstack-release04:14
*** annabelleB has quit IRC04:19
*** openstack has joined #openstack-release04:30
*** ChanServ sets mode: +o openstack04:30
*** lifeless_ has joined #openstack-release04:54
*** yamamoto has joined #openstack-release04:55
*** lifeless has quit IRC04:55
*** yamamoto has quit IRC04:58
*** yamahata has joined #openstack-release04:58
*** yamamoto has joined #openstack-release04:59
*** zhongjun_ has joined #openstack-release05:21
*** annabelleB has joined #openstack-release05:24
*** lxkong has joined #openstack-release05:24
*** ajo has joined #openstack-release05:24
*** TheJulia has joined #openstack-release05:25
*** ekcs__ has joined #openstack-release05:26
*** mwhahaha has joined #openstack-release05:28
*** annabelleB has quit IRC05:29
*** coreycb has joined #openstack-release05:30
*** udesale_ has joined #openstack-release05:33
*** betherly_ has joined #openstack-release05:34
*** vdrok has joined #openstack-release05:35
*** udesale has quit IRC05:36
*** johnsom has joined #openstack-release05:36
*** kmalloc has joined #openstack-release05:40
*** gmann has joined #openstack-release05:40
*** radek__ has joined #openstack-release05:40
*** mnaser has joined #openstack-release05:42
*** beisner has joined #openstack-release05:45
*** armax has quit IRC05:45
*** spsurya has joined #openstack-release05:47
*** beisner has quit IRC05:51
*** mnaser has quit IRC05:51
*** mnaser has joined #openstack-release05:51
*** beisner has joined #openstack-release05:51
*** ying_zuo_ has joined #openstack-release05:53
*** robcresswell has joined #openstack-release05:53
*** ifat_afek has joined #openstack-release05:53
*** gmann has quit IRC05:55
*** beisner has quit IRC05:56
*** mnaser has quit IRC05:56
*** mwhahaha has quit IRC05:56
*** ekcs__ has quit IRC05:56
*** kmalloc has quit IRC05:56
*** coreycb has quit IRC05:57
*** zhongjun_ has quit IRC05:57
*** spsurya has quit IRC05:57
*** ying_zuo_ has quit IRC05:57
*** johnsom has quit IRC05:57
*** robcresswell has quit IRC05:58
*** ajo has quit IRC05:58
*** lxkong has quit IRC05:58
*** TheJulia has quit IRC05:58
*** betherly_ has quit IRC05:58
*** vdrok has quit IRC05:59
*** lvdombrkr has joined #openstack-release06:04
*** e0ne has joined #openstack-release06:08
*** dims has quit IRC06:09
*** dims has joined #openstack-release06:10
*** mnaser has joined #openstack-release06:10
*** beisner has joined #openstack-release06:10
*** lvdombrkr has quit IRC06:11
*** lvdombrkr has joined #openstack-release06:11
*** jtomasek has joined #openstack-release06:11
*** gmann has joined #openstack-release06:13
*** dims has quit IRC06:16
*** dims has joined #openstack-release06:17
*** zhenguo has joined #openstack-release06:19
*** samueldmq has joined #openstack-release06:19
*** vdrok has joined #openstack-release06:20
*** TheJulia has joined #openstack-release06:20
*** ekcs__ has joined #openstack-release06:21
*** portdirect has joined #openstack-release06:21
*** coreycb has joined #openstack-release06:21
*** lxkong has joined #openstack-release06:21
*** portdirect has quit IRC06:21
*** portdirect has joined #openstack-release06:21
*** coreycb has quit IRC06:22
*** coreycb has joined #openstack-release06:22
*** lxkong has quit IRC06:22
*** lxkong has joined #openstack-release06:22
*** betherly_ has joined #openstack-release06:22
*** johnsom has joined #openstack-release06:23
*** jungleboyj has joined #openstack-release06:23
*** zhongjun_ has joined #openstack-release06:23
*** kmalloc has joined #openstack-release06:23
*** ajo has joined #openstack-release06:24
*** e0ne has quit IRC06:24
*** otherwiseguy has quit IRC06:24
*** mwhahaha has joined #openstack-release06:25
*** ying_zuo_ has joined #openstack-release06:25
*** spsurya has joined #openstack-release06:26
*** robcresswell has joined #openstack-release06:26
*** otherwiseguy has joined #openstack-release06:27
*** annabelleB has joined #openstack-release06:29
*** zhenguo has quit IRC06:30
*** ykarel_ has joined #openstack-release06:33
*** dirk has joined #openstack-release06:34
*** annabelleB has quit IRC06:34
*** ykarel has quit IRC06:36
*** ykarel__ has joined #openstack-release06:42
*** ykarel_ has quit IRC06:42
*** ykarel__ is now known as ykarel06:43
*** lvdombrkr89 has joined #openstack-release06:50
*** e0ne has joined #openstack-release06:53
*** lvdombrkr has quit IRC06:53
*** armax has joined #openstack-release06:53
*** armax has quit IRC07:04
*** udesale__ has joined #openstack-release07:06
*** udesale_ has quit IRC07:09
*** alexchadin has joined #openstack-release07:17
*** amoralej|off is now known as amoralej07:21
*** dtantsur|afk is now known as dtantsur07:21
*** annabelleB has joined #openstack-release07:29
*** annabelleB has quit IRC07:35
*** lvdombrkr89 has quit IRC07:43
*** jpich has joined #openstack-release07:59
*** peereb has joined #openstack-release08:09
*** pcaruana has joined #openstack-release08:11
*** peereb has quit IRC08:14
*** peereb has joined #openstack-release08:15
*** peereb has quit IRC08:16
*** peereb has joined #openstack-release08:16
*** ykarel_ has joined #openstack-release08:17
*** peereb has quit IRC08:17
*** peereb has joined #openstack-release08:18
*** peereb has quit IRC08:19
*** peereb has joined #openstack-release08:19
*** annabelleB has joined #openstack-release08:19
*** ykarel has quit IRC08:20
*** peereb has quit IRC08:20
*** peereb has joined #openstack-release08:21
*** peereb has quit IRC08:21
*** annabelleB has quit IRC08:24
*** shardy has joined #openstack-release08:45
*** spsurya has quit IRC08:46
*** ykarel_ is now known as ykarel|lunch08:48
*** radek__ has quit IRC08:49
*** sree has quit IRC09:09
*** ifat_afek has quit IRC09:09
*** sree has joined #openstack-release09:09
*** ykarel_ has joined #openstack-release09:11
ttxI just W+1 the series, we can always roll back if that was a terrible idea09:12
*** ykarel|lunch has quit IRC09:13
*** lvdombrkr has joined #openstack-release09:15
*** annabelleB has joined #openstack-release09:16
*** lvdombrkr89 has joined #openstack-release09:18
*** lvdombrkr has quit IRC09:21
openstackgerritMerged openstack/releases master: Remove DragonFlow from aclfixer exceptions  https://review.openstack.org/57513309:23
openstackgerritMerged openstack/releases master: update validation to support eol tags  https://review.openstack.org/57546309:23
openstackgerritMerged openstack/releases master: make new-release support eol tags  https://review.openstack.org/57546409:23
openstackgerritMerged openstack/releases master: protect against errors from the hound API  https://review.openstack.org/57550809:24
openstackgerritMerged openstack/releases master: make sphinxext support eol tags  https://review.openstack.org/57554609:25
openstackgerritMerged openstack/releases master: mark tripleo deliverables for newton EOL  https://review.openstack.org/57546509:25
openstackgerritMerged openstack/releases master: add import-eol-tag subcommand to edit-deliverable  https://review.openstack.org/57573609:25
openstackgerritMerged openstack/releases master: bypass validation checks when tags exist  https://review.openstack.org/57582809:25
openstackgerritMerged openstack/releases master: allow setting tarball-base once in the repository-settings  https://review.openstack.org/57652709:25
*** lifeless_ has quit IRC09:27
*** annabelleB has quit IRC09:28
*** lifeless has joined #openstack-release09:29
*** electrofelix has joined #openstack-release09:34
*** ykarel_ has quit IRC09:35
*** ykarel_ has joined #openstack-release09:35
*** gcb has quit IRC09:41
*** gcb has joined #openstack-release09:43
*** sree has quit IRC09:43
*** alexchadin has quit IRC09:46
*** pkovar has joined #openstack-release09:52
*** radek__ has joined #openstack-release09:53
*** ykarel__ has joined #openstack-release09:59
*** ykarel_ has quit IRC10:02
*** ykarel__ is now known as ykarel10:04
*** shardy has quit IRC10:06
*** shardy has joined #openstack-release10:06
*** radeks_ has quit IRC10:10
*** yamamoto has quit IRC10:18
*** alexchadin has joined #openstack-release10:23
*** annabelleB has joined #openstack-release10:25
*** alexchadin has quit IRC10:28
*** annabelleB has quit IRC10:30
*** kumarmn has joined #openstack-release10:40
*** ifat_afek has joined #openstack-release10:45
*** kumarmn has quit IRC10:48
*** kumarmn has joined #openstack-release10:48
*** kumarmn has quit IRC10:53
*** e0ne has quit IRC10:56
*** alexchadin has joined #openstack-release11:13
*** shardy is now known as shardy_afk11:13
*** yamamoto has joined #openstack-release11:19
*** amoralej is now known as amoralej|out11:20
*** udesale__ has quit IRC11:20
*** yamamoto has quit IRC11:24
*** annabelleB has joined #openstack-release11:25
*** annabelleB has quit IRC11:29
openstackgerritMerged openstack/releases master: import newton-eol tags  https://review.openstack.org/57573711:30
*** alexchadin has quit IRC11:40
*** spsurya has joined #openstack-release11:43
*** yamamoto has joined #openstack-release11:49
openstackgerritThierry Carrez proposed openstack/releases master: aclfixer.py: Remove entry for Chef  https://review.openstack.org/57371311:56
openstackgerritThierry Carrez proposed openstack/releases master: aclfixer.py: Remove exceptions for TripleO repos  https://review.openstack.org/57372911:56
*** e0ne has joined #openstack-release11:58
*** yamamoto has quit IRC12:00
*** ajo has quit IRC12:00
*** ajo has joined #openstack-release12:01
openstackgerritThierry Carrez proposed openstack/releases master: aclfixer.py: Remove heat-cfntools from exceptions  https://review.openstack.org/57682912:01
*** annabelleB has joined #openstack-release12:02
openstackgerritThierry Carrez proposed openstack/releases master: aclfixer.py: Remove murano-apps from exceptions  https://review.openstack.org/57683112:04
*** annabelleB has quit IRC12:07
*** annabelleB has joined #openstack-release12:16
*** ykarel_ has joined #openstack-release12:17
*** ykarel has quit IRC12:19
*** annabelleB has quit IRC12:20
*** ifat_afek has quit IRC12:22
*** shardy_afk is now known as shardy12:26
*** zhongjun_ has quit IRC12:29
ttxdhellmann, smcginnis: wanted to discuss/decide how much we want to handle externally-released deliverables like Chef cookbooks or Juju Charms. Let me know when you have a minute in the upcoming 2.5 hours12:29
smcginnisI'm around.12:33
ttxok let's see when dhellmann can join12:34
*** ykarel_ is now known as ykarel12:50
*** yamamoto has joined #openstack-release12:51
*** edmondsw has joined #openstack-release12:52
dhellmanntonyb , smcginnis , ttx: yeah, I think we were ready for the eol stuff to go in12:53
smcginnisThink they're all through now.12:53
dhellmannttx, smcginnis : give me 10 minutes to make breakfast before we talk about external deliverables?12:53
smcginnisSounds good.12:54
ttxsure12:54
*** sree has joined #openstack-release12:57
* dhellmann returns, toast in hand13:01
ttxOK let me introduce the topic, it's toast-compatible13:02
smcginnisttx, dhellmann: So to recap, these things are kind of cycle-trailing, but they have different deliverable requirements than our normal packages?13:02
ttxsmcginnis: hmm, taht's not how I would present it13:02
ttxBasically, we have a bunch of things where people collaborate in an openstack project team, but where the release process is externally-managed13:03
ttxmostly because the publication of the deliverable ends up being domain-specific13:03
ttxSo the question is more, how much do we want to get involved in that13:04
ttxWe have two options13:04
smcginnisOK, seems like another way to say what I said. :)13:04
ttxWe can channel them toward openstack/releases and at least use our automation to tag/create branches13:04
ttxor we can consider them exceptions13:04
ttxPersonally I'm leaning toward the latter, after carefully considering the options13:05
ttxSince we don't publish their releases, another website/system/tooling does13:05
ttxso they do not really belong in releases.o.o13:05
ttxso they don't really belong in openstack/releases13:05
smcginnisEach one has their own unique deliverable/packaging needs, right? So it's not really too feasible for us to add handling for each specific one.13:05
dhellmannideally the publishing steps would be automated, so they're not depending on a single person's credentials somewhere13:05
ttxdhellmann: yes, and if they want to do that on openstack infrastructure, we should help them13:06
ttxbut I'm not sure there is value in forcing them to go through openstack/releases if all they need from us is the ability to create a branch13:06
dhellmannbut I agree, if we can define a class of these sorts of projects that we don't need to manage then I'm fine with leaving them on their own or at least making using the releases repo optional13:06
smcginnis++ I agree.13:07
ttxSo the remaining question is, how do we mark them as "externally-released"13:07
dhellmannI do want to somehow try to describe that class of projects, though, so we can be clear on the "boundaries"13:07
ttxFirst, obviously that should only be an option for those things that actually plug into a whole different ecosystem13:07
*** amoralej|out is now known as amoralej13:07
smcginnisThey could still use releases if they want to have the tagging and tar'ing automated, knowing they will then do something else on their own for their specific needs.13:07
ttxlike teh Charm store or the Chef $library13:07
dhellmannwe could add a page to releases.o.o using an rst file that describes the project and links to whatever hosting service they're using13:08
ttxIn particular that should definitely not be an option for main "OpenStack" deliverables13:08
ttxdhellmann: ++13:08
smcginnisdhellmann: I like that idea.13:09
ttxMy original idea was to split deliverables in projects.yaml into 3 types, but that might be a bit destructive13:09
smcginnisDid we used to have something for Puppet Forge? https://forge.puppet.com/openstack/cinder13:09
ttxdeliverables -> things that are released through releases.o.o13:09
ttxexternal-deliverables: things taht are released, but via some other mechanism13:09
dhellmannthe deliverable files are things we need to update frequently, but these don't feel like they would fit that13:09
ttxother-repos -> things that are not really deliverables, like -spec repos13:09
ttxBUT that would break a lot of existing tooling for little gain13:10
dhellmannI'm thinking we just need info like "Chef Cookbooks are available in the Kitchen at $link"13:10
ttxalthough I like the idea of haviong a single list of "other-repos" for project teams13:10
smcginnisAn external-deliverables group might be nice. They could just submit patches with their released versions and URL or instructions of where to get them, then our docs builds can pull that info in somehow to display on a separate cycle deliverable section or page.13:11
ttxdhellmann: If we end up doing a deployemnt-tool specific landing page udner openstack.org/software, that blurb could belong there as well13:11
dhellmannttx: sure. though it would be nice not to duplicate info, and just link from one to the other (in either direction)13:11
ttxsmcginnis, dhellmann: we can certainly refine the thing as we go -- my main concern is what do we do right now to mark them13:12
smcginnisOr yeah, more static pointers works well too and would be less of an exception case for their release process to have to remember to go update the releases repo for each manually processed release.13:12
dhellmannsmcginnis : I'm not even thinking of listing versions. Those hosting services have their own navigation options, so we should be able to just make a list one time and be done.13:12
ttxCurrently they are just exceptions and just appear nowhere, so anything would be an improvement really13:12
smcginnisdhellmann: That's probably more scalable.13:12
ttxi don't want to embark into a 6-month effort to properly mark them13:12
*** bobh has joined #openstack-release13:13
dhellmannlet's ask those teams to provide a blurb and link(s) to go on this page13:13
ttxJust listing them in aclfixer.py sounds like a bit too little :)13:13
smcginnisOne yaml file, deliverable, location, starting cycle, last cycle. Sphinx extension to pull that in and list external deliverables for each cycle?13:13
dhellmannafter we have 2-3 of them we can create the page and then as others come in we can add their details13:13
dhellmannsmcginnis : no, just a simple rst file13:13
ttxdhellmann: we could add them all to an "externally-released" directory under openstack/releases yes13:13
smcginnisThinking the yaml file would be a way we can have a central spot that can generate the right things for each release without one of us needing to research what's available for Stein.13:14
dhellmannsmcginnis : this data won't change though, right?13:14
smcginnisAvoiding listed (just as a theoretical example) if Charms weren't available for Rocky yet, then the yaml file wouldn't be updated to show Rocky and it wouldn't show up on the list.13:15
ttxThere might be more than the 3 we identified. The ones we identified are those that used tagging and branching. But some others just don't even use that13:15
smcginnisSince some of these may not be available for some time after the release.13:15
ttxArguably Packaging-RPM is another "externally-released"13:15
*** sree has quit IRC13:15
smcginnisThen would we want to list deb packages too?13:16
ttxsmcginnis: I would make it cycle-independent13:16
ttxsmcginnis: deb packages: not under releases.o.o13:16
smcginnisMy problem with cycle-independent is a given cycle may not have that external deliverable (yet or ever).13:16
dhellmannI thought the point of this was that we weren't going to worry about that13:16
ttxsmcginnis: sure. they use whatever cycle makes sense in their ecosystem13:16
ttxdhellmann: ++13:16
ttxCharms use their own cycle, tied to Ubuntu release cycle13:17
ttxand that's good for them13:17
smcginnisAre we talking about under https://releases.openstack.org/ or something under https://releases.openstack.org/rocky/index.html ?13:17
ttxI would do it under https://releases.openstack.org/13:18
smcginnisOK, I thought the proposal was for the latter. In that case, I think a static page with no additional information is best.13:18
ttxLike have a link to/list of "externally released deliverables" theer13:18
dhellmannwe have https://releases.openstack.org/independent.html today and I'm thinking of that as a parallel (although not the content)13:18
ttxWe could also punt completely and let the landing page I mentioned above handle it13:18
dhellmannhttps://releases.openstack.org/externally-managed.html or something13:19
smcginnisWould make sense to link it under https://releases.openstack.org/#series-independent-releases as a second bullet I think.13:19
ttxI would avoid "independent" since it's loaded13:19
smcginnisSeries-Independent Projects, Externally Projects - something along those lines.13:19
dhellmannmaybe a separate section just under that one?13:19
ttxright13:20
smcginnisAren't they also series-independent though>13:20
ttxI'm saying we could leave that up to the landing page under www.o.o/software because we are entering a grey area there13:20
ttxLike for example deb packages, which are no longer produced on our infra but arguably still close to our community. Should we really not be mentioning them at all ?13:21
smcginnisI think if we are mentioning RPMs, we should mention debs.13:21
ttxA "deployment tools" landing page could mention them and link to them13:21
smcginnisEnd consumers aren't going to know or care who is managing those.13:21
ttxa release.o.o page, not so much13:21
ttxsmcginnis: right13:21
ttxso should we really start listing the whole ecosystem under releases.o.o13:22
smcginnisIt's a good point.13:22
ttxor leave that to a more "ecosystemy" page13:22
smcginnisttx: So you are proposing getting a static page added to https://www.openstack.org/software/ to list these things instead?13:22
ttxsmcginnis: yes, we are working on one anyway13:22
ttxlisting all the options to deploy openstack13:23
ttxI don't think we'd stop at the ones developed in house13:23
smcginnisI'm good with just having that. If we aren't managing the releases, then not really under our domain.13:23
smcginnisAnd that would make them discoverable and available for consumers looking for the software under the broader page.13:23
smcginnisttx: ++13:23
ttxwe are doing it anyway. The question is whether we want to duplciate that work under releases.o.o13:24
ttxfor completion reasons...13:24
smcginnisI vote no. I think https://www.openstack.org/software/ is probably a better or more likely place for people to discover these things.13:24
ttxor of only because we will likely be able to do it faster...13:24
dhellmannI don't think we want the info duplicated, so if we're going to put it on w.o.o we could just link to it from the releases site13:24
smcginnisreleases.o.o is kind of jumping deeper into the weeds for someone that isn't aware of these things.13:25
ttxthat's fair yes13:25
ttxreleases.o.o, to me, list the releases we handle as a community'13:25
*** pkovar has quit IRC13:25
ttxopenstack.org/software is more of an informative website for those who want all options listed13:25
dhellmannthat seems like a good place to draw the line13:25
ttxOK, so how about:13:26
ttx1. We list such ACLs into the aclfixer.py exception list so that they don't trigger on our checks13:26
ttx2. We defer to a "deployment tool" landing page to point users to where those artifacts are published13:27
ttx3. We might want to somehow mark those in projects.yaml so that we know they are externally-released13:27
smcginnis+213:27
ttxin order of decreasing urgency13:28
dhellmannprojects.yaml where? in the governance repo?13:28
smcginnisAre there issues today with not having 3?13:28
ttxdhellmann: that's where we list deliverables13:28
*** pkovar has joined #openstack-release13:28
ttx(yes, in governance repo)13:28
dhellmannsmcginnis : mostly I get confused when we have "exceptions" to rules, so I'd either like a clear "classification" or some sort of indication that I can use to figure out for a given deliverable whether it's something I need to be concerned with13:29
ttx(3) is last because it's a bit of a mess to balance human readability and backward compatibility there13:29
smcginnisdhellmann: That's fair.13:29
dhellmannin this case I think "it is published to some other software archive" is probably an easy enough rule for me to keep straight :-)13:30
ttxI know how the data should be, but we'd have to change a lot of tooling that ingests projects.yaml today and assumes everything is a deliverable13:30
smcginnisOf course, this also raises the question of if we are not managing the releases and they are doing their own thing, should those repos/projects even be listed as governed in projects.yml in the first place.13:30
dhellmannttx: oh, so you're not thinking of a tag?13:30
dhellmannsmcginnis : the main point of the governance list is voting rights13:31
ttxdhellmann: let me show what I had in mind13:32
dhellmannok13:32
ttxhttp://paste.openstack.org/show/723927/13:34
ttxAssuming everything is a deliverable creates a lot of noise in that file13:34
ttxwhile for things like specs, docs, or externally-released repos it does not make a lot of sense13:35
smcginnisOr should we just add a new tag under tags: release:external13:35
ttxsmcginnis: that's really a convenience tag for us, not sure it conveys much information to anyone else13:36
dhellmannreorganizing the data would be ok. I might combine "extenally-released" into "other-repositories" but I can see having them separate. That's going to break quite a few things, though.13:36
ttxyeah, that's what I meant by balance human readability and backward compatibility there13:36
ttxThat paste is the most human-readable13:36
ttxbut also the most backward incompatible13:36
smcginnisThe benefit from using the tags is we already handle processing those. Would be easy to have a validation check to make sure that tag is not present in a release request.13:37
ttxthe tag approach gets the marking done but creates a lot of extra noise13:37
dhellmannif we put some code in the governance repo to let consumers of that file not care about the format, and released that as a library, then we could treat the library as the API instead of the data file13:37
smcginnisAnd it may be interesting information for others to know it's delivered differently than other OS deliverables.13:37
ttxsmcginnis: look at the chef YAML entry, you'd have to add the tag to 20+ repos, adding 40+lines13:37
ttxall so that you can explain that it's not us releasing it13:37
smcginnisWould we have the case where a team has some repos managed by us and some not?13:38
ttxThat's just hurting my OCD too much13:38
smcginnis:)13:38
ttxsmcginnis: yes13:38
ttxI could see that happening13:38
dhellmannas soon as we say it won't, it will13:39
ttxyeah, I see no reason why the "team" concept" would align nicely with how externally-released some of their deliverables are13:39
ttxeven if there is no example now13:40
ttxanyway, we don't need to solve (3) today13:40
smcginnisTrue13:40
dhellmannthe openstack_releasese/governance.py module would make a good start for an openstack-governance library that we could reuse for the releases and elections repos13:40
ttxyeah, been on my plate for a while to actually create an API that would let us balance file format readability and backward compat13:41
ttxI guess that's the bane of human-readable data files13:42
dhellmannheh, yeah13:43
ttxIt's all nice until someone uses them13:43
ttxOK, thanks for your input. I'll track that in a StoryBoard entry13:43
dhellmannso do you want to file storyboard stories for these things?13:43
dhellmannjinx13:43
dhellmannok13:43
smcginnisSounds like a good plan.13:44
*** ykarel has quit IRC13:44
*** ykarel has joined #openstack-release13:44
openstackgerritMerged openstack/releases master: Release keystoneauth 3.9.0  https://review.openstack.org/57663413:47
*** udesale has joined #openstack-release13:47
ttxOh, and this "ability" would be limited to things in the "deployemnt/lifecyclemanagement" bucket, + maybe the "adjacentenablers" bucket13:50
ttx(map-wise)13:50
*** annabelleB has joined #openstack-release13:51
ttxhmm, i could see SDKs in the openstack-user bucket potentially happening one day13:51
ttxbut let's not go there just yet13:51
smcginnisI was thinking about SDKs too.13:52
ttxIt's all about how much they end up touching other ecosystems, raelly13:52
smcginnisI don't want to "bless" any specific SDKs, but I do think it would be useful for folks that get to that software page to be able to discover what their options are for say Java or Go.13:52
ttxlet's keep it to deployment right now13:52
smcginnis++13:53
ttx(A SDK "landing page" is also in the works)13:53
*** bobh has quit IRC13:53
*** udesale_ has joined #openstack-release13:55
*** udesale has quit IRC13:56
*** ykarel is now known as ykarel|afk13:56
ttxOK, done @ https://storyboard.openstack.org/#!/story/200262413:57
*** pkovar has quit IRC13:57
*** annabelleB has quit IRC13:58
smcginnis👍14:01
*** annabelleB has joined #openstack-release14:13
*** mlavalle has joined #openstack-release14:13
*** ykarel|afk is now known as ykarel14:13
*** annabelleB has quit IRC14:17
openstackgerritThierry Carrez proposed openstack/releases master: aclfixer.py: Remove exceptions for TripleO repos  https://review.openstack.org/57372914:23
openstackgerritThierry Carrez proposed openstack/releases master: aclfixer.py: Remove heat-cfntools from exceptions  https://review.openstack.org/57682914:23
openstackgerritThierry Carrez proposed openstack/releases master: aclfixer.py: Remove murano-apps from exceptions  https://review.openstack.org/57683114:23
openstackgerritThierry Carrez proposed openstack/releases master: aclfixer.py: Document standing exceptions  https://review.openstack.org/57687414:23
*** gcb has quit IRC14:23
dhellmannsmcginnis , ttx: maybe the tags we need are which bucket a deliverable is in on the map?14:24
*** bobh has joined #openstack-release14:24
ttxdhellmann: yeah, we keep on circling around that... One issue is that I want the map to be opinionated and a marketing/upstream exercise, which is why we are handling it at staff-level right now14:26
ttxSo I fear that documenting it in governance would turn it into an governance issue14:27
ttxplacing us back to square 0 and being unable to produce one for 7 years14:27
smcginnisIt would be nice to automatically have that map generated.14:28
dhellmannah, yeah14:28
ttxsmcginnis: same. Turns out tuning that map is a design exercise14:28
ttxBut I can see how that conflicts long-term if we start building rules around buckets14:29
ttxSo I've been avoiding that discussion so far :)14:29
*** bobh has quit IRC14:29
ttxI'd rather have it be a thing first, rather than optimize prematurely14:29
*** annabelleB has joined #openstack-release14:30
smcginnis++14:30
ttxBut I can definitely see us documenting it in YAML somewhere14:30
ttxand at some point if we make critical decisions based on it, have some kind of TC approval on it. Or at least on the parts that affctes TC decisions14:31
ttxIn the mean time I'd like to see the map the consequence of governance and policy rather than the other way around14:31
ttxBut I'll admit the difference is subtle :)14:32
*** annabelleB has quit IRC14:35
*** annabelleB has joined #openstack-release14:37
*** sree has joined #openstack-release14:41
*** annabelleB has quit IRC14:42
*** bobh has joined #openstack-release15:00
*** sree has quit IRC15:04
*** sree has joined #openstack-release15:04
*** sree has quit IRC15:09
*** pkovar has joined #openstack-release15:13
*** annabelleB has joined #openstack-release15:14
*** armax has joined #openstack-release15:19
*** kumarmn has joined #openstack-release15:19
*** kumarmn has quit IRC15:21
openstackgerritMerged openstack/releases master: aclfixer.py: Remove exceptions for TripleO repos  https://review.openstack.org/57372915:25
*** kumarmn has joined #openstack-release15:27
*** jtomasek has quit IRC15:36
*** jtomasek has joined #openstack-release15:36
openstackgerritRico Lin proposed openstack/releases master: Release heat-translator 1.1.0  https://review.openstack.org/57689515:38
*** kumarmn has quit IRC15:38
*** lvdombrkr89 has quit IRC15:38
openstackgerritDoug Hellmann proposed openstack/releases master: cliff 2.12.1  https://review.openstack.org/57689715:52
smcginnisricolin_: Did you want me to wait for Bob to see that release?15:53
smcginnisToo late. :)15:55
dhellmannoh, sorry15:57
ricolin_smcginnis, :)15:57
ricolin_dhellmann, it's fine15:57
dhellmannsmcginnis : that cliff release will unblock the tacker team15:58
ricolin_at least like Bob to be awared of it15:58
smcginnisOK, have it open and just waiting for zuul results.15:58
*** iyamahat has joined #openstack-release15:58
*** smcginnis is now known as swampboys16:00
*** swampboys is now known as smcginnis16:01
*** jpich has quit IRC16:11
*** yamamoto has quit IRC16:12
openstackgerritMerged openstack/releases master: Release heat-translator 1.1.0  https://review.openstack.org/57689516:13
openstackgerritMerged openstack/releases master: cliff 2.12.1  https://review.openstack.org/57689716:21
*** yamamoto has joined #openstack-release16:22
*** ykarel is now known as ykarel|away16:24
*** yamamoto has quit IRC16:27
*** yamamoto has joined #openstack-release16:37
*** yamamoto has quit IRC16:41
*** ricolin_ has quit IRC16:50
*** yamamoto has joined #openstack-release16:52
*** udesale_ has quit IRC16:55
*** yamamoto has quit IRC16:56
*** yamahata has quit IRC17:02
*** e0ne has quit IRC17:04
*** bobh has quit IRC17:05
*** bobh has joined #openstack-release17:05
*** dtantsur is now known as dtantsur|afk17:06
*** iyamahat has quit IRC17:07
*** yamamoto has joined #openstack-release17:07
*** yamamoto has quit IRC17:12
*** iyamahat has joined #openstack-release17:21
*** yamamoto has joined #openstack-release17:22
*** spsurya has quit IRC17:23
*** yamahata has joined #openstack-release17:23
*** ykarel|away has quit IRC17:25
*** yamamoto has quit IRC17:27
*** amoralej is now known as amoralej|off17:27
*** ekcs has joined #openstack-release17:39
*** shardy has quit IRC17:42
*** yamamoto has joined #openstack-release17:52
*** iyamahat_ has joined #openstack-release17:54
*** iyamahat has quit IRC17:56
*** yamamoto has quit IRC17:57
*** kumarmn has joined #openstack-release17:57
*** electrofelix has quit IRC17:59
*** yamamoto has joined #openstack-release18:02
*** yamamoto has quit IRC18:02
*** radek__ has quit IRC18:05
*** e0ne has joined #openstack-release18:13
*** pkovar has quit IRC18:15
*** e0ne has quit IRC18:23
*** yamamoto has joined #openstack-release18:36
*** ianychoi has quit IRC18:36
*** e0ne has joined #openstack-release18:40
*** yamamoto has quit IRC18:41
*** yamamoto has joined #openstack-release18:51
*** yamamoto has quit IRC18:56
*** lifeless has quit IRC19:00
*** yamamoto has joined #openstack-release19:06
*** yamamoto has quit IRC19:10
*** annabelleB has quit IRC19:12
*** yamamoto has joined #openstack-release19:22
*** yamamoto has quit IRC19:26
*** yamamoto has joined #openstack-release19:37
*** Deknos has joined #openstack-release19:39
*** yamamoto has quit IRC19:43
*** lifeless has joined #openstack-release19:49
*** Deknos has quit IRC19:52
*** kumarmn has quit IRC19:57
*** kumarmn has joined #openstack-release20:28
*** kumarmn has quit IRC20:32
*** annabelleB has joined #openstack-release20:36
*** yamamoto has joined #openstack-release20:39
*** pcaruana has quit IRC20:41
*** yamamoto has quit IRC20:44
*** jtomasek has quit IRC20:46
openstackgerritLance Bragstad proposed openstack/releases master: Release python-keystoneclient 3.17.0  https://review.openstack.org/57697820:53
*** kumarmn has joined #openstack-release20:58
*** kumarmn has quit IRC21:03
*** kumarmn has joined #openstack-release21:06
*** kumarmn has quit IRC21:10
*** kumarmn has joined #openstack-release21:21
*** kumarmn has quit IRC21:26
*** kumarmn has joined #openstack-release21:36
*** e0ne has quit IRC21:36
*** kumarmn has quit IRC21:40
*** yamamoto has joined #openstack-release21:41
*** lifeless has quit IRC21:46
*** yamamoto has quit IRC21:47
*** lifeless has joined #openstack-release21:47
*** kumarmn has joined #openstack-release21:51
*** kumarmn has quit IRC21:56
*** kumarmn has joined #openstack-release22:01
*** spzala has joined #openstack-release22:04
*** spzala has quit IRC22:04
*** edmondsw has quit IRC22:07
*** edmondsw has joined #openstack-release22:10
*** edmondsw has quit IRC22:14
*** e0ne has joined #openstack-release22:14
*** e0ne has quit IRC22:15
*** mlavalle has quit IRC22:27
*** yamamoto has joined #openstack-release22:43
*** annabelleB has quit IRC22:46
*** yamamoto has quit IRC22:49
*** annabelleB has joined #openstack-release22:57
*** kumarmn has quit IRC23:00
*** bobh has quit IRC23:00
openstackgerritMerged openstack/releases master: Release python-keystoneclient 3.17.0  https://review.openstack.org/57697823:08
*** annabelleB has quit IRC23:14
*** annabelleB has joined #openstack-release23:15
*** kumarmn has joined #openstack-release23:18
*** annabelleB has quit IRC23:19
*** kumarmn has quit IRC23:20
*** kumarmn has joined #openstack-release23:20
*** armax has quit IRC23:25
*** kumarmn has quit IRC23:34
*** yamamoto has joined #openstack-release23:45
*** kumarmn has joined #openstack-release23:45
*** yamamoto has quit IRC23:50
*** armax has joined #openstack-release23:51
*** kumarmn has quit IRC23:53

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