12:00:24 #startmeeting Mer release management meeting 24/1/2012 12:00:24 Meeting started Tue Jan 24 12:00:24 2012 UTC. The chair is Stskeeps. Information about MeetBot at http://wiki.merproject.org/wiki/Meetings. 12:00:24 Useful Commands: #action #agreed #help #info #idea #link #topic. 12:00:40 #topic Since last 12:00:49 #topic Since last 12:01:35 #info Released 0.20120120.1 12:02:02 bunch of upgrades, fixes, qt4.8.0, etc, but not qtwebkit 2.1.0 yet, as well as switching to GNU style symbol hashes for platforms that support it (MIPS don't) 12:02:41 #info First booting to qmlviewer on MIPS (O32 ABI, MIPS32 processors), http://releases.merproject.org/~carsten/mer-on-mipsel-qemu.png 12:03:02 #info Mer reference image kickstarts, http://releases.merproject.org/releases/0.20120120.1/kickstarts/ 12:03:16 anything else? 12:03:38 oh, and 12:03:43 #info FOSDEM ARM BoF: http://fosdem.org/2012/schedule/event/arm_bof 12:03:58 from me 12:03:59 #info Significant progress on the sample HA packaging 12:04:19 #info Joggler HA now works 12:04:49 #info Wiki structuring effort started and looks good 12:05:30 that's most of what I've been doing 12:06:58 right, switching to plans 12:07:12 (unless anyone else has anything to report in "since last" ?) 12:07:25 * lbt looks at phaeron ... :) 12:07:31 mmm 12:07:33 oh, right 12:07:39 I hate spectacle :D 12:07:50 #info OBS exports 'blocked' state over the repository cache 12:07:56 we should take over developing 12:08:09 phaeron: fork it and call it mer-spectacle 12:08:16 Stskeeps: agree 12:08:32 Stskeeps: oh yeah about that , are you using something to detect whether a repo is published 12:08:36 before downloading its state 12:08:47 yes, myself ;) 12:08:58 oh :D 12:09:08 rofl 12:09:11 didn't work this time, must be a bug 12:09:20 there's a function to check for that in python-buildservice 12:09:24 * lbt offers to make a patch for Stskeeps... 12:09:33 heh what component do I report it against 12:09:49 anyway 12:09:51 .Other and catch in triage 12:10:24 i stole some of phaeron's packages and added a bit on top, https://build.pub.meego.com/project/packages?project=home%3Astskeeps%3Atools 12:10:27 with a working 'mic' 12:11:05 OK - I want those tools to go through some kind of QA release cycle too 12:11:13 :nod: 12:11:14 we did this in Nokia and it's a PITA 12:11:21 really really annoying 12:11:28 so we need to do better 12:11:51 yeah but the difference is this time we're mostly forking them 12:11:53 the idea was to create a Mer Tools project, right? 12:11:59 Stskeeps: yes 12:12:08 it's actually #1 on my 'plans' 12:12:09 no meego upstream to scream at 12:12:11 then we can take it over gerrit and release it against mer core 12:12:19 Carry on with SDK (including Mers tools setup) 12:12:33 :nod: 12:13:14 * phaeron wanted to try review board .. 12:13:15 then #2 is Take a look at infra backlog - IMG probably highest prio 12:13:35 phaeron: yeah ... we were supposed to have a months trial of gerrit.... 12:13:49 month's or months' 12:13:56 :D 12:14:12 OTOH it seems to provide a reasonable service 12:14:31 my concern is that we're getting towards needing a pkgDB 12:14:48 I vote for having one inside obs 12:14:54 yeah ... 12:15:07 I'm kinda leaning that way 12:15:11 \o/ 12:15:45 as usual I worry about monolithic OBS 12:16:56 ideally no strict ties to obs, if anything, to the core's .xml descriptions 12:17:57 having text based is the other idea 12:18:28 tbh it's still a little in the distance 12:18:39 getting QA process sorted first is higher prio for me 12:18:42 yes 12:18:48 if anything cleaning up IMG 12:19:06 though phaeron did most of that already 12:19:54 so phaeron lets put RB on the back burner for a couple of weeks? 12:19:59 ok 12:20:01 bring it up again after FOSDEM ? 12:20:04 yes 12:20:27 hmm Stskeeps, you're away-ish next week 12:20:32 yes, anyone up for chairing? 12:20:32 :P 12:20:37 sure 12:20:40 ok, plans time 12:20:45 any agenda items for a FOSDEM meetup? 12:21:18 icecream? 12:21:22 maybe just action each of us to identify topics best suited to f2f meetings 12:21:28 like icecream:) 12:21:54 let's think a bit about that during the week 12:21:57 #topic Plans 12:22:46 i'm currently moving SB2-OBS into Mer production, as stated on the mailing list 12:22:52 so we're intentionally first releasing in a few weeks 12:23:16 as well as adding MIPS port on top when we have it 12:23:32 this will require SB2-OBS to be accessible in package form for people having OBS'es and local builds 12:23:45 ie, packages of obs 12:23:53 oh yeag 12:23:56 *h 12:24:02 and COBS should have it :) 12:24:35 I looked at how opensuse build their rpms. they use the source service to pull from git 12:24:43 ok 12:24:44 can we do same? 12:24:59 if lbt agrees to enable it :) 12:25:16 if we do it properly 12:25:17 build.opensuse.org is a bit hosed atm, so let's not rely on that one for builds 12:25:35 I think it would be saner than uploading tarballs to obs 12:25:47 just my 0.02 12:26:00 it , is a bit hackish though :( 12:26:20 lbt: so we need to look at that again 12:26:49 I'd like to see git push to OBS rather than the other way round 12:27:17 pandora's box 12:27:34 so obs would host a git repo that you commit to? 12:27:39 I agree of course 12:27:46 timoph: no need 12:27:53 timoph: no git commit pushes to obs 12:28:07 git/gerrit/boss trigger sends a tarball to OBS 12:28:13 also, we have to do this within two weeks.. 12:28:13 ah. ok 12:28:13 :P 12:28:15 possibly tarball+patches 12:28:24 Stskeeps: that's the problem :) 12:28:28 we have to build packages in 2 weeks 12:28:42 we don't need a tools cycle within 2 weeks 12:28:50 yes, ok 12:29:13 the critical thing is that we document (spec) it well enought that any one of us can do it manually 12:29:16 then we automate it 12:29:24 not the other way around 12:29:48 ideally also able for people using mer in their own obs to pick it up 12:30:09 yes 12:30:22 but anyway, just stating what's coming, so noone's surprised when their builds fail ;) 12:30:59 hehe 12:31:05 some tasks for bugzilla 12:31:14 #info add 'mipsel' architecture support to 'mic' 12:31:54 and to cobs ? 12:32:06 i guess 12:32:07 btw 12:32:20 #info obs: 'mipsel' architecture doesn't work in practice, 'mips' does 12:32:21 :P 12:32:26 so it's Core_mipsel / mips 12:32:33 mipsel simply won't work in meta prj 12:32:42 yet another alias 12:32:44 yeah ... that naming needs more explanation 12:33:04 see http://releases.merproject.org/releases/latest/builds/armv7l/packages/ 12:33:38 the arm* dirs will hopefully go down in amount with sb2 12:34:09 meanwhile could we explain them somewhere 12:34:12 :nod: 12:35:20 there's a lot less hocus pocus going on with the new cross compile approach, so 12:35:40 that's a good part of the justification then 12:35:50 and deomonstration of Mer value add 12:36:12 (ie it's worthwhile documenting the old rubbish) 12:37:28 anyhow, yes, add mips to mic and obs - with documentation in the wiki in http://wiki.merproject.org/wiki/Category:Arch 12:38:21 :nod: 12:39:53 infra then 12:40:34 I'm thinking we can get an IMG setup or a base Mer COBS setup before FOSDEM 12:40:39 probably not both 12:41:00 given SDK/Tools is higher prio (which I agree with) 12:41:13 we have a c.obs and no signs yet of shutdown 12:41:25 Intel will give us some notice I'm sure 12:41:35 so IMHO that's low prio until they do 12:42:03 and I think X-Fade is keeping current backups of key stuff 12:42:36 so I would like to use swerden's machine for an IMG deployment 12:43:07 the other use was to take the wiki onboard - but then we get into ldap and stuff 12:43:30 so IMG is more valuable 12:43:34 mm, i respectfully disagree, as we're not only putting us in risk, but also PA, Nemo efforts - and i don't want to rely on notices, as i think we already had one 12:43:35 . 12:43:45 so i'd prefer base COBS setup, even if minimal 12:44:02 as this was what we were approached with at first, with the PA angle in mind as well 12:44:10 to show progress 12:44:30 if we deploy cobs to it we can't use it for IMG 12:44:36 so no image creation 12:44:51 i know, and for the nearby laying things, we can do manual image creation 12:44:54 ie, platform sdk, etc 12:45:00 have you heard anything on meego cobs? 12:45:21 it's only january and we got april as an indication 12:45:58 also, another thing to perhaps keep in mind: IMG supporting 'mic' 12:46:11 that's easy 12:46:15 that needs to be done as well 12:46:25 #info IMG should support 'mic' 12:46:33 one character change at least 12:46:38 :D 12:46:41 phaeron: bit more than that :) 12:47:05 it should also use the Mer SDK/bootstrap 12:47:11 the options seem to be mostly the same and most of them are inside the kickstart anyway 12:47:22 but anyhow... 12:48:33 the other thing from my PoV is getting into a c.obs setup is a move away from the process and RE 12:48:50 and I don't really want to context switch just yet 12:49:27 well, you're of course welcome to select your own priorities - i'd personally like us to be on a level where we have a development OBS we aren't afraid will disappear at any minute 12:49:37 but OK, if you want to go with IMG, go with IMG 12:49:49 I do agree 12:49:55 and c.obs is very high on the list 12:50:01 even a FE/BE that responds without workers is fine 12:50:26 is the new machine physically connected to the same infra ? 12:50:28 no 12:50:44 there's a lot of vpn tunneling I need to review 12:50:49 ah so one machine won't be able to host cobs + surrounds 12:50:55 it seemed to take a lot of cpu to encrypt 12:51:12 it's a single 4-thread 8Gb machine 12:51:13 lbt: this was when i forgot to add obs worker cache 12:51:14 :P 12:51:21 Stskeeps: hehe 12:51:22 OK 12:51:46 phaeron: oh, and it runs suse 12.1 12:52:00 fun 12:52:03 yeah 12:52:15 3Tb disks wouldn't boot on 11.4 12:52:23 or something like that 12:52:46 lbt: OK, how about 'set up IMG' and 'wiki page describing migration plan and setup for new-COBS'? 12:52:55 along with some dates 12:53:25 and spec 12:53:26 for pre-FOSDEM 12:54:12 i think that works for me, then we can show activity and actual plans 12:54:45 is Stefan going do you know? 12:54:59 good question, let's ask? 12:54:59 our phone conferences were not very useful 12:55:12 there's a lot of opensuse people going, so 12:55:13 I agree that living up to the promise and making people safe when they bet on you is important 12:55:34 *feel safe 12:55:44 we also need a plan for Nemo BOSS migration, too 12:56:08 yeah, true 12:56:20 ouch 12:56:30 that's a lot of sysadmin work 12:56:34 that's what I meant by surrounds 12:56:45 phaeron: I misunderstood 12:57:07 I thought "I've not heard anyone mention Surrounds in a long time..." 12:57:38 I didn't know it was a reserved keyword :D 12:58:08 #info prepare migration plan and setup for a Mer COBS. Describe what's needed to make it happen. 12:58:31 Stskeeps: we could do that on 4 of the Hetzner machines couldn't we? 12:58:45 dowhich? 12:58:51 complete COBS 12:59:04 not workers 12:59:09 we need space for CI OBS 12:59:17 no, 4 new one 12:59:19 s 12:59:20 just saying that for $600 + $200 per month 12:59:44 that is true, though i'd like to see how much it actually costs in traffic for remote workers too 13:00:09 we do have something like 40tb traffic each on the phosts we have 13:00:23 er, total 13:00:32 allowance or used? 13:00:37 allowance 13:00:43 and LAN is unlimited 13:01:01 we may want to tell them to allocate physically close if we take that route 13:01:12 I gtg 13:01:14 cya 13:01:17 but I was mainly thinking of a HW spec 13:01:18 yes, let's wrap up the meeting 13:01:19 bye 13:01:21 bye 13:01:41 so yes, img and COBS deployment plan 13:02:00 pre fosdem 13:02:32 #info prepare IMG deployment plan (and maybe deployment) 13:04:21 anything else? 13:04:55 I wanted to ask about Mer Groups but that can be in #mer 13:05:09 think that's it 13:05:13 thank you all for coming 13:05:19 ty 13:05:19 #endmeeting