11:03:16 #startmeeting Mer release management meeting 11:03:16 Meeting started Tue Jul 31 11:03:16 2012 UTC. The chair is Stskeeps. Information about MeetBot at http://wiki.merproject.org/wiki/Meetings. 11:03:16 Useful Commands: #action #agreed #help #info #idea #link #topic. 11:03:33 #info one more systemd patch needed and we're ready for prerelease 11:04:23 #info Automatic smoke test QA would have been immensely useful 11:05:23 who else has something to report? 11:06:13 #info quickbuild work in osc is done - pending changes are in Core for next release 11:07:17 #info SDK is being updated and bugfixed at the moment - interested parties should contact me now for feature inclusion or to help with testing 11:09:02 #info BOSS bundler work was paused but now works using Bundler which should make it *much* easier for any Mer systems using ruby to stay up-to-date 11:10:18 #info git-pkg is now being used for Mer:Tools and works nicely. I'll release it around the time I release the SDK. 11:11:23 mmm, think that's it for news 11:11:52 sorry too many things happening at the same time 11:12:01 we really need to discu git-pkg before pushing it 11:12:33 I've been discussing it for many months :) 11:12:49 now I'm JFDI'ing it 11:13:07 well I pointed out some things and you didn't address them yet so.. 11:13:23 this is not OBS-side 11:13:25 lbt: so we have ability to deploy an up to date BOSS? 11:13:39 Stskeeps: yes, when we have one 11:13:46 (hmm?) 11:13:53 lbt: yes I know but it duplicates the obs side stuff 11:13:57 anyway discuss later 11:14:05 was just registering my point 11:14:08 I've got a mechanism now - but we haven't ported boss to latest amqp gems etc 11:14:14 phaeron: sure. 11:14:15 okay 11:14:35 can i expect ability to have an up to date BOSS installation on mer infra in next week, or should i use the old one? 11:14:45 (say no if you don't think it can be delivered) 11:15:26 imho with my current load I won't be able to help in this week , so I would rather do the boss and new process stuff after the release 11:15:43 alright, so i'll use old one 11:15:50 I tend to agree - would rather focus on SDK 11:16:17 OK 11:16:23 the old installation 'works' so 11:17:15 phaeron: do you have an url for your osc-boss stuff? 11:17:56 Stskeeps: the python library ? 11:18:08 yes 11:18:24 nb - I'm going to start pushing all git to mer's gitweb 11:18:55 "all" ? 11:19:02 no problem with using github etc but master is mer git 11:19:08 mer-tools/ you mean? 11:19:14 yes 11:19:26 Stskeeps: https://meego.gitorious.org/meego-infrastructure-tools/python-buildservice/trees/mint_master 11:19:37 phaeron: thank you 11:19:39 Stskeeps: it's not perfect but better than osc 11:19:44 do we have it packaged anywhere? 11:19:49 for opensuse/debian 11:20:12 Stskeeps: yes on cobs. Project:MINT:Testing 11:20:30 https://build.pub.meego.com/project/monitor?project=Project:MINT:Testing 11:20:33 thanks 11:20:48 lbt: where are we at with OBS with phaeron's disable-patch? 11:21:11 I've done a review but need to create and run some tests 11:21:14 Stskeeps: lbt code reviewed it. 11:21:39 I have packages in Mer:OBS:Devel 11:21:41 lbt: OK, can i get that around thursday sometime? 11:21:53 ok 11:21:59 thanks 11:22:57 so my aim for this week is getting release out thursday 11:23:34 and next snapshot out on friday? 11:23:42 of contents? 11:23:53 we'll see, a lot of stuff to review 11:23:58 yes, I need new rpm and build at least 11:24:06 :nod: 11:25:10 any expectations towards release after the one on thursday? 11:26:02 image tested 11:26:07 blocker 11:27:03 :nod: 11:27:51 I would like us to review how the gitpkg works for Tools and consider it for Core in that timeframe too 11:28:15 :nod: let's give it some weeks in tools 11:29:59 the first point I have is _src doesn't say what git repo it used 11:31:20 it uses "." 11:31:39 lbt: got any documentation on the gitpkg stuff yet? 11:31:45 ie, standard working procedure for a packager/fixer 11:31:57 yes 11:32:17 I'm iterating it during 'real life' use in Tools prep - henc the release 11:32:34 ok, please let me know when you have it 11:33:06 anyway we discuss later 11:33:18 how are we doing on automatic VM testing side? 11:33:30 essentially "gp_setup" to get going; symlink .git to your osc pkg dir and "gp_make_src" to update ready for osc ar/ci 11:33:43 I want to deploy it 11:34:17 phaeron: what do you need for this? 11:34:24 besides cookies, of course 11:34:28 :D 11:34:41 dinner ? ;) 11:34:52 yeah, sure 11:34:58 i meant in terms of infra 11:35:51 seriously though , share phost with obs worker , or powerful vm with nesting ( and hope it doesn't crash both ) and connectivity to boss 11:36:19 not crash both in case of nested vm only 11:37:16 lbt: how does our capacity look atm? 11:37:21 phost4 came free 11:37:35 I still need to do VM migrations 11:37:42 ok, let's use that for auto vm tests 11:37:54 are we keeping it? 11:38:12 keeping? 11:38:18 thought it may be worth dropping and picking up a better host - not 100% sure 11:38:39 * Stskeeps looks 11:38:41 way back the plan included dropping it 11:38:44 what type is it? 11:39:02 not sure - it's not on my dashboard 11:39:17 ok, so it's one of mine 11:39:17 sec 11:39:34 78.46.39.4 11:39:35 ? 11:40:38 if so, it's a EX 5 11:41:03 "phost4 A 78.46.39.4 ; stskeeps replacement for monster" 11:41:04 i don't see any big reason to trade it up, 24 gb ram should be fine for qa workers 11:41:17 so no 11:41:33 it's phost3 which is monster and may want an upgrade 11:41:36 yes 11:42:01 lbt: can you do the needed to enable phaeron to do work on phost4? 11:42:06 yep 11:42:18 my goal is basic i586 smoke testing as a stat 11:42:24 phaeron: let me know when and we'll pair on it 11:43:04 lbt: ok , most probably next weekend. keep in mind we'll eventually want yunta's ots replacement 11:43:11 yup 11:49:03 ok, anything else? 11:50:01 nothing that's not come up in old meetings 11:50:09 alrightt 11:50:12 thank you all for coming 11:50:14 #endmeeting