=== meetingology` is now known as meetingology === yofel_ is now known as yofel === head_v is now known as head_victim === ronnoc_ is now known as ronnoc === Mkaysi_ is now known as Mkays === Mkays is now known as Mkaysi [15:28] when does the DMB meeting start? [15:55] bencer: 19:00 UTC https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda [16:11] yup, just saw it, thanks tumbleweed, i'll be arround here for my PerPackage application [18:16] \o [18:16] Hello! [18:17] * sbeattie o/ [18:17] at least I don't have to chair this one :) [18:19] or do I? [18:19] * micahg looks around for jdstrand [18:20] micahg: thanks for volunteering :) [18:20] jjohansen: I'm already doing one, what's two? [18:20] micahg: just teasing we should wait for jdstrand even if you were running it [18:21] I know :) [18:22] ok, sorry [18:23] I called the meeting then didn't show up :) [18:23] that is pretty lame [18:23] #startmeeting [18:23] Meeting started Mon May 21 18:23:15 2012 UTC. The chair is jdstrand. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [18:23] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired [18:23] The meeting agenda can be found at: [18:23] [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting [18:23] [TOPIC] Weekly stand-up report === meetingology changed the topic of #ubuntu-meeting to: Weekly stand-up report [18:23] I'll go first [18:23] I am on triage this week [18:24] mdeslaur and I will be finishing the work items review this week [18:24] I will be publishing a libxml2 update today or tomorrow [18:24] I have several pending updates I am working on [18:24] and then an embargoed issue [18:25] I'm hitting small work items here and there, and have started ufw python3 port (over the weekend, but may poke at it some this week) [18:26] mdeslaur is off today. I know he is working on pending updates. he is in the happy place [18:26] sbeattie: you're up [18:26] I'm on community this week [18:26] I've also got a few updates in progress. [18:27] I'm also planning on apparmor work this week. [18:27] I think that's it for me. [18:27] micahg: you're next [18:28] sbeattie: are those apparmor work items, the SRU or some combination? [18:29] jdstrand: SRU + work items, yes. [18:29] I've got patch piloting today, webkit update for precise this week, apparmor profile fixes for Firefox/Thunderbird (SRU for lucid-precise), will do earlier in the week so as not to block sbeattie, and chromium's build is broke ATM, so I need to dig into that as there's a pending update [18:29] awesome, thanks :) [18:30] I guess that's it for me [18:30] I'm in the happy place this week [18:31] It is a short week for me since I'm off Friday [18:31] I took on a sudo update and a sudo feature backport last week, so I've still got my eCryptfs work that I planned on doing last week [18:32] I imagine that getting caught up on eCryptfs bug fixes and the kernel merge window will soak up most of my week. I've got a few bug fixes that have patches written, I just haven't had a chance to test and push them upstream. [18:32] If I do get through all of that early, I've got a pidgin update that is pending in the testing stage. [18:33] (I see a reoccuring theme here :) [18:33] That's it for me [18:33] jjohansen: You're up [18:33] * jjohansen needs to work with sbeattie on releasing apparmor 2.8 this week, there are a couple of minor patches to finish up/test finish. /me also needs to finish going through work items and sticking time estimates on them. After that its back to resurrecting prototypes, dbus, cgroups, env filtering [18:34] I think that is about it jdstrand back to you? [18:34] jjohansen: how did the quantal kernel fixes go? [18:35] jdstrand: oh those look good, thanks for the kick I forgot to push them on the weekend [18:35] * jjohansen will do that first [18:35] * jjohansen got side tracked bug hunting [18:35] cool [18:35] * jdstrand wasn't trying to kick, just curious :) [18:36] nah, is good [18:36] [TOPIC] Highlighted packages === meetingology changed the topic of #ubuntu-meeting to: Highlighted packages [18:36] http://people.canonical.com/~ubuntu-security/cve/pkg/libspring-java.html [18:36] http://people.canonical.com/~ubuntu-security/cve/pkg/python-tornado.html [18:36] http://people.canonical.com/~ubuntu-security/cve/pkg/drupal6-mod-views.html [18:36] http://people.canonical.com/~ubuntu-security/cve/pkg/dimp1.html [18:36] http://people.canonical.com/~ubuntu-security/cve/pkg/pyfribidi.html [18:37] The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so. [18:37] See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved. [18:37] did that slightly out of order... [18:37] [TOPIC] Miscellaneous and Questions === meetingology changed the topic of #ubuntu-meeting to: Miscellaneous and Questions [18:37] There are a lot of merge opportunities for packages listed in http://people.canonical.com/~ubuntu-security/d2u/. Performing these updates is a great way to help Ubuntu and bolster your developer application. [18:37] I also had two other things [18:38] 1. jjohansen has too many work items. once he gives time estimates mdeslaur and I will look at them and then probably discuss as a team how to proceed (eg, Roadmap 'low' ones or reassign some) [18:38] (mdeslaur will lead that effort) [18:39] 2. the desktop team approached me about testing mozilla releases before upstream release day [18:39] (fyi micahg ^) [18:39] I said that this is the plan and that we have work items in place to achieve this [18:40] they do realize this is one day, right? [18:40] micahg: no, test the images for they tag them [18:40] like we said, we build them automatically [18:40] jdstrand: huh? [18:40] when it gets close, we test [18:40] s/for they/before they/ [18:41] yes, I mean there is only 1 work day to do this still (builds are tagged on Friday), yes, it's possible [18:41] eg, the release every 6 weeks [18:41] at 5 weeks, we can have testable packages [18:41] no, we can't [18:41] why? [18:41] they push out fixes in the final week [18:41] * jdstrand nods [18:41] the beta PPA is for people to test [18:42] the beta ppa is on 15 or something now, no? [18:42] ideally, people are running the beta and reporting issues along the way so my final testing is basically a rubber stamp [18:42] test = look at 20 screenshots [18:42] if I catch anything in my testing, it's too late anyways [18:43] yeah, once we have the automated testing screenshots, I think I'll run that against the beta PPA weekly, that should improve things [18:43] s/improve/catch things earlier/ [18:43] I would still argue that testing twice, once a week before and one day of would still be better than testing a day or two after [18:43] even if it is not automated yet [18:43] but anyway [18:43] sure, I can QA the beta the week before [18:44] in this particular instance, that asked if we could test early (ie, twice) to catch anything for the point release [18:44] micahg: can you coordinate that with the desktop team-- ie the exact timing) [18:44] the point release is in 3 months, we'll have 2 more releases before that [18:45] micahg: you might also mention the beta ppa-- I mentioned it, but they ones I saw were way past '13'-- they were on 15 [18:45] 12.04.1 will get FIrefox 14 [18:45] jdstrand: is there ay possibility of getting QA resources to assist? [18:45] micahg: yes, I know-- but they asked for this to happen in a couple of weeks. can you coordinate/clarify what they need? [18:46] * jdstrand is trying not to be the middle-man [18:46] jdstrand: sure, who's the contact for that? [18:46] seb128 asked me-- I imagine either him or chris [18:46] sbeattie: I asked QA a while back to start running QRT, maybe I can get them to review the results more frequently once we have the screenshotting capability [18:47] sbeattie: well, now that we are on rapid release, we don't have the big call for testing-- everything is just a 'regular' update [18:47] jdstrand: I think he meant help with testing :) [18:47] and all they are asking for is us to do our regular testing by some point [18:47] jdstrand: what micahg said, not just calls for testing. [18:47] (see last statement) [18:48] and since that regular testing is something we should be doing anyway, I said 'ok' [18:49] anyhoo, this is a little more complicated than it has to be. desktop team needs tests to happen be a certain date. if micahg can ascertain the date and do the testing, that would be great. everything else is executing our work items [18:52] I think that is it [18:52] Does anyone have any other questions or items to discuss? [18:57] #endmeeting === meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology [18:57] Meeting ended Mon May 21 18:57:23 2012 UTC. [18:57] Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-21-18.23.moin.txt [18:57] Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-05-21-18.23.html [18:57] mdeslaur, sbeattie, micahg, tyhicks, jjohansen: thanks! [18:57] thanks jdstrand [18:57] jdstrand: thank you! [18:57] thanks jdstrand [18:57] thanks! [19:00] ah, one more thing: [19:01] Felix Geyer (debfx) provided a debdiff for pidgin-otr (LP: #1000363) [19:01] Your work is very much appreciated and will keep Ubuntu users secure. Great job! :) [19:01] !dmb-ping [19:01] bdrung, cody-somerville, Laney, micahg, barry, tumbleweed, stgraber: DMB ping [19:02] * stgraber waves [19:02] hi [19:02] hi all, bencer here for the DMB meeting [19:02] we need one more for quorum [19:03] * bdrung waves [19:04] #startmeeting [19:04] Meeting started Mon May 21 19:04:24 2012 UTC. The chair is micahg. Information about MeetBot at http://wiki.ubuntu.com/meetingology. [19:04] Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired [19:04] #topic Review of previous action items === meetingology changed the topic of #ubuntu-meeting to: Review of previous action items [19:05] I don't seem to recall any that need discussing and the wiki isn't showing any either [19:05] anyone have anything to discuss WRT this? [19:06] * micahg takes that as a no, moving on [19:06] I think we took care of all past actions during the last meeting, that's unless we count the recuring action for cody-somerville to write that wiki page on testimonials, but this one has been there for more than 6 months now :) [19:06] * micahg also has a recurring action item that he'll get to next week [19:06] #topic Cesare Falco PPU === meetingology changed the topic of #ubuntu-meeting to: Cesare Falco PPU [19:07] cfalco: are you around? [19:07] hi all! [19:07] #link https://wiki.ubuntu.com/c.falco/DeveloperApplication [19:07] * tumbleweed looks for an IRC log for the previous conversation [19:08] #link http://irclogs.ubuntu.com/2012/04/23/%23ubuntu-meeting.html#t19:35 [19:08] ah, thanks [19:11] cfalco: so, continuing from last time, if a few files moved from one package to another, let's say mame -> mame-common, what changes would need to made to the packaging to accommodate this [19:11] *to be made [19:11] depends [19:11] micahg: your question is a reminder for me for the vlc PPA package. ;) [19:12] @micahg: what's vlc? :o [19:12] cfalco: Error: "micahg:" is not a valid command. [19:12] cfalco: vlc is a package that bdrung maintains in Debian [19:12] micahg: what's vlc? :o [19:13] ah ok :) [19:13] mame should depend on mame-common [19:14] and maybe also a breaks or something, or dpkg could have trouble in removing mame before installing mame-common [19:14] but before doing anything I would check the debian policy ;) [19:14] let's assume you already had mame and mame-common, and so mame was already depending on mame-common [19:15] but you moved a file from mame to mame-common [19:15] I guess replace is only suitable when *all* files get moved [19:15] correct? [19:17] replaces isn't what you think it would be [19:19] cfalco: do you know where to look up these things? [19:19] micahg: ok, so I assume I should use replace? [19:19] micahg: http://www.debian.org/doc/debian-policy/ch-relationships.html === jalcine is now known as Jacky [19:21] well, I'd like you to tell me the changes :) (and that's the right link) [19:22] ok both, replaces: and breaks: :$ [19:22] and we were assuming depends: from the start [19:23] I must admit I thought replaces: is only suitable when *all* files are to be replaced [19:23] for which packages and are they versioned? [19:24] cfalco: yeah, replaces is slightly counterintuitive from the non-packaging definition [19:25] micahg: the version I'm packaging... i.e I'm packaging mame-common 2.0: -> Replaces: mame (<< 2.00) [19:25] where << is strictly less than iirc [19:25] cfalco: cool, thanks [19:26] cfalco: which tools will you use to sync a package from Debian to Ubuntu? [19:27] bdrung: I guess it's syncpackage, but I still have to read all the documentation on this [19:28] cfalco: why not just use dput? [19:30] bdrung: I see it preserves the checksums and I'm not sure dput would do that [19:31] cfalco: dput can preserve the checksums, but it opens a window for errors. that's why using syncpackage is recommended. [19:31] cfalco: are you subscribed to ubuntu-devel-announce? [19:32] not yet [19:32] please do, it's where freezes are announced [19:32] (amongst other useful things) [19:33] tumbleweed: I'll do it for sure :D [19:33] cfalco: i see that mame is out of sync b/w ubuntu and debian. what are your plans for sync'ing them and how would you go about doing that? [19:34] barry: mame 0.146 has just been released today, it will mark the first release synced from Debian [19:34] \o/ [19:35] cfalco: cool. do you foresee any reason for ubuntu to carry deltas from debian in the future? [19:36] barry: no, I'm working with the debian maintainers and we will make things suitable for both distros as much as we can [19:36] cfalco: great, thanks [19:37] cfalco: btpd is only available in Ubuntu. are there plans to get it into Debian? [19:38] bdrung: no at present, but I'd like to. I find it very useful, but it seems nobody else is interested. [19:39] cfalco: how did you come to the conclusion that nobody is interested? [19:40] bdrung: is the utnubu team still active? maybe I could find some help from them. [19:40] bdrung: I have no feedbacks in ubuntu, let alone debian... ;) [19:41] cfalco: there are a bunch of ubuntu people who are DDs. I'm working on a list that makes them easy to find [19:41] tumbleweed: cool! is it in the wiki? [19:41] cfalco: dunno if utnubu is still active, but debian mentors is up and running. [19:42] DEX has superseded utnubu for the most part AIUI [19:42] Ubuntu DEX to be more specific [19:42] yeah, you don't need ubuntu-developers to sponsor it, any debian sponsor will do. But obviously ubuntu people have extra motivation to help us get ubuntu packagesinto Debian [19:43] the list is here, but doesn't show who the DDs are yet http://people.ubuntuwire.org/~stefanor/debian-ubuntu-developers/ [19:44] I see micahg is a DEX member, right? :) [19:44] yeah, with no Debian uploads [19:44] * micahg needs to fix that [19:45] cfalco: are you familiar with how to request a freeze exception and when it's appropriate [19:46] micahg: i did it once for btpd, for a minor fix in a configuration file iirc [19:47] it was long ago, I'd need to check the wiki :$ [19:47] cfalco: ok, you know where that is? [19:48] micahg: https://wiki.ubuntu.com/FreezeExceptionProcess [19:48] cfalco: great [19:48] ok, any more questions? [19:48] yes [19:48] cfalco: what changes with DIF? [19:50] bdrung: after dif packages with differences between ubuntu and debian must be imported explicitly by a developer [19:51] cfalco: are package with differences between ubuntu and debian synced automatically before the DIF? [19:52] bdrung: I guess no, as the version is different [19:53] I mean the 0ubuntuNN suffix [19:53] cfalco: then i have to ask again: what is the different before and after the DIF? [19:54] because packages with 0ubuntuNN needs to be always synced manually [19:54] (or merged) [19:55] bdrung: I guess it's like the "main" freeze [19:56] I mean, before dif you sync the package [19:56] after dif you ask something like a freeze exception [19:56] no: https://wiki.ubuntu.com/DebianImportFreeze [19:57] new versions of packages will be automatically imported from Debian where they have not been customized for Ubuntu [19:57] that's before the DIF and it needs to be done manually afterwards [19:57] bdrung: so no syncpackage is required on a non-customised package before dif? [19:57] you are still allowed to sync packages with new features after DIF [19:58] cfalco: exactly [19:58] bdrung: great [19:58] that is unless you have an immediate need in the devel release (bug fix needed immediately, FTBFS, NBS) [19:58] and should a new version be put in debian after dif I'll have to manually sync it in ubuntu, right? [19:58] yup [19:59] ok, we need to vote [19:59] bdrung, micahg, tumbleweed: thanks! [19:59] #voters bdrung, cody-somerville, Laney, micahg, barry, tumbleweed, stgraber [19:59] Current voters: Laney barry bdrung cody-somerville micahg stgraber tumbleweed [20:00] posh [20:00] #vote Cesare Falco PPU for btpd and mame [20:00] Please vote on: Cesare Falco PPU for btpd and mame [20:00] Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me) [20:00] +1 [20:00] +1 received from Laney [20:00] +1 [20:00] +1 received from tumbleweed [20:00] +1 [20:00] +1 received from barry [20:00] +1 [20:00] +1 received from bdrung [20:01] +1 [20:01] +1 received from micahg [20:01] stgraber: ? [20:01] +0 [would have liked to see better pre-meeting knowledge of the Ubuntu processes and freezes] [20:01] +0 [would have liked to see better pre-meeting knowledge of the Ubuntu processes and freezes] received from stgraber [20:02] #endvote [20:02] Voting ended on: Cesare Falco PPU for btpd and mame [20:02] Votes for:5 Votes against:0 Abstentions:1 [20:02] Motion carried [20:02] cfalco: congratulations [20:02] thanks anyone! :) [20:02] #action stgraber to give cfalco PPU for btpd and mame [20:02] ACTION: stgraber to give cfalco PPU for btpd and mame [20:02] #action micahg to add cfalco to ubuntu-dev [20:02] ACTION: micahg to add cfalco to ubuntu-dev [20:04] #topic PPU for Jorge Salamero Sanz === meetingology changed the topic of #ubuntu-meeting to: PPU for Jorge Salamero Sanz [20:04] #link https://wiki.ubuntu.com/JorgeSalamero/PerPackageDeveloperApplication [20:04] cfalco: one last thing, just want to encourage you to come to #ubuntu-motu with any questions [20:04] micahg: action done [20:04] stgraber: thanks [20:04] bencer: can you introduce yourself? [20:05] hi all [20:05] I'm Jorge Salamero aka bencer [20:05] micahg: sure, thank you! :) [20:05] I'm a DD since a few years already, now I'm working on eBox Technologies, the company behind Zentyal (previously eBox Platform) [20:06] I'm applying for PerPackage rights to upload zentyal packages to Universe, eventually main if we make it [20:06] I've been working on the packages, although is jacalvo, the product manager the one making the releases [20:07] and I also have pushed all the needed deps via Debian and then requesting the sync [20:07] I was in Oakland on the UDS, holding 4 sessions on Zentyal / Ubuntu integration [20:08] and seems that we made a good progress making people aware of Zentyal and for Q we have some blueprints we are going to work together with Edubuntu ppl [20:08] I think that's it :) [20:10] micahg: any questions? [20:11] bencer: hi. i noticed that zentyal is only in ubuntu currently. you're a dd - why isn't zentyal in debian? [20:11] barry: zentyal uses some ubuntu specific stuff [20:12] like upstart, appamor and specially the versions of the packages [20:12] i always say that would take 3-4 days work to make it fully working on debian [20:12] upstart and apparmor are in Debian (not entirely functional yet, but that's a WIP) [20:12] but we dont have the time [20:12] i know, its wip [20:13] once they are updated and available and working, would you then be interested in pushing this work up? [20:13] but probably the biggest issue is that our versions depend on ubuntu versions [20:13] bencer: but if someone contributed changes to make it possible, would you sponsor it into debian? [20:13] sure [20:13] we are working a lot on getting more contributors [20:14] I'm glad to see the dependencies at least pushed to Debian which lays the ground work for someone to do the last mile bit [20:14] due the philosophy of zentyal, most of our community are sysadmins with not developers/integrators [20:14] micahg: yes, we always do that, we want to contribute as much as we can to debian/ubuntu [20:14] we have sent some patches to asterisk [20:15] filled bugs to launchpad on per daily basis (almost) :) [20:15] and some contributions to samba4 are on the way [20:16] bencer: I seem to recall that the zentyl packages have only had a single upload so far [20:16] which required a bit of back and forth for sponsorship [20:16] are you confident in yoru ability to maintain them from here? [20:18] ok, sorry guys, i had some problems with the charger, im back [20:18] tumbleweed: what happened is that in the past, was a volunteer/unofficial upload [20:19] what has changed since then? [20:19] now one of our project goals is to get the best integration with the ubuntu ecosystem we can get [20:19] so we have official resources=time, to invest in ubuntu [20:19] right [20:19] also this is not a new upload, but a rename of the packages [20:19] in the past the packages were ebox-* [20:19] now they are zentyal-* [20:19] yeah, I seem to recall that Breaks + Replaces was missing in the rename [20:20] yeah, that was fixed on time :) [20:20] bencer: yes, but you also only had one round of the ebox packages, and that was a year previous [20:20] I assume we can expect some more frequent uploads now? [20:20] yes, i've not too much to say about the previous packages [20:20] tumbleweed: yes, i can show you more than words [20:21] bencer: you are subscribed to ubuntu-devel-announce? [20:21] http://git.zentyal.org/zentyal.git/commit/ac1c7717efdd52cb763ec55e8c10b61301a8b053 [20:21] this commit fixes one of the reported issues on launchpad [20:22] to the packages we uploaded [20:22] we are going to discuss if it should go to SRU or not [20:22] tumbleweed: sure [20:22] also security, -server, -edu and -doc [20:22] good [20:23] since we have a chapter in the ubuntu-server-guide [20:23] bencer: why are the packages all native packages? [20:24] bdrung: this has been a hot point [20:24] we consider zentyal as an ubuntu only software [20:24] is tied to ubuntu software like i said (upstart, apparmor, etc) [20:24] and is tied to specific versions included in ubuntu [20:25] our configuration templates are tested with the versions on ubuntu [20:25] other packages are tied to upstart and apport too, but aren't native [20:25] not with any squid or dansguardian versions for example [20:25] bdrung: imho we can find reasons to push in both directions, native and non-native [20:26] according to the policy, we define ourselves as native, and we are native [20:26] true that we could be non-native [20:26] but current status is as it is [20:26] maybe the day someone contributes debian support, we can evaluate going to non-native [20:26] but with more maintenance power it could become non-native with supporting other distros? [20:26] but at the moment, we only run on ubuntu, so we are native :) [20:27] could be, but the company is not interested in supporting other distros [20:27] so that would be community contributions [20:27] you wrote that you dislike when Debian and Ubuntu packaging are different without justification [20:27] do you have examples for it? [20:28] in the past asterisk, at the moment i dont know the status [20:28] i think they are the same now [20:28] no, we still have a diff [20:28] if eventuall we want zentyal in debian [20:29] having the packages we use, be as similar as possible, would help a lot [20:29] but again, i dont see debian support close, maitenance of it wouldnt be easy neither [20:29] as the release cycles of both doesnt fit [20:29] bencer: any ideas to reduce the amount of differences? do you work on getting the differences reduced? [20:30] bdrung: our first goal was to get the zentyal packages on a good shape in precise [20:30] now our goal is going to be to contribute patches to make all the services we depend on, use upstart [20:31] also some contributions are in the roadmap, like sssd support on auth-client-config [20:31] reducing the differences was a personal thing, more than something scheduled on the roadmap [20:32] bencer: are you aware of the various freezes in Ubuntu and how they might affect your ability to upload? [20:33] yes [20:33] micahg: we already had to deal with that [20:33] zentyal packages got uploaded with a feature freeze exception [20:34] bencer: ok, what about the milestone freezes, if for example, edubuntu would have an image with zentyal on it [20:34] yup, our internal planification is done with the wiki page of release timeline next to us [20:35] https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule [20:36] so, if zentyal were on and Edubuntu image, would you be able to upload a new version on June 6? [20:36] s/and/an/ [20:36] yup, actually we plan to upload something close to our zentyal 3.0rc [20:37] i already discussed this with jacalvo, in charge of the releases [20:37] but as this schedule was published a few days ago, still we dont have detailed plan [20:37] but we are totally aware of the dates [20:38] bencer: I'm not so sure :), June 6 is relevant for uploads on images, do you know why? [20:38] yeah we talked about it in the edubuntu session, so the actual upload after the freeze would just be a minor bug fix upload [20:39] micahg: probably to deal with images sizes?, but i dont know exactly why [20:40] having upload privileges will help to be faster uploading packages [20:40] bencer: for alphas, the archive is soft frozen, any uploads for sources that affect images needs to be coordinated with teh release team [20:40] also rebuilding all the images take time, so a change in on of the packages forces a complete rebuild [20:41] right [20:41] so, given that, would you still upload a new version on June 6? [20:42] only if a critical bug is found that forces us to do so [20:42] but will try our best to have everything before ready [20:42] bencer: what would you do if you found a bug that needed to be uploaded? [20:42] also i cound with the support of more experienced people like highvoltage or jamespage (or last sponsor) [20:42] count* [20:43] so we will be asking for advice to them when in doubt [20:43] well, as this will be because edubuntu, first of all i will discuss about the bug with edubuntu people [20:44] and if we dont have any other option that request a new upload [20:44] file a bug and explain the release team the situation [20:44] bencer: are you subscribed to ubuntu-devel-announce? [20:45] yup [20:45] all announces about release dates are sent there [20:45] bencer: do you envision more people wanting to apply for upload rights to these packages? [20:46] jacalvo in the future too, so i'm not the only one, in case i'm super busy with something else [20:46] also i plan to ask for motu once i'm more experienced with the ubuntu workflows, which are different to the debian ones i'm used to and i know well [20:46] ok, I'd like to create a packageset with those packages in it then [20:47] this way we will be able to work more on depends [20:47] but that will be after we start contributing patches to these packages, doesnt make sense to do it now [20:47] bencer: do you have a description we can use for that packageset to determine what belongs in it? (is zentyal-* sufficient?) [20:47] there is an other one [20:47] (we still have to vote on the packageset and your rights as well) [20:48] zbuildtools does not match zentyal-* [20:48] bencer: right, I see zbuildtools as well (I mean for future additions that won't require coming back to the DMB to be added) [20:48] zbuildtools [20:48] +zentyal-* [20:48] ok [20:49]