Tuesday, 2016-03-15

openstackgerritamrith proposed openstack/releases: Please tag python-troveclient v2.2.0  https://review.openstack.org/29265000:05
amrithdhellmann, I'm now working to get changes merged into the trove project so I can push up an rc1 soon.00:15
amrithfor now, python-troveclient ~ v2.2.0 (457360c69f651aea92769c9e543492d770b84595), trove-dashboard (731e005b6b14256efb25b1aea388478f6f32cbe8)00:15
amrithdhellmann ^^ thanks00:15
openstackgerritTony Breeds proposed openstack-infra/release-tools: add convenience script for finding unreleased stable branch changes  https://review.openstack.org/27027300:16
openstackgerritTony Breeds proposed openstack-infra/release-tools: Actually use the URL specific in --project-list  https://review.openstack.org/29265700:16
*** dims has joined #openstack-release00:23
openstackgerritTony Breeds proposed openstack-infra/release-tools: DNM: Add a release tool to find bugs tagged for backport  https://review.openstack.org/29266000:28
*** mordred has quit IRC00:31
*** dims has quit IRC00:32
*** mordred has joined #openstack-release00:32
*** sdake has joined #openstack-release00:55
*** dims has joined #openstack-release00:56
*** sdake has quit IRC01:10
*** yarkot_ has joined #openstack-release01:24
*** yarkot_ has quit IRC01:33
*** sridhar_ram has quit IRC01:39
*** amrith is now known as _amrith_01:49
*** rockyg has joined #openstack-release01:54
*** rockyg has quit IRC02:31
*** cody-somerville has joined #openstack-release02:35
*** dims has quit IRC02:38
*** armax has quit IRC02:38
*** armax has joined #openstack-release02:58
*** doug-fish has joined #openstack-release03:03
*** sdake has joined #openstack-release04:06
*** sdake_ has joined #openstack-release04:10
*** sdake has quit IRC04:11
*** amotoki has joined #openstack-release04:17
*** sdake_ has quit IRC04:19
*** armax has quit IRC04:20
*** armax has joined #openstack-release04:25
*** sdake has joined #openstack-release05:16
*** amotoki has quit IRC05:21
*** armax has quit IRC05:29
*** amotoki has joined #openstack-release05:31
*** sdake has quit IRC05:33
*** amotoki has quit IRC05:35
*** amotoki has joined #openstack-release05:47
*** armax has joined #openstack-release05:48
*** amotoki has quit IRC05:55
*** ihrachys has joined #openstack-release07:17
*** kzaitsev_mb_ has joined #openstack-release08:40
ttxdhellmann: https://review.openstack.org/29278109:36
ttxPre-release ACLs for stable/mitaka ^09:37
ttxfwiw I only did managed / cycle-with-milestones projects.09:38
*** sdague has joined #openstack-release10:01
*** dims has joined #openstack-release11:12
-openstackstatus- NOTICE: Gerrit is going to be restarted11:14
*** dims has quit IRC11:20
*** dims has joined #openstack-release11:21
*** dims has quit IRC11:21
*** dims has joined #openstack-release11:21
*** ihrachys has quit IRC11:31
*** ihrachys has joined #openstack-release11:32
-openstackstatus- NOTICE: Gerrit had to be restarted because was not responsive. As a consequence, some of the test results have been lost, from 08:30 UTC to 10:30 UTC approximately. Please recheck any affected jobs by this problem.11:33
*** ihrachys has quit IRC11:36
-openstackstatus- NOTICE: Gerrit had to be restarted because was not responsive. As a consequence, some of the test results have been lost, from 09:30 UTC to 11:30 UTC approximately. Please recheck any affected jobs by this problem.11:36
*** _amrith_ is now known as amrith11:54
*** ihrachys has joined #openstack-release12:07
dimsgood morning dhellmann and ttx : i've taken care of the oslo.messaging 4.5.1 release and updated the spreadsheet12:19
*** bdemers has quit IRC12:20
*** dims has quit IRC12:25
*** dims has joined #openstack-release12:26
ttxdims: awesome thx12:26
*** armax has quit IRC12:33
dimsttx : looking at TODO(s), looks like we just need ./release_from_yaml.sh and ./make_stable_branch.sh scripts. right? the ACL stuff is changing permissions in project-config?12:36
*** gordc has joined #openstack-release12:50
dhellmanndims : the oslo.messaging release request is approved but still shows as unmerged in gerrit. did that get lost in the gerrit restart?12:50
dhellmannamrith : ack, I'll take a look after breakfast12:50
dimsdhellmann : y12:50
dhellmannttx: +112:50
*** amrith is now known as _amrith_12:50
dhellmanndims : ok, I'll re W+1 it and see if that helps12:50
dhellmanndims : you did the release, right?12:51
dimsdhellmann : i tried W+1 then a recheck and then a +2...then decided to wait a bit....yes, please12:51
dimsdhellmann : y, it's on pypi12:51
dhellmanndims : ok, so we just need to get it to merge, that's good12:51
dhellmannok, the W+1 doesn't seem to have made any difference but we should give gerrit/zuul a couple of minutes probably12:53
dimsdhellmann : right12:53
*** armax has joined #openstack-release13:05
*** sdake has joined #openstack-release13:08
*** AJaeger has joined #openstack-release13:13
dhellmanndims : infra says there are still ongoing gerrit/zuul issues, and we're waiting for the rest of the team to come online to deal with them. that patch may need to sit out there for a while.13:13
dimsdhellmann : ack thanks13:13
AJaegerI have a problem to solve with you release experts13:14
dhellmanndims : though sdague did suggest rebasing against master to make sure it's clean13:14
dimsdhellmann : let me try that13:14
AJaegerThe manuals we produce use the openstackdocstheme and that one includes the name of the current release13:14
openstackgerritDavanum Srinivas (dims) proposed openstack/releases: Oslo.Messaging 4.5.1 for Mitaka  https://review.openstack.org/29253913:14
AJaegerincluding a link to the home page - see http://docs.openstack.org/admin-guide-cloud/ for example13:15
AJaegerWith last release we did a last minute release for openstackdocstheme to change the publishing13:15
AJaegerCan we do this again this time? Or do you have better suggestions?13:15
AJaegerdhellmann, dims : What do you think?13:17
dhellmannAJaeger : thinking13:17
dhellmannAJaeger : how about a configuration option defined in the theme and set in the manual repo?13:18
*** ig0r__ has joined #openstack-release13:19
dimsdhellmann : sounds logical :)13:20
AJaegerdhellmann: let me check that...13:20
*** armax has quit IRC13:21
AJaegerwe use that theme in several repos - a grep shows 16 repos using it right now13:21
dhellmannAJaeger : if you don't have a good example of how to do that, I can help find one13:21
*** ig0r_ has quit IRC13:22
AJaegerdhellmann: updating doc/source/conf.py should do it...13:22
dhellmannI meant to actually define the option as an option (variables you throw in conf.py aren't visible in templates unless they are true sphinx options)13:22
AJaegerLooking at the repos - now nova and soon barbican use it. And I don't think you want to update those last minute...13:25
dhellmannwe're talking about putting "mitaka" into the title, right?13:25
dhellmannwe can do that at the beginning of the cycle, can't we?13:25
dhellmannand we can always update the lib to change the default for the option13:26
AJaegerwe publish those guides continously13:26
dhellmannfrom master? or from branches? or both?13:26
AJaegerSo, we have three guides that are version specific, the rest gets published whenever we update it.13:26
AJaegerFrom master!13:26
AJaegerSo, the admin-guide-cloud I referenced above gets published *only* from master13:26
AJaegerand covers several releases13:26
dhellmannand you don't want that to say "mitaka" until the end of the release? that would be simplest with an in-repo option change13:27
AJaegerIt's mitaka and a link to http://docs.openstack.org/mitaka as well13:28
AJaegerSo far, we only lifted that on the release day13:28
AJaegerI'm fine doing that some days earlier - but if we change modus operandi completely, we need to rethink13:29
*** mriedem_away is now known as mriedem13:30
AJaegerWE could also change the titel from "RElease: Liberty" to something generic - and that might be more appriorate since we cover several versions.13:31
AJaegerLet me write up the situation and options in an email to openstack-docs. dhellmann, dims: Should I CC you on that one or are you subscribed?13:32
dhellmannyeah, changing the title and linking to a home that isn't version-specific seems like a good solution, too13:33
* dhellmann drop afk for a bit13:34
dimsAJaeger : i'll subscribe now13:34
dimsam on AJaeger13:36
*** sdake has quit IRC13:38
AJaegerdims: thanks - will write that email later today13:41
*** sigmavirus24_awa is now known as sigmavirus2413:45
*** kzaitsev_mb_ is now known as kzaitsev_mb13:49
*** bdemers has joined #openstack-release13:55
*** bdemers has quit IRC13:55
*** Guest41345 has quit IRC14:03
*** bdemers has joined #openstack-release14:07
*** armax has joined #openstack-release14:10
*** armax has left #openstack-release14:11
*** sdake has joined #openstack-release14:25
*** ihrachys has quit IRC14:25
*** bdemers has quit IRC14:37
*** ihrachys has joined #openstack-release14:37
kzaitsev_mbI just wanted to verify if it is safe to accept new features to master clients libraries now, that stable/mitaka is cut?14:56
-openstackstatus- NOTICE: Launchpad OpenID SSO is currently experiencing issues preventing login. The Launchpad team is working on the issue14:59
*** ChanServ changes topic to "Launchpad OpenID SSO is currently experiencing issues preventing login. The Launchpad team is working on the issue"14:59
*** bdemers has joined #openstack-release15:06
bauzasso, I have 2 questions here :-)15:18
ttxask and you shall be answered15:18
bauzas#1 (the most important) how to branch mitaka when rc1 is tagged now that we removed setup.cfg version ?15:18
bauzasusing the releases repo ?15:19
*** _amrith_ is now known as amrith15:19
ttxwe branch from rc115:19
bauzas#2 how to make sure that all milestone-related notes are squashed into one single release version as a page ?15:20
bauzasttx: okay, so the release managers ? I can't write a patch for that, right?15:20
ttx#2 I think we tested that, dhellmann can confirm15:20
ttxbauzas: yep, no patch. We automatically cut the release branch from RC115:20
bauzasokay, nice to know15:20
ttxthen the release branch becomes stable branch at release day15:20
bauzasthat, I know, I was just wondering if I was having super-powers now that we have a nice tooling for tagging milestones and rcs :p15:21
ttxnope :)15:22
*** armax has joined #openstack-release15:29
*** ChanServ changes topic to "OpenStack Release Managers office - Where weekly 1:1 sync points between release manager and PTLs happen - Logged at http://eavesdrop.openstack.org/irclogs/%23openstack-release/"15:32
-openstackstatus- NOTICE: Launchpad SSO is back to normal - happy hacking15:32
amrithhello ... could I get someone to whet the request(s) in https://review.openstack.org/#/c/292650/ and https://review.openstack.org/#/c/292652/ please.15:34
patchbotamrith: patch 292650 - releases - Please tag python-troveclient v2.2.015:34
patchbotamrith: patch 292652 - requirements - Update upper-constraints for python-troveclient v2...15:34
amrithI may be afk for a bit, but I'll be back online in a couple of hours.15:34
ttxamrith: we were waiting for infra to stop being on fire15:35
ttxwe should be able to process that now15:35
openstackgerritArmando Migliaccio proposed openstack/releases: Neutron Mitaka RC1 deliverables  https://review.openstack.org/29244515:39
*** sridhar_ram has joined #openstack-release15:43
*** amrith is now known as _amrith_15:49
*** daemontool has joined #openstack-release15:51
openstackgerritMerged openstack/releases: Oslo.Messaging 4.5.1 for Mitaka  https://review.openstack.org/29253915:58
*** _amrith_ is now known as amrith16:04
david-lyledhellmann: sorry for the delay, manila-ui release from Feb should be final for Mitaka16:05
david-lyleyou also asked about a stable branch, was that also for manila-ui or something else?16:05
amrithttx, thanks. I haven't been paying attention to the channel. now that I read the backlog, I understand. Thanks ...16:08
*** johnsom has joined #openstack-release16:10
johnsomttx Who do we need to poke to get this moving? https://review.openstack.org/#/c/290735/16:13
patchbotjohnsom: patch 290735 - governance - Update lbaas dashboard repo to be similar to octav...16:13
ttxjohnsom: such patches have to wait for a minimum of 7 days to give a chance for TC members to object to them, then they merge if nobody objected16:14
ttxso I'll process it tomorrow16:14
johnsomAh, I didn't know that.  Thanks!16:14
ttxit's our "lazy consensus" model16:15
*** armax has quit IRC16:16
*** kzaitsev_mb has quit IRC16:18
dhellmanndavid-lyle: the question about the stable branch was also manila-ui -- if you're ready, I can cut it from 2.0.016:18
david-lyledhellmann: yes, we're ready16:18
david-lylethank you16:18
dhellmanndavid-lyle : ok, I'll do that now16:19
*** amrith is now known as _amrith_16:19
dhellmanndavid-lyle : https://review.openstack.org/29302916:19
david-lyledhellmann: +A'd16:20
dhellmannttx, dims: so is CI working correctly again? it looks like the oslo.messaging patch merged16:22
dimsdhellmann : y it's back up now. i saw a revert of a job definition go by16:24
bauzasdhellmann: I think we still have a problem with reno reverts https://review.openstack.org/#/c/292290/1/releasenotes/notes/reserved-hugepages-per-nodes-f36225d5fca807e4.yaml16:29
patchbotbauzas: patch 292290 - nova - Revert "virt: reserved hugepages on compute host" (MERGED)16:29
bauzasdhellmann: that note still appears on http://docs.openstack.org/releasenotes/nova/unreleased.html#new-features16:29
bauzas(and on my local branch too)16:29
bauzasreno==1.6.0 there16:30
bauzasdhellmann: I thought it was fixed ?16:30
dhellmannbauzas : let me take a look16:31
bauzasdhellmann: thanks16:31
*** sdake_ has joined #openstack-release16:31
*** sdake has quit IRC16:34
*** kzaitsev_mb has joined #openstack-release16:44
dhellmannbauzas : it looks like I handled rename but not delete; I think I have a fix for that17:01
*** bdemers has quit IRC17:12
*** bdemers has joined #openstack-release17:13
*** openstackgerrit has quit IRC17:14
*** openstackgerrit_ is now known as openstackgerrit17:14
*** openstackgerrit has quit IRC17:15
*** openstackgerrit_ has joined #openstack-release17:15
*** openstackgerrit_ is now known as openstackgerrit17:16
*** openstackgerrit_ has joined #openstack-release17:16
*** pcaruana has quit IRC17:24
bauzasdhellmann: coolness, no worries, just wondering if we can fix that before mitaka17:26
dhellmannbauzas : I'll try. It's proving a bit trickier than I originally thought.17:26
*** pcaruana has joined #openstack-release17:36
*** mriedem1 has joined #openstack-release17:43
*** mriedem has quit IRC17:44
*** mriedem1 has quit IRC17:46
*** mriedem has joined #openstack-release17:53
*** ihrachys has quit IRC17:58
*** bdemers has quit IRC17:59
openstackgerritDoug Hellmann proposed openstack/reno: handle deleted notes properly  https://review.openstack.org/29307818:00
dhellmannbauzas : ^^18:01
dhellmannttx, dims: ^^18:01
*** bdemers has joined #openstack-release18:02
*** dims_ has joined #openstack-release18:03
*** dims has quit IRC18:03
*** kzaitsev_mb has quit IRC18:07
*** sridhar_ram1 has joined #openstack-release18:14
*** sridhar_ram has quit IRC18:14
*** flwang has quit IRC18:16
sridhar_ram1dhellmann: dims_: As you know I'm trying to get the house in order for tacker liberty before getting into mitaka release. I've couple of patchsets in the queue... https://review.openstack.org/291879 (client 0.2.1) and https://review.openstack.org/292621 (tacker 0.2.0). I'd appreciate your review on these.18:25
*** sridhar_ram1 is now known as sridhar_ram18:26
*** daemontool has quit IRC18:27
*** dims_ has quit IRC18:29
*** flwang has joined #openstack-release18:29
dhellmannsridhar_ram : I'll take a look.18:30
sridhar_ramdhellmann: thanks!18:34
*** sdake_ has quit IRC18:34
dhellmannttx, dims: we have a request from _amrith_ for a troveclient release for mitaka, which will also need a requirements bump if we're going to actually let it be used anywhere. I see heat, mistral, and rally as other consumers of that library. So far we've pushed back on projects with late requirements changes. What do you think about processing the release, but not the requirements change? Or should we hold off18:37
dhellmann on both?18:37
*** _amrith_ is now known as amrith18:49
dhellmannsridhar_ram : "git merge-base origin/master origin/stable/liberty" shows your stable/liberty branch was created at 7ae2388903fb998f467c8b57846544c6864c3c5b and not the patch you're tagging as 0.2.018:51
sridhar_ramdhellmann: sorry, will fix.. think I ended up using the hash from first stable/liberty commit18:54
dhellmannsridhar_ram : the first commit on the branch is the one where you created the branch18:54
amrithdhellmann, I just saw your question above. I'm also speaking with mriedem about a global-requirements.txt change for this.18:57
amrithspeaking with mriedem in openstack-stable.18:57
sridhar_ramdhellmann: I used "git oneline master..stable/liberty" and picked the oldest entry.. looks "merge-base" is the correct approach. Will use that going forward for the initial release18:58
dhellmannamrith : ok18:58
dhellmannsridhar_ram : ah, yeah, the log is only going to show you the changes18:58
sridhar_ramdhellmann: merge-base cmd now goes to my git cheatsheet!18:59
sridhar_ramdhellmann: fyi, I'll have an immediate follow on 0.2.1 for tacker with the latest in stable/liberty18:59
dhellmannsridhar_ram : ok, we should sort out 0.2.0 first so the validation job for the later release can see that tag for some of the checks18:59
sridhar_ramdhellmann: sure, that would explain why my local tox failed for 0.2.1 (not a descendant error)19:01
*** bnemec has quit IRC19:03
sridhar_ramdhellmann: while you are there.. I believe we need to pull stable/mitaka at some point... how much room we have to wait it out to pull that for tacker ?19:05
*** sdake has joined #openstack-release19:07
openstackgerritSridhar Ramaswamy proposed openstack/releases: Release tacker 0.2.0 for liberty  https://review.openstack.org/29262119:08
amrithdhellmann, it appears that the only change I will need in master is as described in https://review.openstack.org/#/c/292652/ and changes upper-constraints.txt.19:11
patchbotamrith: patch 292652 - requirements - Update upper-constraints for python-troveclient v2...19:11
dhellmannsridhar_ram : let's get your releases straightened out before creating any more branches19:11
dhellmannamrith : yes, but that file is frozen to avoid introducing issues into test jobs during the release candidate period19:12
*** dims has joined #openstack-release19:12
*** bnemec has joined #openstack-release19:13
*** krotscheck is now known as kro_death_by_sin19:14
amrithdhellmann, ok. will follow the conversation with ttx/dims and hopefully we'll be able to find a way to accomodate this request because the one change in 2.2.0 is in support of a capability on the backend for which there was no client support in 2.1.x. thanks.19:14
*** kro_death_by_sin is now known as kro_sinus_hell19:14
*** bnemec has quit IRC19:16
*** bnemec has joined #openstack-release19:18
*** dims has quit IRC19:18
*** sdake_ has joined #openstack-release19:21
mriedemdhellmann: amrith and i talked in stable and i'm not in favor of raising the minimum required version for troveclient in g-r on master or stable/liberty19:22
mriedemreleasing a new version of the module api support in the client is up to the release and trove team, but it doesn't sound like any minimum versions need to be updated b/c nothing is consuming this feature yet19:23
dhellmannmriedem : yeah, that wasn't even going to be an option. The only question in my mind is if we allow the constraint update.19:23
*** sdake has quit IRC19:23
dhellmannI'm reluctant to do that, either. We've not done it for feature work in other clients after the freeze.19:23
sridhar_ramdhellmann: sounds good19:25
mriedemdhellmann: given nothing needs it in mitaka, i'd nack it19:25
dhellmannmriedem : yeah, it's not clear if the trove server actually needs it (maybe for a test suite?) but if so, the patch can't have landed yet19:26
*** dims has joined #openstack-release19:26
mriedemno, i assume it's just to get the cli / python api available in the client for mitaka19:27
*** sridhar_ram has quit IRC19:28
johnsomHi.  I just released Octavia 0.8.0.  I am wondering what I need to do for the release notes page to get updated: http://docs.openstack.org/releasenotes/octavia/19:31
*** cody-somerville has quit IRC19:42
*** cody-somerville has joined #openstack-release19:43
*** dims has quit IRC19:45
dhellmannjohnsom : when we create your branch, we'll add a page for mitaka there19:46
dhellmannjohnsom : before I approve your release announcement, I want to confer with ttx about whether you can say this is "part of the mitaka series"19:47
dhellmannjohnsom : since the repo uses the release:independent tag, we wouldn't normally list it as part of mitaka19:47
johnsomOh, ok.  Hmm19:48
johnsomdhellmann What do you mean by "create your branch"?19:49
dhellmannjohnsom: the stable/mitaka branch19:49
johnsomSomeone already did that this morning19:50
dhellmannok, well then you'll need to make the appropriate update yourself, let me find you an example19:51
ttxdhellmann: I'm fine with a library bump if need be, as long as it happens before RC1 and we merge the requirements bump in affected projects19:51
johnsomOk, thanks!19:51
*** sdake_ has quit IRC19:51
dhellmannttx: ok, we said no to neutron so I wasn't sure19:51
ttxdhellmann: assuming the bump is not featureful19:52
ttxIthink we said no to neutron wmore due to FF than due to the library deadline ?19:52
dhellmannjohnsom : have a look at this series, and let me know if you have any issues creating a similar patch in your repo: https://review.openstack.org/#/q/topic:reno-mitaka19:52
dhellmannttx: yes, this is a feature release for troveclient19:52
ttxdhellmann: ah.19:53
ttxso we need some library feature freeze exception, i.e. we need the thing to bring more to the table than it causes trouble19:53
dhellmannttx: while I have you before the meeting, johnsom has an announcement for the octavia release that calls it part of the mitaka release series. Do we care about that in announcements, or just in the releases repo?19:54
ttxre troveclient Does the release request mention why we absolutely need it ?19:54
ttxdhellmann: I think it should say "the release that goes with the mitaka release"19:54
dhellmannttx: in this case it adds client support for a feature trove server has. nothing else seems to be using that feature. it's very similar to the neutron case we rejected previously, except in this case they've already landed the trove feature (I think)19:54
*** sridhar_ram has joined #openstack-release19:54
dhellmannjohnsom : can you rewrite your announcement email? ^^19:55
ttxor "the release compatible with the mitaka release"19:55
johnsomSure.  BTW, how important is the patch list?  I didn't add that last time, but can if people care.19:55
ttxit's ok to track compatibility, it's another matter to say something is part of the 6-month release cycle19:55
dhellmannjohnsom : it's generally more important for libraries than services19:56
johnsomYeah, well, this is all messy.  We applied to be part of the release cycle but got denied.  The messy part is neutron-lbaas aligns to this driver as it is the reference implementation.19:57
amrithdhellmann, yes. we have. and this was something we explicitly FFE'ed.19:57
johnsomI think that mess will all get sorted out in newton19:57
*** rockyg has joined #openstack-release19:58
dhellmannjohnsom : you were denied by the release team, or neutron?19:58
johnsomrelease team19:58
ttxdhellmann: I'm fine either way. I guess it boils down to how critical the feature is to the success of the release19:58
dhellmannamrith : ok. In the case of the client, though, you're *well* past freeze, and changing the dependencies of other projects has to be considered.19:59
ttxIt's just very late and the argument that the feature could be exposed early in the newton client is something to consider19:59
ttxsince that's the argument we served the neutron folks19:59
dhellmannyeah, though in there case they hadn't already landed the feature, iirc20:00
ttxgtg meeting20:00
bauzasdhellmann: thanks for the change, will test it locally before +1ing20:00
dhellmannbauzas : great, let me know how that goes, please20:01
johnsomdhellmann history is in the comments: https://review.openstack.org/#/c/226933/20:03
patchbotjohnsom: patch 226933 - governance - Update Octavia release model (MERGED)20:03
*** ig0r_ has joined #openstack-release20:05
*** ig0r__ has quit IRC20:06
*** dims has joined #openstack-release20:11
*** sdake has joined #openstack-release20:11
mriedemdims: as oslo PTL, this is waiting for your ack https://review.openstack.org/#/c/292044/20:20
patchbotmriedem: patch 292044 - releases - kilo: release oslo.db 1.7.420:20
mriedemdims: it's kilo20:20
dimsmriedem : +220:21
dimsmriedem : dhellmann : should we cut it this week?20:21
*** kzaitsev_mb has joined #openstack-release20:23
mriedemdims: yeah20:23
mriedemit's kilo and would unblock ceilometer on kilo20:23
dimsmriedem : ack.20:24
dimsdhellmann : want me to take care of it later today?20:24
AJaegerdhellmann, dims : Message send for openstackdocstheme as discussed earlier...20:24
dhellmanndims : sure, go for it20:25
*** sridhar_ram1 has joined #openstack-release20:29
*** bswartz has quit IRC20:29
*** sridhar_ram has quit IRC20:30
*** bswartz has joined #openstack-release20:30
*** gordc has quit IRC20:34
kzaitsev_mbhi, I just wanted to make sure, that it's ok to accept commits to client repos master branches, that add new features, not that stable/mitaka is cut, right?20:36
*** rockyg has quit IRC20:37
*** rockyg has joined #openstack-release20:38
dhellmannjohnsom : it appears the tag was changed in https://review.openstack.org/#/c/272696/20:42
patchbotdhellmann: patch 272696 - governance - neutron: Change release model for Octavia, OVN, an... (MERGED)20:42
dhellmannkzaitsev_mb : yes, if your stable branch is there it's safe. we won't be releasing anything for a while yet, though20:42
johnsomdhellmann Yeah, I just saw that.  I guess we didn't know we would be shunned for skipping a milestone release.  I wish there were notifications to the PTL when a governance change is proposed (though it could have been before my time).20:43
kzaitsev_mbgot it.20:48
dhellmannjohnsom : I don't understand the neutron situation. mestery was involved in the discussions, I thought he was the appropriate liaison and would be communicating with the subteam. If that's not how you're actually organized, I apologize for making the assumption.20:49
* mestery catches up20:49
mesteryjohnsom dhellmann: What did I do wrong?20:50
johnsomDisconnects happen.  Thank you for the sentiment.20:50
*** ihrachys has joined #openstack-release20:50
*** sdake has quit IRC20:50
dhellmannjohnsom : but in general, yes, the release model tags are meant to be an indication of what you're intending to and actually doing. so missing a milestone would mean you're not actually following that model20:50
johnsommestery We are talking about the non-mitaka thing I sent you.20:50
mesteryRight, octavia is independent20:50
dhellmannmestery : octavia is marked as release:independent, which means we would prefer they not list the project as "part of mitaka"20:50
johnsomAbout the release change to independent due to not doing an M-120:50
mesteryIt had never released with milestones20:50
mesterydhellmann: Agreed. johnsom, did I lead you astray?20:50
mesteryBecause what dhellmann says makes sense to me20:51
johnsommestery https://review.openstack.org/#/c/272696/20:51
patchbotjohnsom: patch 272696 - governance - neutron: Change release model for Octavia, OVN, an... (MERGED)20:51
mesteryjohnsom: Yes, I proposed that in fact20:52
johnsomYep.  I don't think we knew this was going to be this big of a problem.20:53
johnsomWe could have cut M1, it was bad timing with a big feature (VRRP).20:53
*** sdake has joined #openstack-release20:53
mesteryI think you could just release what you have, you just can't call it Mitaka20:54
johnsomRight, which gets very strange given it's the reference code for neutron-lbaas20:54
mesteryjohnsom: It's only strange for one release, you can change the release tag for Newton20:54
* mestery shrug20:54
johnsommestery Yep.  We need to fix this setup in newton.20:55
*** AJaeger has left #openstack-release20:57
johnsomdhellmann Do you have a link to the definitions of these release tags?  I want to bring this up with the team at our meeting tomorrow.  I think we need to understand the consequences of these and make a decision of what we want to be.20:57
dhellmannjohnsom : http://governance.openstack.org/reference/tags/index.html#release-management-tags20:58
johnsomThank you!20:58
dhellmannjohnsom : the has-stable-branches tag is likely to be deprecated, but look at stable:follows-policy instead20:58
openstackgerritFlavio Percoco proposed openstack/releases: Tag Glance Mitaka RC1  https://review.openstack.org/29313720:58
*** sridhar_ram1 has quit IRC21:01
johnsomdhellmann Will we be moved over to the new tag or is there something more we need to do?21:01
dhellmannjohnsom : I think you'll be encouraged by mriedem to apply for the new tag, since the evaluation criteria are more stringent than the existing one21:01
dhellmannthere may have already been a ML post about it?21:02
dhellmannjohnsom : yeah, I found a message in my mail archives with the subject 'The stable:follows-policy tag is official, projects need to start applying for it" from 7 March21:02
*** sdake_ has joined #openstack-release21:02
*** gordc has joined #openstack-release21:03
johnsomThanks for the heads up.  Missed that.21:04
*** sdake has quit IRC21:05
stevemardhellmann: random question for ya21:05
dhellmannstevemar : 4221:06
dhellmannstevemar : lunchbox21:06
stevemardhellmann: i know library releases are fairly frozen atm, so if we wanted a new version of keystoneauth, could we release one against newton here? https://github.com/openstack/releases/tree/master/deliverables21:06
dhellmann(let me know when one of these random answers seems to fit)21:06
stevemardhellmann: ha21:06
dhellmannstevemar : no, newton isn't open for releases yet21:07
dhellmannthe point of the release freeze is to slow down outside changes while projects test their release candidates21:07
*** bdemers has quit IRC21:08
stevemardhellmann: and releasing a new version of ksa is a no-no at this point: https://github.com/openstack/keystoneauth/compare/2.3.0...master21:08
stevemaryeah, i understand21:08
stevemarokay, we can wait21:08
dhellmannit won't be much longer21:08
stevemardhellmann: yep21:09
dhellmannstevemar : get your keystone rc1 request in, and it will be even shorter ;-)21:09
*** sdague has quit IRC21:09
stevemardhellmann: hehe21:10
stevemardhellmann: thanks for the answer21:11
dhellmannstevemar : any time21:11
johnsomdhellmann mestery Ok, so reading through those, I think the octavia team was operating under the "cycle-with-intermediary" tag.  (I realize that isn't what is listed in the projects file).21:13
dhellmannjohnsom : ok. that's a fine model to use. the expectation there would have been some sort of release prior to or around the time of the freeze last week, with the idea that you might have another this week or next if you find issues to resolve21:14
johnsomYeah, that is what we have done for liberty and now mitaka21:14
openstackgerritFlavio Percoco proposed openstack/releases: Tag Glance Mitaka RC1  https://review.openstack.org/29313721:15
johnsomI'm going to add all of this to our weekly meeting agenda.21:15
*** sdake_ is now known as sdake21:23
dhellmannjohnsom : good plan. let me know if you have other questions, I'm happy to help you make the right choice for the team.21:33
*** amrith has quit IRC21:35
*** amrith has joined #openstack-release21:35
*** pcaruana has quit IRC21:38
*** pcaruana has joined #openstack-release21:52
*** mriedem has quit IRC21:55
*** sdake has quit IRC22:09
*** rockyg has quit IRC22:10
*** dims_ has joined #openstack-release22:11
*** sigmavirus24 is now known as sigmavirus24_awa22:12
*** david-lyle has quit IRC22:13
*** dims has quit IRC22:14
dhellmannttx: we have rc1 tags for neutron and glance proposed. should we go ahead and create their stable/mitaka branches when we cut those candidates?22:15
*** gordc has quit IRC22:15
*** dims has joined #openstack-release22:16
*** dims_ has quit IRC22:17
*** dims has quit IRC23:06
*** ihrachys has quit IRC23:45
*** sdake has joined #openstack-release23:45
*** kzaitsev_mb has quit IRC23:47
*** sdake_ has joined #openstack-release23:59

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