[03:08] micahg, i updated the seeds for putting blender back [03:23] ScottL: thanks, let's wait until tomorrow's ISO run before reuploading the meta [09:36] Hmm now lmms is now at 0.4.14-rc1 [09:46] And actually it is JUST released two days ago [11:35] ScottL, zequence, len-dt, holstein one of our main targets this cycle is to resume weekly meetings. How's that progressing? [11:36] * smartboyhw goes to send the release report mail [11:37] Actually a draft, I can send it out tmr [11:45] Actually what do you guys wanna add? [11:45] smartboyhw: What report is that? [11:45] Which release? [12:11] zequence, https://wiki.ubuntu.com/ReleaseTeam/Meeting/Agenda/TeamTemplate [12:11] ScottL let me write the reports since about September [12:14] Better grammar: ScottL permitted me to write the reports since Sept. [12:30] hello [12:30] zequence, dart [12:30] zequence, darktable has been updated. is it possible to backport or sru it ? [12:30] Hiya ttoine [12:30] ttoine, does it fix bugs? [12:31] ttoine: If it's not a matter of a bugfix, we should backport [12:32] http://www.darktable.org/2012/12/released-1-1-1/ [12:32] bug fixes [12:33] ttoine, well then you have to SRU it [12:33] ttoine: The bugs need to be serious in some way [12:33] I can't tell how serious they are, but it seems there are some low level bugfixes there [12:34] Would be good to find some bugs for it in LP [12:35] If found, and they are in deed serious, add all the info for a workitem in the SRU blueprint [12:35] else, the Backport blueprint [12:36] ttoine, wait a minute..... the version of darktable in Raring is still 1.05-1ubuntu1 [12:37] It isn't updated in the main Ubuntu repos [12:37] It was just released yesterday, so it'll take a little time [12:37] First it will be updated in Debian repos [12:38] Then, depending, it will be synced to raring [12:39] If it isn't synced automatically (cause I think we sync from Debian testing, which is in feature freeze, and soon to be released), then we can request a sync from Debian Sid [12:40] yeo [12:40] s/yeo/yep [12:40] Probably things will start to move faster in a month or so. I'm expecting Wheezy to be released any day now, really. [12:41] zequence, I want that freeze lifted too:P [12:41] zequence, what about the sru of sound converter ? [12:41] ttoine: Anyone can do it. I'm doing other things for a while, so I might do it in a couple of weeks, the earliest [12:42] I'm working on my personal project right now [12:43] zequence, what is your personnal project ? [12:43] zequence, ooh [12:43] ttoine: A all in one [12:43] ? [12:43] all-in-one live audio software [12:43] I'm doing it in puredata right now [12:43] Will start a project in C++ next year, but that will take some time [12:44] like ableton live ? [12:44] I haven't tried it, but I doubt it [12:44] smartboyhw: will you be preparing an email for the release team this week? [12:44] not like, but live oriented, I mean [12:44] hi ttoine and zequence :) [12:45] hi scott-work [12:45] smartboyhw: Hello [12:45] micahg: waiting to touch the metas sounds like a good plan [12:45] ttoine: Live orientated, yes. It could beused for creating music too, but the main strength is that you can control any aspect of it live [12:46] I mean, used for creating, and then playing back music, as in contrast for live music [12:47] It's a huge project for me, so I can't actually realize all the features myself very quickly, even if pd is quite fast to code in [12:47] And it gets to a point where you need more muscle, which pd can [12:47] can't offer [12:49] Which release you'd want it to be backported? quantal doesn't make much sense, as it's not LTS. And quite frankly, precise feels very old already. :) [12:55] LTS at least, but as quantal is still the latest, it makes sense to me [12:56] Some people, like holstein, like to keep their LTS for the whole period of 2 years, or longer [12:57] I don't feel we have a "real" LTS for multimedia, but it's still a LTS [13:07] scott-work, yep [13:26] smartboyhw: i want to make a post about the new testing covention. would you please give me a few bullet point items to mention. i will fill in the language around them [13:27] scott-work, uh? [13:27] um [13:27] 1. Alphas and Beta 1 has been abolished by vanilla Ubuntu (aka Ubuntu Desktop/Core) [13:28] 2. Flavours can choose whether they want Alpha 1, Alpha 2 and Beta 1 milestones. [13:30] 3. They can choose to do "cadence" testing instead, no freeze will be taken in these cadence weeks, the daily image builds will continue [13:31] 4. In these "cadence" weeks the main Ubuntu QA Team will test only certain apps (and of course dailies) [14:16] astraljava, I think it is good to have it backported in 12.04 and 12.10. Both are commonly used [14:16] astraljava, or SRU [14:24] ttoine, you can't expect to SRU or backport everything:) [14:28] The only thing we backported so far, I think is qjackctl, cause it should have helped solve a bug [14:28] It's not like we do a lot of backporting [14:28] and no SRU's so far [14:28] As soon as I have time, I will start working on it. We need docs for it [14:29] Should then be simple for anyone to do it [14:29] And actually I don't think backporting to 12.10 should be necessary [14:30] smartboyhw: why is that? [14:30] smartboyhw: part of the process for backporting has been to require backporting to 12.10 to get something backported to 12.04 [14:30] smartboyhw: thank you for the bullet points. i would really like to get a post pushed out to most places about the new testing procedures [14:30] scott-work: I don't think all backports are like that though [14:30] scott-work, oh yeah? [14:31] zequence: i was under the impression that this was required for all bakcports. doesn't mean i'm not wrong though :D [14:31] speaking of cadence testing: has anyone done any testing lately? [14:31] So if one day it gets in the middle of developing 14.04 LTS, I need to backport it to 13.10, then 13.04, then 12.10, then finally to get to 12.04 LTS? [14:31] scott-work, NO:P [14:31] Last cadence week I had been busy with tests [14:31] scott-work: Well, UKT is backporting kernels to LTS, and I'm not actually sure if they ended up in Quantal too. Those are a little different probably [14:32] Will do some testing tmr [14:32] smartboyhw: yeah, 14.04 -> 13.10 -> 13.04 -> 12.10 -> 12.04 [14:32] scott-work, god that is really tiring then [14:32] zequence: good point. the kernel might be very distinctive outlier for the process [14:33] smartboyhw: it is better than before, the backports team has automated many things [14:33] and using prevu or sbuilds for multiple versions is not too bad ;) [14:35] grrr [14:40] i haven't actually used sbuild (micah told me he uses it) but i have used pbuilder quite a bit too [15:12] I use pbuilder-dist normally [15:14] smartboyhw: you can backport straight from 14.04 to 12.04 once 12.10 is EOL [15:14] the idea with backports is to have a supported upgrade path [20:06] zequence: kernels make more sense, as they might include drivers that some hardware really need. But users might be satisfied with older, other software. [20:16] astraljava: It's up to the user if they want to update to backported software, and if anyone feels there's a reason to backport something, I don't see why anyone should object [20:16] First of all, it would be nice if we could make sure this one release was actually bug free (13.04) [20:16] zequence: not possible [20:16] And it would be nice if we could SRU stuff some more [20:17] micahg: Well, on a level which we can control anyway