Hi, We had a release management meeting yesterday but the meeting bot was on vacation, so here's the logs:
[13:05] <Stskeeps> #startmeeting Mer release management meeting 17/1/2012 [13:05] <MerBot> Stskeeps: Error: Can't start another meeting, one is in progress. [13:06] <Stskeeps> oh ffs [13:06] <lbt> nope... just broken [13:07] <Stskeeps> okay, anyway, let's go through a quick status of release management and release planning [13:07] <Stskeeps> i'm planning a new prerelease of Mer tomorrow hopefully, which will include a bunch of changes, including speedup in symbol lookup and Qt 4.8.0 and qtwebkit 2.2.1 [13:07] -!- dm8tbr [[email protected]] has joined #mer-meeting [13:08] <Stskeeps> dm8tbr: could you reboot merbot? it's stuck in a meeting [13:09] <Stskeeps> i've been working on new ways of preparing and sharing Mer image descriptions, both the core, hardware adaptations, UX, in order to be able to have a feeling of just pulling additions to your product off a shelf [13:10] <Stskeeps> http://releases.merproject.org/~carsten/mer-kickstarter-configs/ is an example, mer/ contains descriptions of the core that people can derive from, includes repository information, basic settings, etc. mer-reference-images is the images that will be included with mer release, useful for hardware porting, or as examples for your product [13:10] <Stskeeps> and ks/ is the outputted kickstart files (still some bugs to fix) [13:10] <Stskeeps> i also started documenting the kickstarter format on wiki [13:10] <Stskeeps> .. what about the rest of you? [13:11] <lbt> This is good - fits right alongside the work I'm doing on getting systems setup and actually starting a new product [13:11] <lbt> I'm using the Joggler as a product (it's an Atom powered Openframe pictureframe) [13:12] <sonach> StsKeeps: this work is very useful for me:) [13:12] <Stskeeps> yes, for all of us [13:12] <lbt> this is helping get the kernel packaging setup and I'm also going through some first-mer-boot docs too [13:12] <lbt> I'm not yet at the stage where I'm pulling in updates but it's on the plan [13:13] <lbt> essentially I'm going to do "a day/week/month,,, in the life of a vendor" [13:13] <lbt> to go through all the things like integrating a new Mer release [13:14] <lbt> or managing an old internal release after Mer has been updated [13:14] <lbt> bug submission and tracking ... whilst keeping my bug 'private' [13:14] <lbt> so tbh a lot of this is spread out as bullet points and notes at the moment :) [13:15] <lbt> I hope to get the first bit up this week [13:15] <Stskeeps> we should probably do a handbook outline or something [13:15] <lbt> yeah ... I also have that "concept index" I'm working on too [13:15] <lbt> but a handbook is another way to look at the "day in the life of" [13:16] <lbt> (you could also call it process documentation :) ) [13:16] <Stskeeps> :nod: [13:16] <lbt> I need to make some time to look at infra too [13:16] <lbt> there's a fair backlog there now [13:17] <lbt> but I think phaeron can help out there [13:17] <lbt> ok... done until I remember something else [13:17] <sonach> lbt: I think we all know the basic steps of building. Maybe the handbook should focus on some important points. [13:18] <lbt> sonach: suggestions welcome [13:18] <lbt> especially for prioritisation of docs [13:20] <Stskeeps> or what docs are missing :) [13:20] <sonach> For me now, I am porting Mer to my platform. I can get sources of bootloader and linux kernel of the platform. But I don't know how to config/package/... [13:20] <lbt> right [13:20] <lbt> I have docs on exactly that [13:21] <lbt> I'm doing a small tool that will check your .config and say "you need CONFIG_AUTOFS" .... because systemd needs it [13:21] <lbt> http://wiki.merproject.org/wiki/Adaptation_Guide#Kernel [13:21] <lbt> is that what you meant sonach ? [13:22] <Stskeeps> but also how to package a kernel, i presume [13:22] <sonach> lbt: Yes! It seems good to me:) [13:23] <lbt> Stskeeps: got that covered too [13:23] <lbt> you need a git tree with a set of commits and a baseline tag [13:23] <lbt> it prepares a .yaml section for the patches [13:23] <lbt> and all the patches etc [13:24] <Stskeeps> lbt: just remember that that's not a typical scenario for someone getting a reference board, a tarball is [13:24] <lbt> ... worst case you feed it a tarball [13:24] <Stskeeps> ok [13:25] <lbt> I'm sure sonach has a nice kernel git tree though ... :D [13:25] <Stskeeps> so, my goal is that the kickstarter stuff is in next mer kernel so we can start using that [13:26] <sonach> lbt: No git tree, but source code in a tarbar privided by the vendor. [13:26] <lbt> sonach: *grin* .... I'm sure we'll manage [13:27] <Stskeeps> right, anything else to report? [13:28] <lbt> we have a week and a bit to FOSDEM [13:29] <lbt> err, no 2 weeks... nm [13:30] <lbt> nothing from me [13:30] <Stskeeps> ok, thank you all for coming [13:30] <sonach> Stskeeps: Where can I report my porting process? to the mailing-list? [13:31] <Stskeeps> yes, if you have any questions or the likes or want to share experiences, mailing list is good [13:31] <Stskeeps> even asking where documentation for things is [13:32] <lbt> and if you have any issues to discuss then raising them here is fine as well [13:32] <sonach> OK. [13:32] <sonach> nothing from me [14:01] -!- sonach [[email protected]] has quit [Ping timeout: 240 seconds] BR Carsten Munk
