| *** markwash has quit IRC | 04:56 | |
| *** johnthetubaguy has quit IRC | 06:05 | |
| *** jraim has quit IRC | 06:05 | |
| *** johnthetubaguy has joined #openstack-relmgr-office | 06:06 | |
| *** jraim has joined #openstack-relmgr-office | 06:06 | |
| *** markwash has joined #openstack-relmgr-office | 14:03 | |
| *** kgriffs|afk is now known as kgriffs | 14:55 | |
| ttx | #startmeeting incub_sync | 15:29 |
|---|---|---|
| openstack | Meeting started Thu Jun 5 15:29:22 2014 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:29 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:29 |
| openstack | The meeting name has been set to 'incub_sync' | 15:29 |
| ttx | jraim: around? | 15:29 |
| jraim | yep | 15:29 |
| ttx | #topic Barbican | 15:29 |
| * ttx looks up the LP pages | 15:29 | |
| ttx | jraim: when do you plan to do a juno-1 ? | 15:30 |
| ttx | in sync withe the integrated release, or when ready ? | 15:30 |
| jraim | we usually try to stay in sync | 15:31 |
| jraim | all our releases since incubation have been in sync with integration timelines | 15:31 |
| ttx | jraim: OK, juno-1 is next week, with a tag pushed to master in a window going from Tuesday to Thursday | 15:31 |
| jraim | for the havana release, there was a wiki page with the dates on it...do we have one for Juno? | 15:32 |
| ttx | We abandoned the concept of creating a branch for dev milestones | 15:32 |
| ttx | (no more milestone-proposed) | 15:32 |
| jraim | ahh, okay | 15:32 |
| ttx | https://wiki.openstack.org/wiki/Juno_Release_Schedule* | 15:32 |
| ttx | err | 15:32 |
| ttx | #link https://wiki.openstack.org/wiki/Juno_Release_Schedule | 15:32 |
| jraim | perfect, thanks | 15:32 |
| ttx | so just let me know when you want to apply the tag and which SHA you want the tag applied to | 15:33 |
| jraim | will do | 15:33 |
| ttx | not necessarily between Tue and Thu, your call | 15:33 |
| jraim | we have some PRs circling that I want to get the status of, then we should know | 15:33 |
| ttx | I think I saw you were using a barbican-specs repo ? | 15:33 |
| jraim | the PR is in to infra, just waiting for the final approvals | 15:33 |
| ttx | ok | 15:33 |
| ttx | jraim: is https://launchpad.net/barbican/+milestone/juno-1 up to date with your j-1 goals ? | 15:34 |
| jraim | its close, but we're planning a cleanup once the barbican-specs stuff lands | 15:34 |
| ttx | jraim: NB: you generally want to set a priority to any blueprint you add there. | 15:34 |
| ttx | The idea being we plan to use the -specs repo as the entry point for new feature, rather than encourage people to file BPs | 15:35 |
| jraim | I'll make sure they are all filled out during the clean up | 15:35 |
| jraim | yep, we're excited about the -specs approach | 15:35 |
| ttx | so the milestone page serves as a communication tool and should be controlled by the project drivers | 15:35 |
| ttx | but since LP lets anyone set target milestones, we use the priority field to check it's blessed | 15:36 |
| jraim | are there understood meanings for the various statuses? | 15:36 |
| ttx | I even have an autokick script that will remove BPs from milestones if they aren't prioritized | 15:36 |
| ttx | yes, see https://wiki.openstack.org/wiki/Blueprints | 15:36 |
| ttx | might be outdated with all the -specs approach though | 15:37 |
| jraim | understood | 15:37 |
| ttx | Priority and Implementation fields are what you should maintain | 15:37 |
| ttx | and their meaning is still current | 15:37 |
| jraim | okay | 15:37 |
| ttx | #action ttx to check https://wiki.openstack.org/wiki/Blueprints for validity in -specs world | 15:38 |
| ttx | so yeah, on https://launchpad.net/barbican/+milestone/juno-1 you should fix the "undefined" and the "unknown" | 15:38 |
| ttx | jraim: other questions ? | 15:39 |
| jraim | just one about integation | 15:39 |
| jraim | we got a lot of questions about it at the Summit | 15:39 |
| ttx | jraim: want me to create the other milestones in LP with due dates matching the integrated release ? | 15:39 |
| ttx | jraim: sure ask | 15:39 |
| jraim | sure, if you want that would be helpful | 15:39 |
| jraim | I wasn't orignally planning on trying for integration this cycle | 15:39 |
| ttx | #action ttx to create barbican milestones | 15:39 |
| ttx | I have a script for that, so fast | 15:39 |
| jraim | what would be your thoughts on us attempting that? | 15:40 |
| jraim | any minefields you see? I don't want to waste the team and TC's time if we think there isn't a high chance | 15:40 |
| ttx | jraim: you mean, graduate within this cycle ? | 15:40 |
| jraim | yes | 15:40 |
| ttx | in all cases you can't be "integrated in Juno release" since the Juno contents are decided before the cycle starts | 15:41 |
| ttx | but you can aim for graduation at the end of Juno to be part of K release | 15:41 |
| jraim | okay, that seems reasonable | 15:41 |
| ttx | and I think it is reasonable | 15:41 |
| jraim | most of the questions were just about wanting us to be integrated before people started deployment work | 15:41 |
| jraim | okay, i'll start reviewing the requirements and see where we are with an aim to asking late in the cycle for K | 15:41 |
| ttx | the release lags behind the dev cycles anyway | 15:42 |
| ttx | OK, talk to you next week, tehn | 15:42 |
| ttx | kgriffs: around? | 15:42 |
| jraim | awesome, thanks | 15:42 |
| *** devananda has joined #openstack-relmgr-office | 15:42 | |
| kgriffs | o/ | 15:42 |
| ttx | #topic Marconi | 15:43 |
| ttx | kgriffs: o/ | 15:43 |
| kgriffs | howdy | 15:43 |
| ttx | kgriffs: planning to tag juno-1 next week ? Or some other time ? | 15:43 |
| ttx | #info Barbican planning to do juno-1 in sync with Juno release cycle | 15:44 |
| kgriffs | yep. I'd like to continue getting the team comfortable with the cadence of the integrated projects | 15:44 |
| ttx | #info Marconi planning to do juno-1 in sync with Juno release cycle | 15:44 |
| ttx | kgriffs: ok, so the new process is just a tag on master, based on a SHA you provide | 15:45 |
| kgriffs | ah, ok | 15:45 |
| ttx | as we dropped usage of a release branch for lowly milestones | 15:45 |
| ttx | nobody backported anything to them anyway | 15:45 |
| kgriffs | so I just send you the SHA when we are ready to go? | 15:45 |
| kgriffs | ttx: makes sense | 15:45 |
| ttx | kgriffs: yes | 15:45 |
| ttx | kgriffs: milestoens are not really important anyway... all commits should work ;) | 15:46 |
| kgriffs | do you prefer IRC or an email or? | 15:46 |
| ttx | but you can implement a soft freeze to slow down crazy patches while you try to get a working SHA | 15:46 |
| kgriffs | ttx: heh, gotchya | 15:46 |
| ttx | kgriffs: IRC or email | 15:46 |
| kgriffs | kk | 15:46 |
| ttx | https://launchpad.net/marconi/+milestone/juno-1 looks good | 15:46 |
| ttx | expect maybe that essential task which is not started | 15:46 |
| kgriffs | yeah... I was just following up with the team on that to see what is going on there | 15:47 |
| kgriffs | I suspect it will get bumped to j-2 | 15:47 |
| ttx | kgriffs: want me to create all the Juno milestones with dates matching the release schedule ? | 15:47 |
| kgriffs | it really is essential then, because v1.1 of the api requires it | 15:47 |
| ttx | I'll run the same script as Barbican | 15:47 |
| kgriffs | ttx: that would be awesome! | 15:48 |
| ttx | #action ttx to create marconi milestones | 15:48 |
| kgriffs | btw, I came across a reference on the wiki to a "future" series | 15:48 |
| ttx | it might fail miserably due to Launchpad ACL but then I'll ping you to add me :) | 15:48 |
| kgriffs | kk | 15:48 |
| ttx | kgriffs: yes, it's a way to categorize future work | 15:48 |
| ttx | I can create that too | 15:48 |
| ttx | #action ttx to create future series for Marconi | 15:48 |
| kgriffs | so, what goes in future vs., say j-2 or j-3 ? | 15:49 |
| ttx | jraim: let me know if you want it as well | 15:49 |
| ttx | things that are pushed back to next cycle. useful around feature freeze | 15:49 |
| ttx | "future" series has "next" and "ongoing" milestones | 15:49 |
| jraim | jraim: that's fine with me | 15:49 |
| jraim | ha | 15:50 |
| kgriffs | ah, ok. makes sense. I could definitely have used that for the Juno freeze. It will be handy for next time. | 15:50 |
| jraim | ttx: that's fine with me | 15:50 |
| ttx | next is for "not in this cycle" | 15:50 |
| ttx | "ongoing" is for work that is never really finished | 15:50 |
| ttx | like "increase coverage" | 15:50 |
| ttx | that avoids to push it back milestone to milestone | 15:50 |
| ttx | #action ttx to create barbican future series too | 15:50 |
| kgriffs | makes sense | 15:51 |
| ttx | kgriffs: ok, anything else ? | 15:51 |
| ttx | we can keep some questions for next week :) | 15:51 |
| kgriffs | just a quick note that we are putting the finishing touches on our tempest tests and will be making that gate voting ASAP | 15:51 |
| ttx | kgriffs: great news! | 15:51 |
| ttx | #info Marconi are putting the finishing touches on our tempest tests and will be making that gate voting ASAP | 15:51 |
| kgriffs | also, py3k compat is coming along nicely. We have an intern doing great work there. | 15:52 |
| ttx | feel free to use the #info tag yourself | 15:52 |
| ttx | so that it appears in the automated summary | 15:52 |
| kgriffs | #info py3k compat is coming along nicely. We have an intern doing great work there. | 15:52 |
| ttx | here you go :) | 15:52 |
| kgriffs | ttx: thanks for the reminder! | 15:52 |
| ttx | devananda: around ? | 15:52 |
| ttx | kgriffs: np! | 15:52 |
| devananda | ttx: o/ | 15:53 |
| ttx | #topic Ironic | 15:54 |
| ttx | devananda: looks like you have your milestones and series already set | 15:54 |
| ttx | So... juno-1 sometimes next week ? | 15:54 |
| devananda | ttx: i think you created them for us a while back | 15:54 |
| devananda | fwiw, we've drunk the specs coolaid, and pushed all our BPs back, and are focusing on clean up right now | 15:54 |
| ttx | As I told the others, we dumped the milestone-proposed-based process to do a simple tag for juno-1 | 15:55 |
| ttx | on master | 15:55 |
| devananda | aiming to merge the nova.virt.ironic driver into nova by j2, as opposed to adding more features | 15:55 |
| devananda | ah, that's convenient | 15:55 |
| ttx | so just gove me a SHA for it when you want it tagged | 15:55 |
| ttx | give* | 15:55 |
| devananda | we probably wont have any new features in j1 -- just lots of bug fixes | 15:55 |
| devananda | that's why no BPs are targeted to it right now | 15:56 |
| ttx | that's what your juno-1 page says, for sure :) | 15:56 |
| devananda | several specs are in flight and aiming for j2 / j3 | 15:56 |
| ttx | devananda: heard of my autokick script ? I told jraim about it | 15:56 |
| ttx | it may be used to enforce LP missing consistency | 15:56 |
| devananda | ttx: nope | 15:56 |
| devananda | sounds interesting | 15:57 |
| ttx | i.e. make sure people don't pollute your milestoen pages by adding random stuff to it | 15:57 |
| devananda | kicks anything missing an approved spec? | 15:57 |
| ttx | .. not quite | 15:57 |
| ttx | but removed BPs that are in the milestone page that don't have a priority | 15:57 |
| devananda | ah, cool | 15:57 |
| ttx | priority is a field only drivers can set | 15:57 |
| devananda | i kicked one of those manually today | 15:57 |
| ttx | so it shows you blessed it | 15:57 |
| ttx | everythign else can be autokicked | 15:58 |
| devananda | ++ | 15:58 |
| ttx | so that we can truly use this page as a communication tool | 15:58 |
| devananda | link? | 15:58 |
| ttx | rather than as a wall where everyone writes | 15:58 |
| *** zaneb has quit IRC | 15:58 | |
| ttx | devananda: no link yet | 15:58 |
| ttx | it will replace the script that I run to adjust series goal automatically every 2 hours | 15:59 |
| ttx | new one will adjust series goals AND autokick blueprints for projects using -specs | 15:59 |
| ttx | #info ironic using specs | 15:59 |
| devananda | ah, gotcha. sounds good -- i know many folks look at the LP/blueprint status as a guidepost, so keeping it cleaner is important | 15:59 |
| ttx | kgriffs: btw, is marconi planning to use specs (or already using them) ? | 15:59 |
| ttx | devananda: the tradeoff being, you need to prioritize BPs you put there | 16:00 |
| devananda | it's probably not news to anyone, but like most projects, we're short on review (and specs review) bandwidth | 16:00 |
| ttx | devananda: fwiw I also work on a spec2bp script that will file BPs in LP for specs you approve | 16:00 |
| ttx | so that you don't have that manual step | 16:00 |
| devananda | i already make a point to prioritize the BPs, though right now i'm also prioritizing unapproved ones | 16:00 |
| ttx | think: "spec2bp this-spec juno-2 high | 16:01 |
| ttx | " | 16:01 |
| devananda | ahh - that's be handy | 16:01 |
| ttx | now if the LP API will just let me do that... | 16:01 |
| *** zaneb has joined #openstack-relmgr-office | 16:01 | |
| devananda | :) | 16:02 |
| ttx | anyway, our limited time is up... did you have an urgent question? | 16:02 |
| devananda | ttx: nope! if you dont have any Q for me ... | 16:02 |
| devananda | then let's wrap. thanks much! | 16:02 |
| ttx | I have more, but that's for next week's episode. | 16:02 |
| ttx | #endmeeting | 16:02 |
| openstack | Meeting ended Thu Jun 5 16:02:33 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:02 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/incub_sync/2014/incub_sync.2014-06-05-15.29.html | 16:02 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/incub_sync/2014/incub_sync.2014-06-05-15.29.txt | 16:02 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/incub_sync/2014/incub_sync.2014-06-05-15.29.log.html | 16:02 |
| kgriffs | ttx: sorry, missed your earlier question. We have an ongoing discussion on the ML around specs. I think we may try them, but the team wants to be sure they won't become too much of a burden (get the benefits without ending up in a waterfall development process) | 16:04 |
| ttx | kgriffs: that's a valid concern | 16:05 |
| ttx | I kind of want to see how those experiments go myself :) | 16:05 |
| ttx | so far it's all shiny and exceiting, but I fear the additional review burden will create long-term pain | 16:05 |
| kgriffs | I *really* like the idea of using them to triage new features, if nothing else | 16:05 |
| kgriffs | it would add some much-needed structure to triaging | 16:06 |
| ttx | jraim: so... I don't have the LP rights on barbican. Could you set "openstack-admins" as the maintainer of the project at https://launchpad.net/barbican ? | 16:06 |
| kgriffs | ttx: anyway, like I said, we will probably give them a try but also write down some guidelines of how we want to use them to avoid them becoming too burdensome | 16:07 |
| ttx | (you cna leave barbican-core" as driver which will let you retain all rigths | 16:07 |
| ttx | kgriffs: ok, future series created and juno milestones set | 16:09 |
| kgriffs | cool, thanks man. | 16:11 |
| *** zaneb has quit IRC | 16:13 | |
| *** zaneb has joined #openstack-relmgr-office | 16:16 | |
| jraim | ttx: done | 16:38 |
| *** markwash_ has joined #openstack-relmgr-office | 17:05 | |
| *** markwash has quit IRC | 17:09 | |
| *** markwash_ is now known as markwash | 17:09 | |
| *** zaneb has quit IRC | 17:14 | |
| *** zaneb has joined #openstack-relmgr-office | 17:18 | |
| *** SlickNik has quit IRC | 17:45 | |
| *** SlickNik has joined #openstack-relmgr-office | 17:46 | |
| *** markmcclain has joined #openstack-relmgr-office | 17:52 | |
| *** kgriffs is now known as kgriffs|afk | 18:12 | |
| *** markmcclain has quit IRC | 18:24 | |
| *** stevebaker has quit IRC | 19:15 | |
| *** stevebaker has joined #openstack-relmgr-office | 19:15 | |
| *** markwash has quit IRC | 20:04 | |
| *** devananda has quit IRC | 20:19 | |
| *** stevebaker has quit IRC | 21:00 | |
| *** stevebaker has joined #openstack-relmgr-office | 21:00 | |
| *** markwash has joined #openstack-relmgr-office | 22:02 | |
| *** stevebaker has quit IRC | 22:03 | |
| *** stevebaker has joined #openstack-relmgr-office | 22:03 | |
| *** markwash_ has joined #openstack-relmgr-office | 22:06 | |
| *** markwash has quit IRC | 22:06 | |
| *** markwash_ is now known as markwash | 22:06 | |
| *** stevebaker has quit IRC | 22:28 | |
| *** stevebaker has joined #openstack-relmgr-office | 22:28 | |
| *** SlickNik has quit IRC | 23:28 | |
| *** SlickNik has joined #openstack-relmgr-office | 23:29 | |
| *** SlickNik has quit IRC | 23:30 | |
| *** markwash has quit IRC | 23:48 | |
| *** SlickNik has joined #openstack-relmgr-office | 23:59 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!