Friday, 2018-10-26

*** ekcs has joined #openstack-release00:51
*** diablo_rojo has quit IRC00:55
*** ekcs has quit IRC01:28
*** lbragstad has quit IRC01:49
*** lbragstad has joined #openstack-release01:49
*** ricolin_ has joined #openstack-release01:59
*** bobh has joined #openstack-release02:14
*** bobh has quit IRC03:10
*** ykarel|away has joined #openstack-release03:25
*** udesale has joined #openstack-release03:51
*** dave-mccowan has quit IRC04:14
openstackgerritJuan Antonio Osorio Robles proposed openstack/releases master: Release for stein milestone1 for TripleO
openstackgerritAkihiro Motoki proposed openstack/releases master: Neutron Stein-1 deliverables
*** evrardjp_ has joined #openstack-release05:51
*** ianw_ has joined #openstack-release05:54
*** dims_ has joined #openstack-release05:54
*** irclogbot_2 has quit IRC05:55
*** dtruong has quit IRC05:55
*** dims has quit IRC05:55
*** strigazi has quit IRC05:55
*** evrardjp has quit IRC05:55
*** cgoncalves has quit IRC05:55
*** ianw has quit IRC05:55
*** Qiming has quit IRC05:55
*** jlvillal has quit IRC05:55
*** ianw_ is now known as ianw05:55
*** ykarel|away is now known as ykarel06:10
*** aojeagarcia has joined #openstack-release06:29
*** aojea has quit IRC06:33
*** dangtrinhnt has quit IRC07:00
*** ykarel is now known as ykarel|lunch07:24
*** shardy has joined #openstack-release07:26
*** strigazi has joined #openstack-release07:26
*** bauzas is now known as bauwser07:35
*** witek has quit IRC07:35
*** evrardjp_ is now known as evrardjp07:37
*** tosky has joined #openstack-release07:46
*** jpich has joined #openstack-release08:03
*** ykarel|lunch is now known as ykarel08:42
*** witek has joined #openstack-release08:58
*** e0ne has joined #openstack-release09:16
ttxevrardjp: regarding the OSA's non-tagging of roles... you're still using branches and the releases repo, so that would likely not qualify for release:none09:32
ttxthat's why we have
evrardjpyes but we are not tagging09:32
evrardjpwe are just branching09:32
evrardjpso what would that be if not none?09:33
evrardjpwe can go for external,I don't mind09:33
evrardjpbut that didn't sound matching either09:33
ttxsure... but the concern here is to track what is under release management (the openstack/releases repo) and what is not09:33
ttxI guess I should make that clearer in the commit message09:33
ttxtagless deliverables are still "released" in that sense09:34
ttxmaybe 'release-management: none' , 'release-management: external' would make more sense09:35
*** Qiming has joined #openstack-release09:35
* ttx updates09:35
evrardjp"deliverables that are not using tags for their 'release', or that are continuously consumed (docs, specs, cookiecutters...)" are matching for OSA that's why I was confused09:35
ttxyeah, that did not take into account tagless things, let me rewrite09:36
ttxwhile I'm at it, anything in ansible that would qualify as release-management:none ?09:36
*** alexchadin has joined #openstack-release09:36
ttx    openstack-ansible-os_monasca-ui09:37
ttx    openstack-ansible-pip_lock_down09:37
ttx    openstack-ansible-os_freezer09:37
ttx    openstack-ansible-os_karbor09:37
ttx    ansible-config_template09:37
ttx    openstack-ansible-security09:37
ttxin particular those ^ appear to not be managed09:37
evrardjpso openstack-ansible-security is retired same as pip_lock_down09:37
evrardjpos_monasca-ui os_freezer and os_karbor projects were dropped by their contributor without ever getting a release. I called for the community to contribute, else they will be retired09:38
evrardjpansible-config_template is new, and may or may not be tagged in the future for consumption into, which could be external. For now it's only a master deliverable (moving target)09:39
evrardjp(it's new so no need for branching)09:39
evrardjpit's not that easy, as I don't really see how this release-management meets the existing release-styles yet.09:40
ttxadded notes to
evrardjpit's just if release-management is not None or External, then we are considering part of 'releases' therefore matches release styles?09:40
evrardjpoh Yes I saw the etherpad, and I wanted to discuss with you the state before writing. I am glad you brought it up09:41
evrardjpso my concern is ansible-config_template -- in the future we might be wanting to tag it, and it may be branched under certain circumstances (like ansible versions), but I generally think it should not follow openstack branching/releasing strategy.09:43
evrardjpin that case, I'd have done an 'independant' deliverable, but I am wondering if that should not be even a release-management: external' instead09:43
evrardjpI guess we can leave it as is for now, and should we want/need to tag, we'll see09:45
ttxif it can be handled through openstack/releases, then it would not be external09:46
ttxExternal means the Ansible team would be handling its release management09:47
ttxbecause it would not fit what we can offer, and the TC would acknowledge that it's fine in that specific case09:47
ttxLet's keep it as an open question for now09:49
ttxok, new version pushed09:52
evrardjpI also prefer going through openstack/releases, as I am more familiar with that. But it's a community experiment right out there, so we'll see how the community reacts09:52
evrardjplet me review it again then09:52
evrardjpI also think that release-management is clearer to understand09:53
evrardjpI am curious if release-management: none shouldn't be applied to retired repositories, but that's a conversation for another time.09:54
evrardjpthanks for the work there ttx09:56
ttxcould add release-management: retired09:56
evrardjpexactly :)09:57
evrardjpbut later :)09:57
ttxlike 'that repo is about to disappear, don't care too much about it'09:57
ttxwe have a couple in the standing exceptions etherpad09:57
evrardjpyeah -- I have the impression it's a better source of truth for the code in release tooling too09:57
*** electrofelix has joined #openstack-release09:58
evrardjpI mean the deliverable would be skipped quite earlier09:58
ttxyes, currently it's difficult to track outliers (things that are official but are not released)09:58
evrardjp(it's been a while I haven't checked the code I am talking about)09:58
ttxthis will make it more automatable09:59
evrardjpwell governance repo is branchless, so sometimes it's hard to track state09:59
ttxcurrently we just create skeleton files in the releases repo and pray09:59
evrardjpbut assuming we can't do releases for the past, this should be alright09:59
evrardjpI think I need to walk through the code one good time again, so I can have a view of what can be changed. I am still new here10:00
*** ricolin_ has quit IRC10:02
*** luizbag has joined #openstack-release10:05
*** dtantsur|afk is now known as dtantsur10:48
*** e0ne has quit IRC10:51
*** e0ne_ has joined #openstack-release10:52
*** alexchadin has quit IRC10:52
*** dave-mccowan has joined #openstack-release11:14
*** EmilienM is now known as EvilienM11:24
smcginnisttx: +1 to release-management: foo. I think that's more clear.11:26
*** udesale has quit IRC11:28
ttxyes, allows to avoid overloaded "release" term11:47
*** ykarel is now known as ykarel|away11:58
*** ykarel|away has quit IRC12:02
*** peschk_l has joined #openstack-release12:14
openstackgerritLuka Peschke proposed openstack/releases master: Release python-cloudkittyclient 2.1.0
*** bobh has joined #openstack-release12:26
*** e0ne_ has quit IRC12:26
*** dave-mccowan has quit IRC13:00
*** mriedem has joined #openstack-release13:19
*** e0ne has joined #openstack-release13:25
*** bnemec has joined #openstack-release13:54
*** dave-mccowan has joined #openstack-release14:11
*** dave-mccowan has quit IRC14:15
*** onovy has quit IRC14:16
openstackgerritJulia Kreger proposed openstack/releases master: Release ironic-python-agent 3.4.0
*** witek has quit IRC14:21
*** stephenfin is now known as finucannot14:22
*** celebdor has joined #openstack-release14:24
*** tosky has quit IRC14:25
*** tosky has joined #openstack-release14:29
*** armstrong has joined #openstack-release14:51
*** diablo_rojo has joined #openstack-release15:00
*** dansmith is now known as SteelyDan15:01
ttxsmcginnis: meeting?15:01
smcginnisWas just waiting for the last one to finish.15:01
*** onovy has joined #openstack-release15:31
*** zul has quit IRC15:52
smcginnisttx: Not sure how freezer-tempest-plugin was skipped, but wonder if we should get that tagged for rocky.15:57
smcginnistempest-horizon too.15:58
smcginnise0ne: Do you know why some of the xstatic repos were never released in  ?15:58
ttxrepos were never tagged15:59
e0nesmcginnis: some of them are not used in horizon16:04
e0nesmcginnis: I'll recheck the list later tonight or tomorrow morning16:04
smcginnise0ne: Are they retired or abandoned?16:04
e0neoops.. Monday morning16:04
smcginnise0ne: OK, no rush. Just wanted to point that out since you were still around.16:04
clarkbwasn't one of the concerns that we were carrying local patches of the js too?16:05
e0nee.g. xstatic-angular-ui-router was supposed to be used but we still didn't implement anything related16:06
clarkband so didn't want to publish them as if they were actual $js_lib contents?16:06
*** dtantsur is now known as dtantsur|afk16:07
e0neclarkb: we don't allow custom patches to xstatic-*. it's just a python package wrapper around JS libs16:07
* e0ne needs to heads home. be available in ~2 hours16:08
clarkbe0ne: I know but for a while we were making patches like that16:08
clarkb(there was a big long thread about it on the ml and I want to say one of the things we did in resposne was to stop publishing those particular packages?)16:09
e0neclarkb: what patches do you mean?16:09
e0neI missed that thread16:09
*** dtruong has joined #openstack-release16:10
*** e0ne has quit IRC16:10
clarkb"[openstack-dev] [horizon][xstatic]How to handle xstatic if upstream files are modified" was th thread but e0ne is gone :/16:11
clarkbit came up when that particular package had failed to release for unrelated reasons16:11
smcginnisYeah, I remember that thread.16:12
smcginnisI thought (but no actual knowledge of the matter) that they addressed the issues there by not modifying the code anymore.16:13
*** bnemec is now known as beekneemech16:13
openstackgerritCorey Bryant proposed openstack/releases master: Release ldappool 2.4.0
*** shardy has quit IRC16:20
openstackgerritCorey Bryant proposed openstack/releases master: Release ldappool 2.4.0
openstackgerritmelanie witt proposed openstack/releases master: nova: release stein
*** aojeagarcia has quit IRC16:30
*** jpich has quit IRC16:31
smcginnismelwitt: Do you have someone that needs Nova beta releases?16:33
*** dave-mccowan has joined #openstack-release16:33
melwittsmcginnis: I'm not sure, but it's what we have been doing in the past16:34
*** mriedem is now known as mriedem_away16:34
smcginnismelwitt: Would you mind waiting to see if someone asks for it?16:34
melwittsmcginnis: I guess not. why?16:35
smcginnismelwitt: Just making sure you've seen and are doing a beta release for a reason.16:35
melwittsmcginnis: I have, I thought it said beta releases are optional. so I was thinking since we don't know whether folks pick them up or not and we have always had them, that it wouldn't hurt to do it in case people out there expected it16:36
smcginnisOK, that was an unknown assumption we were hoping to get rid of by making this switch. But if you still want to we can release it.16:37
melwittif you think we should wait until someone asks, that's cool. just explaining what I was thinking when I proposed it16:37
smcginnisIt is totally up to you, but my personal preference would be to not do one unless we find an actual need for it.16:37
melwittok, I'll consult with mriedem_away and see if we can ask some operators we know if they would like a s-1 release16:39
smcginnisSounds like a good plan. Thanks!16:39
openstackgerritCorey Bryant proposed openstack/releases master: Release ldappool 2.4.0 and create stable/rocky branch
*** dave-mccowan has quit IRC16:58
*** bauwser is now known as bauzas17:01
amotokismcginnis: I am now checking the need of neutron release around stein-1 which was pointed out in the relmgt team meeting.17:01
smcginnisThanks amotoki!17:02
amotokismcginnis: I need to check the needs in detail but basically we don't need to release it now.17:02
*** ekcs has joined #openstack-release17:24
*** mlavalle has joined #openstack-release17:31
*** electrofelix has quit IRC17:32
*** ykarel|away has joined #openstack-release17:34
*** bobh has quit IRC17:36
*** lbragstad is now known as elbragstad17:37
*** celebdor has quit IRC17:51
*** armstrong has quit IRC18:10
*** mriedem_away is now known as mriedem18:28
*** e0ne has joined #openstack-release18:35
*** luizbag has quit IRC19:02
*** armax has quit IRC19:05
*** e0ne has quit IRC19:14
*** dave-mccowan has joined #openstack-release19:18
*** toabctl has quit IRC19:19
*** e0ne has joined #openstack-release19:19
*** toabctl has joined #openstack-release19:21
*** e0ne has quit IRC19:23
*** armax has joined #openstack-release20:28
openstackgerritMerged openstack/releases master: Mark Ocata as extended maintenance
*** ykarel|away has quit IRC20:34
*** ade_lee has joined #openstack-release20:41
ade_leesmcginnis, ping -- I recall there was a discussion about not having to do milestone releases anymore -- is that the case or do we  still need to do a m1?20:42
*** openstackstatus has quit IRC20:42
*** openstack has joined #openstack-release20:43
*** ChanServ sets mode: +o openstack20:43
ade_leedhellmann, ^20:44
smcginnisade_lee: That is correct. cycle-with-milestone release model deliverables are switching to cycle-with-rc, so only the RC and final releases are required.20:45
ade_leesmcginnis, ok  great. thanks!20:46
smcginnisade_lee: Here is the ML thread if you care to read through all the details -
smcginnisBut I think I've pretty much summarized the important parts. ;)20:47
ade_leesmcginnis, yup  - I remember seeing the thread - but it was billed as proposed changes -- was not sure if those were actually adopted20:48
ade_leesmcginnis, I'm certainly happy *not* to have to work. :)20:49
smcginnisade_lee: Always great when you get to stop doing things. :)20:54
openstackgerritLance Bragstad proposed openstack/releases master: Release keystone
*** mriedem has quit IRC21:52
*** armax has quit IRC21:53
*** bobh has joined #openstack-release22:28
*** ekcs has quit IRC22:54
*** armax has joined #openstack-release22:59
*** pcaruana has quit IRC23:10
*** diablo_rojo has quit IRC23:40

Generated by 2.15.3 by Marius Gedminas - find it at!