| *** david-lyle is now known as david-lyle_afk | 03:16 | |
| *** david-ly_ has joined #openstack-relmgr-office | 04:22 | |
| *** david-lyle_afk has quit IRC | 04:25 | |
| *** david-lyle_afk has joined #openstack-relmgr-office | 04:58 | |
| *** david-ly_ has quit IRC | 04:59 | |
| *** zz_johnthetubagu is now known as johnthetubaguy | 10:10 | |
| *** asalkeld has joined #openstack-relmgr-office | 11:57 | |
| *** asalkeld has left #openstack-relmgr-office | 11:57 | |
| *** johnthetubaguy is now known as zz_johnthetubagu | 13:20 | |
| *** zz_johnthetubagu is now known as johnthetubaguy | 14:18 | |
| ttx | redrobot: around? | 16:00 |
|---|---|---|
| redrobot | ttx yep! | 16:00 |
| ttx | #startmeeting incub_sync | 16:00 |
| openstack | Meeting started Thu Dec 4 16:00:33 2014 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
| ttx | #topic Barbican | 16:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| openstack | The meeting name has been set to 'incub_sync' | 16:00 |
| ttx | We finally manage to meet :) | 16:00 |
| ttx | A few checks on the project first | 16:01 |
| ttx | https://launchpad.net/barbican/ | 16:01 |
| ttx | Teams are set up fine | 16:01 |
| redrobot | Indeed! Sorry I missed you last Thursday, slept in because of Thanksgiving. :) | 16:01 |
| ttx | Missingf the next kilo milestones | 16:01 |
| ttx | Should I create them for you ? You plan to align with the common ones, right ? | 16:01 |
| redrobot | yes, we plan to stick to the Kilo Schedule | 16:01 |
| ttx | ok, let me create them | 16:01 |
| ttx | ok set | 16:02 |
| ttx | As far as artifacts go, is there anything else to "release" at milestones apart from barbican itself ? | 16:03 |
| redrobot | thanks. no, the barbican tarball should be all that is needed | 16:03 |
| ttx | OK, I checked the tarball jobs earlier and we should be all set on that side | 16:04 |
| ttx | https://launchpad.net/barbican/+milestone/kilo-1 | 16:04 |
| ttx | Let's have a quick look at the k1 plans | 16:04 |
| ttx | As a reminder, we use the LP milestone pages to communicate what is coming | 16:04 |
| redrobot | Yes, I spent some time the last few days cleaning up the blueprints | 16:05 |
| *** david-lyle_afk is now known as david-lyle | 16:05 | |
| ttx | Are those 2 blueprints the only things that will land in k1 ? | 16:05 |
| ttx | or do you expect more ? | 16:05 |
| ttx | (if more has already landed, feel free to retroactively add implemented blueprints :) | 16:05 |
| redrobot | No, I don't expect any more BPs to land for k1. We're still reviewing BPs that came out of the summit. | 16:05 |
| ttx | alright, sounds good | 16:06 |
| redrobot | I do want to drum up bugfixes in the next couple of weeks, so I'm hoping some bugs will land. | 16:06 |
| ttx | No more questions from me. Any question on your side ? | 16:06 |
| redrobot | I was curious about where to direct TC questions? is it the openstack-tc dev list? | 16:07 |
| ttx | redrobot: depends. | 16:07 |
| redrobot | There's been questions about the integration requriements/dates etc | 16:07 |
| ttx | redrobot: if you're proposing a governance change, it can be directly proposed as code change to openstack/governance | 16:07 |
| *** bswartz has joined #openstack-relmgr-office | 16:08 | |
| ttx | redrobot: If you're proposing a landslide change, better sent it to -dev ML | 16:08 |
| ttx | redrobot: if it's just a simple question to TC members, you can use the -tc ML or the Open Discussion section of the TC meeting | 16:08 |
| redrobot | I see. | 16:08 |
| redrobot | I think that's all I have for today. | 16:09 |
| ttx | redrobot: Answer is likely to be dependent on the fate of https://review.openstack.org/#/c/138504/ though | 16:09 |
| redrobot | Yeah, I saw that discussion during the last TC meeting. | 16:09 |
| ttx | redrobot: alright then, have a good week! | 16:10 |
| redrobot | thanks you too! | 16:10 |
| ttx | bswartz: around? | 16:10 |
| bswartz | ttx: hi | 16:10 |
| ttx | #topic Manila | 16:10 |
| bswartz | you have a nice office here, ttx | 16:11 |
| bswartz | lol | 16:11 |
| ttx | So first let's do a bit of sanity check on Launchpad permissions | 16:11 |
| ttx | To match what we have for other projects you should change a few things on https://launchpad.net/manila/ | 16:11 |
| ttx | The manila-core team should be renamed manila-drivers | 16:11 |
| bswartz | wait I thought drivers and core team were 2 different groups | 16:12 |
| ttx | And you should add openstack-release to it | 16:12 |
| ttx | Yes they are. But we don't define -core in Launchpad | 16:12 |
| bswartz | ah | 16:12 |
| ttx | since -core is used for reviews, it's defined on Gerrit | 16:12 |
| bswartz | okay that makes sense | 16:12 |
| ttx | basically manila-drivers are the people allowed to play with Launchpad Manila blueprints | 16:13 |
| bswartz | so who should be in the drivers group, other than me and openstack-release? | 16:13 |
| ttx | and create stuff on those pages. | 16:13 |
| ttx | bswartz: whoever you want to delegate that not-so-funny task to, if any | 16:13 |
| ttx | for erference, manila-core is defined there: https://review.openstack.org/#/admin/groups/213,members | 16:14 |
| ttx | So the simpler is to rename the manila-core group in LP to manila-drivers and clean it up | 16:14 |
| ttx | Then you can set manila-drivers both as "Driver" and "Maintainer" of the project | 16:15 |
| ttx | otherwise we'll miss part of the necessary permissions to run the release scripts | 16:15 |
| bswartz | does openstack-infra need to be a driver? | 16:15 |
| ttx | no. But they may want to "own" that team to be able to take over | 16:15 |
| ttx | i.e. you can change the "Owner" of manila-drivers to be openstack-admins | 16:16 |
| ttx | and then you remove openstack-admins from the group itself | 16:16 |
| bswartz | openstack-infra was added to manila-core so the proposal bot could propose things | 16:16 |
| ttx | that lets them explicitely add themselves to fix things, but with an audit trail | 16:16 |
| ttx | Hmm, not sure that's needed anymore | 16:17 |
| * ttx checks other projects | 16:17 | |
| ttx | yeah, other projects don't have the infra bot in "drivers" | 16:17 |
| ttx | Once you added openstack-release to the -drivers team I'll be able to fix your milestones | 16:18 |
| bswartz | okay | 16:18 |
| bswartz | I have created the drivers group and assigned it power | 16:18 |
| ttx | bswartz: you're using different dates currently, is that on purpose ? or should I fix them to align them ? | 16:18 |
| bswartz | please fix them | 16:18 |
| *** nikhil has quit IRC | 16:18 | |
| *** dolphm has quit IRC | 16:18 | |
| *** nikhil has joined #openstack-relmgr-office | 16:18 | |
| ttx | ok, will do once you enable me | 16:19 |
| bswartz | I set up the milestones before the official dates were announced | 16:19 |
| ttx | ok, quick check on k1 | 16:19 |
| bswartz | you should be enabled now | 16:19 |
| bswartz | let me know if it's not working | 16:19 |
| ttx | should be good once I accept invite | 16:20 |
| ttx | done | 16:20 |
| ttx | yep, looks good. | 16:20 |
| ttx | so.. k1 | 16:20 |
| ttx | https://launchpad.net/manila/+milestone/kilo-1 | 16:20 |
| *** dolphm has joined #openstack-relmgr-office | 16:20 | |
| bswartz | yes | 16:20 |
| bswartz | the list of BPs needs cleaning up | 16:20 |
| ttx | Like I said to Douglas, the idea is to maintain this page to describe what's likely to come up, to the best of your prediction abilities | 16:21 |
| bswartz | we discussed that in the previous hour | 16:21 |
| ttx | It's never exact science obviously | 16:21 |
| ttx | ideally all BPs should have an assignee, a priority and an implementation status | 16:21 |
| bswartz | I have an AI to remove BPs that definitely won't happen | 16:21 |
| ttx | OK, we can review the list next week once you clean it up | 16:21 |
| bswartz | and then to track down the assignees of the remaining ones and make sure they're on track | 16:21 |
| ttx | We'll have just one week left to milestone, so that's a good moment to do that | 16:22 |
| bswartz | one week? | 16:22 |
| bswartz | I thought 2 | 16:22 |
| ttx | next week, we'll have only one week left | 16:22 |
| bswartz | https://wiki.openstack.org/wiki/Kilo_Release_Schedule | 16:22 |
| bswartz | this says 18 December | 16:22 |
| bswartz | which is 2 weeks | 16:22 |
| ttx | yes, so next week (Dec 11) we'll be one week away | 16:23 |
| bswartz | oh okay | 16:23 |
| ttx | sorry that was confusing :) | 16:23 |
| bswartz | I'm just glad I didn't tell a lie in the previous meeting | 16:23 |
| ttx | basically, reviewing the list this week to have a good list next week is good timing | 16:23 |
| bswartz | since I told everyone 2 weeks | 16:23 |
| ttx | the Wiki is always Right. | 16:23 |
| ttx | OK, that's all for today. Questions on your side ? | 16:24 |
| bswartz | nope I'm alright | 16:24 |
| ttx | alright then, have a great week! | 16:24 |
| ttx | flaper87: around? | 16:24 |
| bswartz | I still haven't dealt with the tarball thing, it's not urgent though | 16:24 |
| ttx | I think it should be working now | 16:24 |
| ttx | I checkjed and the job is definitely defined | 16:24 |
| bswartz | manila tarball should be working? | 16:24 |
| ttx | so we'll tag and pray | 16:24 |
| bswartz | okay I will follow up on that | 16:24 |
| ttx | bswartz: you already have a manila-branch-tarball building per-commit tarballs at | 16:25 |
| ttx | http://tarballs.openstack.org/manila/ | 16:25 |
| ttx | the manila-tarball job is triggered when a tag is pushed. Like around milestones | 16:25 |
| bswartz | nothing special other than making a tag? | 16:25 |
| ttx | I'll ask infra to doublecheck, but the job is defined, so should work | 16:26 |
| ttx | #action ttx to ask infra about manila-tarball | 16:26 |
| bswartz | thanks | 16:26 |
| ttx | #action ttx to fix kilo milestones for manila | 16:26 |
| ttx | np :) | 16:26 |
| ttx | flaper87: around now ? | 16:26 |
| ttx | Kiall: maybe you can go now | 16:26 |
| Kiall | Heya | 16:26 |
| ttx | #topic Designate | 16:26 |
| Kiall | I'm here.. | 16:27 |
| ttx | ok, so sanity check on the Launchpad project | 16:27 |
| Kiall | Sure - https://launchpad.net/designate/+milestone/kilo-1 | 16:27 |
| ttx | Perms set correctly. I will add the missing kilo milestones unless you tell me not to | 16:27 |
| ttx | #action ttx to create Designate kilo milestones | 16:28 |
| Kiall | Sure, go ahead :) | 16:28 |
| ttx | For release artifacts, is there anything else to "release" than designate itself ? | 16:28 |
| ttx | (around milestones) | 16:28 |
| Kiall | No, Just the designate tarball | 16:28 |
| ttx | sounds good | 16:28 |
| ttx | https://launchpad.net/designate/+milestone/kilo-1 | 16:28 |
| ttx | Looks good anyone assigned to https://blueprints.launchpad.net/designate/+spec/add-reload-config-files and https://bugs.launchpad.net/designate/+bug/1387662 yet ? | 16:29 |
| Kiall | No, no assignee for either yet - the BP is Wishlist if someone happens to do it, the bug I'll need to get someone on it | 16:30 |
| ttx | ok, makes sense | 16:30 |
| ttx | Well, this looks very much under control. Questions on your side ? | 16:30 |
| Kiall | Yep (sorry - it's long ;)) | 16:31 |
| * ttx braces himself | 16:31 | |
| Kiall | - We're working through some big enough changes, the core pieces have landed, but we're struggling to get the new stuff totally integrated, while keeping compatibility for the old stuff.. We're mostly agreed within the team that if we broke the old stuff for K1, and fixed in K2, we're happy.. Not sure what the general policy around this though | 16:32 |
| ttx | Well, I'd say that as long as you're just incubated, we don't really set expectations there | 16:33 |
| ttx | so that is fine (as long as you realize it's not something to do on "released" software) | 16:33 |
| Kiall | Okay - I'm guessing the answer is different for integrated projects then? | 16:33 |
| ttx | Well, those are "released" and are supposed to be always usable | 16:34 |
| ttx | and have drastic deprecation policies | 16:34 |
| Kiall | Ah, yes- I get you now :) | 16:34 |
| ttx | You might still want to communicate that on -dev though | 16:34 |
| ttx | to warn devs and early adopters | 16:35 |
| Kiall | Will do | 16:35 |
| ttx | Kiall: anything else ? | 16:35 |
| Kiall | Okay, that was the only Q I had for you anyway, we'll know at out next meet if we'll go the break in K1 fix in K2 or if we can find another way... | 16:35 |
| ttx | Kiall: ok | 16:35 |
| ttx | Kiall: have a great busy week then :) | 16:36 |
| ttx | flaper87: last call | 16:36 |
| Kiall | I'll try ;) | 16:36 |
| ttx | flaper87: ok, we'll sync next week... ping me if you have urgent concerns. | 16:36 |
| ttx | #endmeeting | 16:36 |
| openstack | Meeting ended Thu Dec 4 16:36:57 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:36 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/incub_sync/2014/incub_sync.2014-12-04-16.00.html | 16:37 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/incub_sync/2014/incub_sync.2014-12-04-16.00.txt | 16:37 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/incub_sync/2014/incub_sync.2014-12-04-16.00.log.html | 16:37 |
| bswartz | ttx: how would I push a "test" tag for manila that I could later delete? is there a naming convention you use for testing the release process? | 16:47 |
| ttx | bswartz: tag deletion is a bit of a pain. People may catch it in their repos... I asked infra to check, and we can rush-fix on the milestone week if their estimation was wrong | 16:48 |
| ttx | i.e. we'll test on the real thing. | 16:48 |
| bswartz | okay that works | 16:49 |
| ttx | but they will check that everything seems to be in place. | 16:49 |
| nikhil_k | ttx: hi | 16:53 |
| nikhil_k | ttx: wanted to update on k-1 BPs | 16:53 |
| nikhil_k | https://launchpad.net/glance/+milestone/kilo-1 | 16:54 |
| ttx | ack | 16:54 |
| ttx | create-glance-manage-conf is unassigned , | 16:54 |
| ttx | ? | 16:54 |
| nikhil_k | ttx: can we have a fast-track for those which do not make it? | 16:54 |
| nikhil_k | ttx: yeah, unfortunately | 16:55 |
| ttx | what do you mean, a fast-track ? | 16:55 |
| nikhil_k | am aware and know who's gunna pick it up | 16:55 |
| nikhil_k | will ask them | 16:55 |
| ttx | you can directly put them in k2 for sure | 16:55 |
| nikhil_k | ttx: is there a way we can say something very soon after k1 | 16:55 |
| nikhil_k | and much before k2? | 16:55 |
| nikhil_k | that way focus is not lost | 16:56 |
| nikhil_k | context switching avoided | 16:56 |
| ttx | I'm not sure I understand | 16:56 |
| nikhil_k | basically, if we miss a BP in k1 | 16:56 |
| ttx | generally you just move BPs from k1 to k2 when they miss the target | 16:56 |
| nikhil_k | oh ok | 16:56 |
| nikhil_k | was hoping there was a way to target a middle sub-milestonre of some srot | 16:57 |
| ttx | there is no process to follow, really, just specify what milestone it's likely to land in | 16:57 |
| ttx | oh, I see | 16:57 |
| nikhil_k | as we are likely going to have a lot of BPs after k1 into k2 | 16:57 |
| ttx | You mean, how to encourage people to land them EARLY in k2 | 16:57 |
| nikhil_k | exmaple: so, there might be a case when k1 has 7 and 5 land in master | 16:57 |
| nikhil_k | then for k2 we've another 7 planned | 16:58 |
| ttx | I guess that's more team priorities -- the BPs | 16:58 |
| ttx | err | 16:58 |
| nikhil_k | gotcha | 16:58 |
| nikhil_k | no way to do that in lp with our current setup? | 16:58 |
| ttx | we don't really communicate with a finer granularity on the lueprint page, so that people can compare projects roadmaps easily | 16:58 |
| nikhil_k | so that communication becomes easier? | 16:58 |
| nikhil_k | makes sense | 16:58 |
| ttx | but you can keep some offline list of "project priorities" and communicate it at team meetings for example | 16:59 |
| ttx | to keep track of what "was in k1 and just missed the mark" | 16:59 |
| nikhil_k | sure, will find another way :) | 16:59 |
| ttx | would be easier if damn LP supported tags for blueprints :) | 16:59 |
| nikhil_k | haha | 16:59 |
| nikhil_k | thanks for the pointer! | 17:01 |
| ttx | bswartz: so.. the tarball generation job should work once https://review.openstack.org/#/c/139113/ lands | 17:01 |
| ttx | (job was defined but not enabled on the rpre-release and release zuul pipes) | 17:02 |
| *** thingee has quit IRC | 17:10 | |
| *** thingee has joined #openstack-relmgr-office | 17:12 | |
| bswartz | ttx: it landed -- thanks | 18:02 |
| *** johnthetubaguy is now known as zz_johnthetubagu | 18:26 | |
| *** dolphm has quit IRC | 19:56 | |
| *** dolphm has joined #openstack-relmgr-office | 20:00 | |
| *** bswartz has quit IRC | 20:43 | |
| *** nikhil_k is now known as nikhil_k|afk | 21:35 | |
| *** asalkeld has joined #openstack-relmgr-office | 22:30 | |
| *** SlickNik has left #openstack-relmgr-office | 22:35 | |
| *** asalkeld has quit IRC | 23:13 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!