14:00:32 #startmeeting Rally 14:00:33 Meeting started Mon Jul 25 14:00:32 2016 UTC and is due to finish in 60 minutes. The chair is andreykurilin. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:34 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:36 The meeting name has been set to 'rally' 14:00:43 o/ 14:00:46 hi 14:00:49 o/ 14:00:50 o? 14:01:25 #topic Happy Birthday boris-42 14:01:29 :) 14:01:30 thanks=) 14:01:37 boris-42, happy birthday:) 14:02:32 so everybody's gone drinkin' 14:02:39 =) 14:02:40 :D 14:02:48 Wish one day to finish Rally=) 14:03:30 finishing rally is pretty easy: git push origin --delete master 14:03:32 ))) 14:03:45 Party like a ROCK STAR on your birthday) 14:04:19 ikhudoshyn: it is much easier:) 14:04:36 redixin had a patch 14:04:55 oO 14:05:25 ikhudoshyn: https://review.openstack.org/#/c/169690/ 14:06:00 ok. do we have anything else to discuss ? 14:06:04 :) 14:06:22 nothing from me 14:06:41 rvasilets had 14:06:50 #topic How to optimize sync requirements workflow 14:06:57 from agenda 14:07:33 So currently we need to manually sync our requirements with global-one 14:07:40 andreykurilin, told that we need to have such patch every time when we cut release https://review.openstack.org/#/c/345307/ 14:08:07 I suggest to think how this could be automatize 14:08:53 yes, we need to add upper limits each time before cutting release and remove them after. it is needed to use uptodated requirements 14:09:38 or to have every time requirements in sync version but before release resync it locally 14:10:05 or I forgot that we can't 14:10:10 what do you mean redync it locally? 14:10:14 *resync 14:11:11 to downgrade requirements locally 14:11:49 or to add upper constrains 14:12:28 or you need updated requirements at origin/master? 14:12:43 not local/master 14:12:54 Currently we use git tags for releases. it means that every requirements change should be done in gerrit-workflow at origin/master 14:14:09 Okey If no one have Ideas then lets keep as it was 14:16:26 maybe in future we will write own "openstack proposal bot" which will take care about all requirements suff(syncing with g-r and pypi) 14:16:32 *stuff 14:16:38 but now we need to do it manually 14:17:11 ok 14:17:22 so there is one more topic from me 14:17:29 #topic python 3 14:17:58 I want to propose to switch our docker image to use python 3 by default 14:18:17 or we can provide one more docker image. let's call it "experimental" 14:18:27 why not 14:18:47 Also, it would be nice to switch several(all) or regular gate jobs to python 3 14:18:54 i mean if it's a container aren't we supposed to put whatever we want there? 14:19:04 we can:) 14:19:27 sure we can 14:19:43 i mean nobody should expect that we won't 14:19:43 also, all upstream gates will move to latest ubuntu image which contain python 3 by default 14:19:44 )) 14:20:31 these two topics are less related for me 14:20:41 :) 14:21:53 ok, anything else to discuss? 14:22:05 About docker image, why not. Experimental image do not oblige us 14:22:16 Nothing from me 14:22:52 not from me 14:22:57 #endmeeting