12:05:13 #startmeeting Release management sync meeting 21/2/2012 12:05:13 Meeting started Tue Feb 21 12:05:13 2012 UTC. The chair is Stskeeps. Information about MeetBot at http://wiki.merproject.org/wiki/Meetings. 12:05:13 Useful Commands: #action #agreed #help #info #idea #link #topic. 12:06:52 so, i think we're doing quite well on way to the next release 12:07:29 we have deloyed sb2-obs patches to community obs and we have seen no visibile regressions from the cross compilation switchover 12:07:46 hello 12:07:58 I have to leave in ~10 minutes 12:07:59 there will be a prerelease (or 0.0.4) soon 12:08:00 ok 12:08:01 http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-02-21-12.05.log.txt 12:08:42 there is still however some fallout in other non-mer targets with the patches and we're working on it 12:08:57 and showing bugs that wasn't visible before 12:09:46 any other statuses? 12:09:46 o/ 12:10:04 Mer c.obs is mainly deployed with new Mer-OBS, Mer MDS and a simple worker but some nasty issues remain - http/https redirect Abandonded this for now. 12:10:27 SDK images built - enter-chroot approach seems fine. looking at lxc and VMs now Packaging done in a branch - https://build.pub.meego.com/project/monitor?project=home%3Albt%3Abranches%3AMer%3ATools%3ATesting local mic builds work - working on IMG to get them done in an easily downloadable area 12:10:44 :nod: 12:10:51 I think I'll push that to Testing now 12:10:55 we should start modifying guides to be using platform SDK as well 12:10:59 like image creation and other things 12:10:59 yes 12:11:12 Plan was to do some bugfixes using SDK but .... OBS got in the way 12:11:19 yeah 12:11:28 so I think that's what I'll do next 12:11:40 use SDK to hit some small bugs and write up 12:11:42 i'm hoping for next release friday 12:11:47 hmm 12:11:52 too early? 12:11:53 monday betteR? 12:12:08 next actual release that is, not prerelease 12:12:10 I haven't done sb2 builds in SDK 12:12:26 and we kinda wanted the SDK at the same time 12:12:44 yeah, true, but we need more infra for that 12:12:45 but maybe leave the SDK as it's still alpha 12:12:47 * Sage_ would suggest pushing forward one week 12:12:49 or release it as that 12:12:57 if you want to do more stuff 12:13:05 it is already so much late :/ 12:13:15 i'd prefer to release it as that, ie, mic, osc, basics working 12:13:16 how important is it to co-release SDK though 12:13:23 yeah - me too 12:13:24 it doesn't have to be co-released 12:13:28 early/often 12:13:31 but it would be good to have some kind of version 12:13:43 I also haven't used it as a dirty build environment 12:13:49 Push SDK out with next release? 12:13:51 just osc build inside sdk 12:14:01 Sage_: yeah - announce it as alpha 12:14:08 and say what we've tested 12:14:10 friday or monday? 12:14:14 monday 12:14:21 i'd like it to be ready for next nemo release too 12:14:22 ok 12:14:38 phaeron: IMG is looking good isn't it? 12:15:19 he may have gone 12:15:21 I think it is 12:15:31 I am slightly blocked on infra atm 12:15:51 we are a bit stretched 12:16:31 in terms of people or in resources 12:16:38 vgrade will buy another EX5 12:16:41 HW 12:16:49 k 12:16:51 we have 20+VMs on 2 hosts 12:17:07 so I've started the chat with H 12:17:19 etzner, let's not confuse the abbreviations 12:17:19 :P 12:17:24 :) 12:17:25 just FYI for this update really 12:17:28 sorry 12:17:43 phone 12:17:50 so, i guess people's tasks are filled up for this week? 12:17:52 lbt: yes IMG is ready to create rootfs using new mic 12:17:53 back 12:18:10 and working on it to use the sdk based kvm 12:18:14 mdfe_: http://mer.bfst.de/meetings/mer-meeting/2012/mer-meeting.2012-02-21-12.05.log.txt 12:18:16 eta today or tomorrow 12:18:28 next week i'd like us to look saner at Mer's BOSS 12:18:39 Stskeeps: yeah, depends on IMG too 12:18:40 and set up a more stable contribution and testing process 12:19:17 as well as automated releases 12:19:23 ideally ;) 12:19:28 the BOSS bit is on my near-term list 12:19:32 http://wiki.merproject.org/wiki/Process 12:19:36 * phaeron thinks Stskeeps is optimistic 12:19:39 :D 12:19:47 hey Stskeeps, aren't I supposed to do the next release? 12:19:56 following your docs? 12:19:58 *g* 12:20:44 anyhow.... new subject 12:20:49 https://bugs.merproject.org/show_bug.cgi?id=174 12:21:01 use /usr/* and not /bin /lib 12:21:21 told Sage_ to bring it up here 12:21:21 it's a large, invasive task 12:21:25 is it? 12:21:27 yes, it is 12:21:30 why? 12:21:33 there's packages installing into /lib 12:21:42 assuming /bin -> /usr/bin is a symlink 12:21:45 mm 12:21:56 also, for no reason whatsoever, there's packages that install into both with same filename.. 12:21:57 it becomes an rpmlint warning issue 12:22:02 Stskeeps: bug 12:22:22 like I say in the bug 12:22:33 we should adopt the policy, make rpmlint warn 12:22:34 lbt: imager succeeds now in :Testing 12:22:43 clean up and then make it mandatory 12:22:54 *if* we agree with it :) 12:22:55 and now gtg 12:23:03 phaeron: thanks .. l8r 12:23:04 cya 12:23:20 lbt: so you want to rpmlint warn when something is installed into /lib /bin /sbin ? 12:23:38 seems like a sane pre-req to the policy 12:23:44 http://pastie.org/3426665 12:23:47 to allow us to phase it in 12:23:51 ^ all those package needs changes 12:24:03 the point is that we're about to do some boss automation 12:24:07 Sage_: at least.. 12:24:11 and that's going to involve writing checks 12:24:13 Stskeeps: :nod: 12:24:34 so if we agree policies like this early then we write a few checks, once 12:24:58 ok, i have no objections to this 12:25:19 one last thing before I go 12:25:24 OK - that's good - the implementation must, of course, not cause isssues 12:25:25 I don't either but I think it is larger task than lbt thinks. 12:25:29 yeah 12:25:30 Sage_: always is 12:25:34 lbt: :) 12:25:38 we needed updated mic which has Sage_'s patches already in 12:25:45 Sage_: your rpm depend may be a pita 12:25:57 lbt: well that as well :/ 12:26:17 phaeron: OK - should they be merged to our git 12:26:29 lbt: those patches are in mic upstream 12:26:32 Sage_: do you know what patches he means 12:26:34 OK 12:26:52 so if we pull latest we're good ? 12:27:04 lbt: latest master yes, latest release needs one patch 12:27:16 latest release is 0.6 and it needs this patch https://github.com/jfding/mic/commit/5abead0efc7b0f84c83c9445b565c794dbf54e8a 12:27:28 OK 12:27:32 one small comment 12:27:44 I have to go out after this meeting so may be doing it later anyhow 12:27:45 https://bugs.merproject.org/show_bug.cgi?id=179 was rated low priority 12:27:55 if something is released, not CI checking it is major 12:28:11 as it might regress and be a mess to figure out where it went wrong 12:28:22 my fault - I wasn't sure of the status of MIPS yet 12:28:38 just for future reference, so it needs bumping to medium/high 12:28:41 I actually thought it couldn't be released since we have no CI of it 12:28:50 it is actually on stable condition right now 12:28:51 high 12:29:01 ok 12:29:26 done 12:30:09 I made a few things "low" (predicting the chat with andre__ actually) 12:31:44 nb ... not sure if it's this meeting or Mer AB or something ... RasPi is going to be out soon 12:31:57 we should have a vendor/port/project ready 12:32:13 it has to be tied together with qt5 work 12:32:35 as qt4.8.0 in default conf won't work with their gles stack 12:32:44 OK - so it's one of my tasks as part of my RasPi role 12:32:57 so keeping a Mer/RasPi page updated is important 12:33:10 so that sounds like a Mer/Qt5 status 12:33:20 we should help ahma along 12:33:56 https://bugs.merproject.org/show_bug.cgi?id=181 maybe should be medium instead, i'll take this one on me 12:34:02 it should be easy to rpm query all the rpms 12:34:06 OK - I'll ask him for Mer/Qt5 status then 12:34:18 qtonpi release image is coming out too 12:34:23 Stskeeps: hmm 12:34:42 I would hate to see a hodge-podge approach to data management in Mer 12:35:01 so just noting that this is part of a bigger issue 12:35:13 :nod: 12:35:26 and like the fakeobs quick hacks.... you get stuck with them 12:35:33 (like arch iirc) 12:35:47 that's the only reason it's low 12:36:01 "do it right, even if we have to wait a couple of weeks" 12:36:01 :nod: 12:36:15 you're right, fakeobs improvements should be on my list before that 12:36:58 I actually wanted to use MDS to deliver releases too - as mentioned with sonach this AM 12:37:11 is that feasible (not having seen the code for any of it) 12:38:32 that's feasible and where i wanted it to go 12:38:44 good 12:39:01 the other thing is some kind of filters - by arch/release 12:39:09 I'm sure you have that too 12:40:25 :nod: 12:40:50 it's important we can do stable releases hence the BOSS focus next week 12:40:53 i do too much manual work for it 12:41:23 I was only partly kidding about me doing the next one - we did agree that :) 12:41:51 yeah, i know 12:42:14 still, it's the manual work before a release 12:42:17 picking up changes, etc 12:42:52 yeah - this is kinda where I'd have liked to get more BOSS webui stuff working 12:43:21 but realistically that's not on the cards w/o a lot more human resource 12:43:36 :nod: 12:44:19 so, I think that's all I have 12:44:34 so, next release on monday then 12:44:42 i think the release content itself is quite good already 12:44:47 OK 12:44:51 #info next release on monday 12:44:54 when next prerelease will be then? 12:45:02 as soon as it finishes building 12:45:07 could you put up a checklist kinda page 12:45:08 Wondering if the release after taht would be on thursday? 12:45:11 real rough 12:45:29 on what you need to do - don't overthink it - just add to it as you go along 12:45:43 Vendors really need more time between prerelease and release than day or two ;) 12:45:48 :nod: 12:46:23 IMO first prerelease should be out on Monday 12:46:25 Sage_: i'm not convinced we'll have more releases after that one, but yes, in case, it'd be thursday 12:46:27 eg I'd like to see us make a decision on a date and then see a triage-like meeting to mark some bugs as release blockers 12:46:46 i'm not delaying this full release any further than to monday 12:46:50 it's already too late :) 12:46:57 :) 12:47:01 np - I'm talking about futures 12:47:02 fair enough 12:47:31 http://pastie.org/3426770 is expected changes 12:47:57 so there will be a prerelease with that content as soon as i can 12:48:06 k 12:48:15 ok 12:48:28 that's the stuff we need to share better 12:48:41 yes, and ideally it would be BOSS showing this 12:48:53 and producing the prerelease too 12:49:00 yup 12:49:36 #info next full release on monday 12:49:51 #info next prerelease with content http://pastie.org/3426770 ASAP (due to CVE bug in libpng) 12:51:03 on documentation side, i'd like it to be possible to read from start, platform sdk install, entering sdk, grabbing/making .ks, to image creation step in wiki 12:51:06 by monday 12:51:41 that's not a problem 12:52:05 mic works fine in the sdk (at least it self-hosts the sdk....) 12:52:32 next week we also start working with generating target sysroots for use with sb2 as well, i think 12:52:37 on platform sdk side 12:53:15 mic can do that 12:53:56 okay, anything else? 12:54:24 Bug 188 - Document image production using SDK 12:54:52 :nod: 12:55:30 okay, thank you all for coming 12:55:34 #endmeeting