13:04:36 #startmeeting rpm_packaging 13:04:36 Meeting started Thu Mar 24 13:04:36 2016 UTC and is due to finish in 60 minutes. The chair is dirk. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:04:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:04:40 The meeting name has been set to 'rpm_packaging' 13:05:31 hello 13:05:35 hi 13:05:49 hey everyone 13:05:55 please update agenda at https://etherpad.openstack.org/p/openstack-rpm-packaging 13:06:35 o/ 13:08:10 #topic stable branch 13:08:26 hi 13:08:48 I'd like to request a creation of a stable branch for rpm-packaging so that we can continue updating to master and to stable/mitaka independently 13:08:53 does anyone have concerns with that? 13:09:43 dirk, fine 13:09:51 +1 13:10:06 +1 13:10:19 only 1 question 13:10:52 if nothing changed - cherry-picking master -> stable/mitaka or how? 13:11:20 I'm about new uploads 13:11:42 1st patchset goes to master 13:12:07 and if there are no diff, cherry-pick back to stable 13:12:23 thoughts? 13:12:40 yep, would work for me 13:12:46 assuming that the change makes sense for mitaka 13:12:50 yes, master should be first 13:12:55 #agreed create a stable/mitaka branch for rpm-packaging 13:13:06 #topic possible design session topics - CIs, how to react, which artifacts could be produced(IgorYozhikov) 13:13:36 yes, want to clarify possible topics 13:14:34 I'm suggesting to discuss how developers should react on CI results 13:14:36 so the main issue I know of is that we didn't get any rooms allocated 13:14:58 dirk, could we do that or it's late 13:16:25 if it's not late - let me know, i'll try to help with somehow 13:17:00 well, we can somehow work it out, even by going to a coffee place 13:18:09 number80, I know, but it could be interesting for more wider audience 13:18:46 IgorYozhikov: we can always manage to be inserted in the official schedule if we have a defined place 13:19:31 IgorYozhikov: I can try to get an answer, but the basic problem 13:19:40 was that I missed the deadline 13:19:47 number80, does it means that all rooms already booked? 13:20:14 IgorYozhikov: yes. there are many more projects in the big tent and fewer rooms 13:20:21 so we hav eless availability than before 13:21:01 ack 13:21:06 dirk, i c. It would be great, because we could discuss not only one particular topic 13:22:14 IgorYozhikov: yep 13:22:19 so I'll try to get an answer 13:22:33 dirk, thanx again 13:22:35 we just need a room that says "rpm packaging" work group, right? 13:22:49 looks fine 13:22:50 and we can bring up topics then for the slot? 13:22:53 yes 13:23:02 ok, 13:23:11 #agreed try to add a slot to the agenda even without a room available 13:23:51 so, i'll try to prepare material from my side and share it with you 13:24:14 great 13:24:21 #topic futher steps according to http://toabctl.de/openstack/rpm-packaging-status.html update "needs upgrade" 1st?( 13:24:50 here I want to figure out what will be more useful to do next 13:25:20 update & merge pending CRs | update what is marked as required 4 update 13:26:10 i mean "needs upgrade" from toabctl list 13:27:19 yep, that should be done as well 13:27:20 I prefer - update outdated 13:27:39 and after that proceed with py*clients 13:28:01 IgorYozhikov: +1 13:28:14 and we should remove all the versions we currently have in the .spec.j2 files. 13:28:37 toabctl, as here - https://review.openstack.org/#/c/270826/ ? 13:29:29 omg, I pushed request before save file :( 13:29:30 IgorYozhikov: hm. there are still versions. I guess from test-requirements because we currently only allow a single requirements file? 13:30:57 fixes 13:31:11 on the way 13:31:40 https://review.openstack.org/#/c/270826/16/openstack/oslo.db/oslo.db.spec.j2 13:31:42 updated 13:31:50 sorry for that 13:32:55 toabctl, I suggest to leave known versions which are differs from requirements file. your opinion? 13:33:24 I mean if version in setup.* is higher then in requirements 13:33:59 IgorYozhikov: I would then just bump the version in the requirements . 13:34:21 but we should check why there are different pbr versions. at least I don't know why that's the case... 13:35:58 may be after stable/mitaka will cut for global-requirements - versions will be equal, just guessing 13:36:17 yeah 13:36:28 ok, so we create a stable/mitaka branch and can keep version handling in global-requirements 13:36:59 anyway, we agreed on updating 1st what is already requires updates 13:38:26 yep 13:38:44 #agreed submit updates for the outdated packages 13:38:48 ok, anything else? 13:39:17 may be last concern - how to deal with pbr 1.6 vs 1.8 13:40:04 leave it as is and just build 1.8 which will be used 13:40:16 +1 13:40:40 ok, so, i'll drop all the rest version record from my CR 13:41:22 done 13:42:52 I'm out of topics for today. Just want to share with you about progress with our CI. 1st steps made inside our "sand-box" and we've got today "green" jenkins jobs. 13:43:06 IgorYozhikov: you're testing what? 13:43:16 mirantis packags on rhel/centos ? 13:43:23 spec.j2 13:43:49 we use centos base layer for packages 13:44:05 ok 13:45:32 so are we done? 13:45:47 toabctl, looks so 13:46:06 any1 else have something to discuss? 13:46:26 number80: any update on your testing integration? 13:47:38 well, I guess we can continue in openstack-rpm-packaging 13:47:47 next week same time! enjoy the long weekend! 13:47:49 #endmeeting