14:04:40 <boris-42> #startmeeting Rally
14:04:40 <openstack> Meeting started Mon Aug 24 14:04:40 2015 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:04:41 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:04:44 <openstack> The meeting name has been set to 'rally'
14:04:47 <kun_huang> yep
14:04:56 <boris-42> hi hi
14:05:04 <rvasilets__> Hi
14:05:42 <skraynev> hi
14:06:01 <andreykurilin__> hi
14:07:01 <boris-42> hi hi
14:07:23 <boris-42> #topic Meeting agenda
14:07:31 <e0ne> пhi
14:07:34 <e0ne> hi
14:07:35 <boris-42> #link https://wiki.openstack.org/wiki/Meetings/Rally#Weekly_Rally_release_meeting
14:07:53 <boris-42> if somebody would like to discuss something please add it to meeting agenda
14:08:03 <boris-42> #topic [andreykurilin] The critical number of outdated patches on review.
14:09:04 <andreykurilin__> we have a lot of patches, which are almost ready, but authors are gone
14:09:58 <andreykurilin__> So I suggest to pay attention to these patches and finish them.
14:10:26 <boris-42> andreykurilin__: so maybe we should create some list
14:10:45 <boris-42> andreykurilin__: with priorities and reasons (why patch is not finished)
14:11:07 <andreykurilin__> boris-42: yes, maybe it will help
14:11:16 <boris-42> andreykurilin__: so people will know that they can just take these patches (like bug) and just finish them
14:11:19 <rvasilets__> Then we need to reassign outdated patches:-)
14:11:48 <andreykurilin__> rvasilets: just put "co-authored" to commit message
14:12:11 <andreykurilin__> Currently we have more than 150 patches on review
14:12:22 <kun_huang> yep, I did something like this before
14:12:51 <rvasilets__> Reassign means to give someone task to finish patch for example
14:13:26 <rvasilets__> For example, roma please finish patch 123456
14:13:26 <patchbot> rvasilets__: https://review.openstack.org/#/c/123456/
14:13:27 <andreykurilin__> Also, I found that several patches are already implemented by another changes, so we can abandon them
14:15:32 <andreykurilin__> rvasilets__: we can create a table at google docs with list of patches and reasons(something like "contains small nits"), so everyone will be able to find a patch to maintain and finish it
14:15:39 <boris-42> +1 for table
14:16:15 <rvasilets__> Ok
14:16:19 <rvasilets__> Good idea
14:16:26 <rvasilets__> Agree:-)
14:16:27 <andreykurilin__> boris-42: Of course you're +1 for the table. it was your suggestion:)
14:17:09 <boris-42> andreykurilin__: okay I am +2 fot the table LOL
14:17:46 <rvasilets__> Lol
14:17:54 <kun_huang> anyone prefer etherpad?
14:18:10 <rvasilets__> Nooo:-)
14:18:16 <boris-42> nooo
14:18:22 <kun_huang> =, =
14:18:23 <andreykurilin__> kun_huang: Does etherpad supports tables?
14:18:36 <kun_huang> just simple list
14:18:52 <kun_huang> google is hard blocked in china :(
14:18:58 <andreykurilin__> :(
14:19:10 <andreykurilin__> ok, we should think more about how to store such table
14:19:33 <boris-42> andreykurilin__: just excel
14:20:01 <boris-42> andreykurilin__: 1 column first line of commit message second url third reason why it's not done
14:20:17 <boris-42> andreykurilin__: I can prepare initial version of itt
14:21:15 <andreykurilin__> another question: Should we abandon changes after they will be added to the table or leave them? From one point of view: if changes will be abandoned, cores will be able to restore them and list of open reviews will contain only uptodate patches.
14:21:50 <boris-42> andreykurilin__: I don't want to abandon them
14:22:33 <andreykurilin__> boris-42: because it will require involvement from core team each time?
14:24:07 <boris-42> andreykurilin__: because we should see issues
14:24:12 <boris-42> andreykurilin__: not hide them
14:24:22 <andreykurilin__> btw, what about using wiki page for the table?
14:24:35 <andreykurilin__> boris-42, kun_huang : ^
14:25:29 <boris-42> andreykurilin__: sound good
14:26:44 <boris-42> okay next topic
14:26:53 <boris-42> stannie: hi there
14:27:03 <stannie> hi
14:27:10 <boris-42> stannie: how things are going?)
14:27:18 <stannie> fine thx :)
14:27:26 <rvasilets__> Wiki is good
14:28:25 <boris-42> ok let it be wiki
14:28:27 <boris-42> now next topic
14:28:48 <boris-42> #topic [boris-42] Updates about switching to Plugin base.
14:29:13 <boris-42> okay guys with help of MetaClasses we can do switching to plugin base in case of scenarios smoother
14:29:24 <boris-42> #link https://review.openstack.org/#/c/213631/
14:30:01 <boris-42> Like we don't need to introduce anything else from what we have now in our scenario.configure() and it will work with Plugin base
14:30:28 <boris-42> This patch finishes large amount of work that will allow us to cleanup a lot of code
14:30:29 <andreykurilin__> yes, metaclasses are nice:)
14:31:31 <boris-42> like we will be able to have @types and @validators, deprecation mechanism & info unified and one code that works with all types of plugins
14:31:39 <boris-42> less code less bugs=)
14:33:10 <boris-42> any questions?
14:33:30 <andreykurilin__> no
14:33:44 <boris-42> okay great
14:33:52 <boris-42> #topic Open discussion
14:33:58 <boris-42> anything to discuss?)
14:35:02 <andreykurilin__> next release date:) it would be nice to have release at 14 September, so we will able to return to our 2-weeks cycle
14:35:20 <andreykurilin__> boris-42: ^
14:36:05 <rvasilets__> Is it too much?)
14:36:22 <boris-42> andreykurilin__: heh sounds good=)
14:36:23 <boris-42> LOL
14:36:31 <boris-42> or we can cut it this week
14:36:57 <boris-42> because what we need is task.abort and basically this patch that switches to plugin base
14:37:00 <boris-42> rest can wait
14:37:14 <andreykurilin__> boris-42: what about new reports?
14:37:31 <boris-42> andreykurilin__: they may wait
14:37:36 <andreykurilin__> ok
14:37:55 <boris-42> andreykurilin__: in any case nothing is stoping us to review in merge them
14:38:22 <andreykurilin__> )
14:38:24 <andreykurilin__> ok
14:38:27 <andreykurilin__> nothing else from my side.
14:40:25 <boris-42> okay
14:40:30 <boris-42> let's finish this meeting
14:40:36 <boris-42> see you next week
14:40:41 <boris-42> #endmeeting