16:02 #startmeeting 16:02 Meeting started Tue Jul 8 16:02:55 2014 UTC. The chair is infinity. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 16:02 16:02 Available commands: action commands idea info link nick 16:02 Sure. 16:03 #meetingtopic Tech Board Meeting 16:03 The docs lie, apparently. 16:03 '#topic' ? 16:04 but it may not work for changing the channel topic, I'm not sure 16:04 #topic Tech Board Meeting 16:04 * infinity shrugs. 16:04 yeah, probably not wired up correctly for use on this channel 16:04 but we can all use our imagination :) 16:04 We'll live. We have almost nothing to discuss, AFAICT. 16:05 Looks like it's not on the ACL 16:05 I don't think that's true 16:05 there are two open questions on the list 16:05 #topic Mailing List Review 16:05 So, which one first? 16:05 juju was first chronologically 16:05 are there? I only have the juju SRU policy 16:06 IIRC 16:06 juju and xfce? 16:06 pitti: xfce MRE 16:06 ah 16:07 So, stgraber and I spent a fair bit of time with the juju team helping them draft their initial policy. 16:07 ah, xfce was actually first 16:07 but either way :) 16:07 * slangasek nods to infinity 16:07 I'll admit that I didn't read what went to the list to see how it matched what we asked them for. 16:07 I was curious what the answer to pitti question was going to be 16:08 ah, I also looked at some initial internal google doc before 16:08 it was really verbose, but the gist of what I'm interested in (which combinations of existing installs they test, and how) was a bit terse 16:09 Should we take some action items for more than two people to read their proposal and get back to them? :P 16:09 I'm in favour of it, in spirit, I just want to make sure it's done sanely in practise. 16:09 I read the mail response as well, and it did resolve two of my original concerns, just not expanding on how they test compatiblity with older versions 16:09 ok, I'll take a look and respond on the list 16:09 right, me too 16:10 #action mdeslaur and infinity to read more into the juju stuff and actually reply 16:10 * meetingology mdeslaur and infinity to read more into the juju stuff and actually reply 16:10 I mean, it's universe and I suppose won't be supported for the full lifetime of trusty anyway, but it makes a nice example how SRUs can look like 16:10 pitti: "supported" is meaningless when Canonical is encouraging people to use it. 16:11 pitti: No one (not even our employer) gets to get away with "we tell people to use it, but don't play by the rules because it's 'just universe'" 16:11 infinity: right, but I mean trusty's go toolchain might stop being able to build juju well before the 5 year life time is over 16:12 anyway, different topic (and that one was discussed to death already) 16:12 pitti: Staying with the trusty toolchain was one of the criteria for this. 16:12 pitti: Until 16.04 is out, that is. 16:12 so, of course this is mostly a question of "how", not "if" 16:12 especially software like this that is typically used in enterprise deployments, rather than some universe desktop mp3 tagger or something 16:12 #topic xfce MRE 16:12 sorry I'm late. here now 16:12 hi kees 16:12 hey kees 16:12 kees: *wave* 16:12 \o 16:13 xfce package list looked reasonable 16:13 does anything else use the unity-gtk greeter? 16:13 agreed: xfce looked fine to me 16:13 sorry, lightdm-gtk-greeter 16:13 xfce-core list, yes; I just wonder what's teh "exception" part there, i. e. what kind of bugs get fixed which don't already fall under the normal SRU policy 16:13 I'm not just interested in upstream's practises here, but also who will be doing these MRE uploads, and how they'll be tested in Ubuntu, I think. 16:14 Task: xubuntu-desktop, xubuntu-core, mythbuntu-frontend, mythbuntu-desktop, mythbuntu-backend-slave, mythbuntu-backend-master, lubuntu-core, ubuntustudio-desktop-minimal, ubuntustudio-desktop 16:14 * infinity was recently burned by the requestor's SONAME change without package name change, and is now wary. :P 16:14 ^ lightdm-gtk-greeter 16:15 yeah, Noskcaj isn't yet an ubuntu dev/uploader 16:15 (but that means that there's another sanity check through the sponsor queue) 16:15 those all happen to use xubuntu as their desktop environment, right? 16:15 so that implies we probably shouldn't bless this for lightdm-gtk-greeter without checking with the other flavors 16:15 mdeslaur: Not lubuntu. 16:15 mdeslaur: lubuntu is lxde, not xfce 16:16 ah, ok, so yeah, I wouldn't include lightdm-gtk-greeter without checking with them 16:16 mdeslaur: lubuntu is LXDE, not sure about mythbuntu 16:16 mythbuntu inherits the desktop bits from one of them but I forget which one - I think xubuntu 16:16 XFCE, so yeah 16:18 the one thing that concerns me in all of this is the emphasis on manual testing 16:18 So, are we generally okay with everything on that list except that? 16:18 manual testing + an upstream policy on not introducing features 16:18 Not that I think that one matters, since its upstream isn't XFCE. 16:18 I don't think the "xfce-related" category should qualify 16:19 I agree; core+other looks ok to me 16:19 yeah, I think we shouldn't allow anything in the xfce-related category either 16:19 since "related" in no way implies they're covered by the xfce upstream microrelease policy 16:19 there seems to be stuff that are used by other environments in there 16:19 supposedly quite similar to the GNOME/KDE updates (which also have manual testing for the most part) 16:19 pitti: but a lot of build-time test suites, I think? 16:20 slangasek: for the libs, not for the pixelish bits 16:20 fair point 16:20 e. g. exo has tests, but not thunar 16:21 I'm fine with a provisional MRE for the first two blocks (i. e. not the "related" ones), and we can see how it goes 16:21 I'm happy enough with trusting upstream here, for the upstream-derived bits and NACKing the "related". 16:22 same with me 16:22 pitti: oh, I meant: don't KDE and GNOME upstream have build-time test suites 16:22 and during that, the test case should cover the most important use cases of said package 16:22 #vote Allow XFCE provisional MRE for all but the "Related" list: 16:22 Please vote on: Allow XFCE provisional MRE for all but the "Related" list: 16:22 Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname) 16:22 +1 16:22 +1 received from infinity 16:22 i.e., my question is is the XFCE upstream testing really on par with what we expect 16:22 slangasek: they do, but again pretty much the same: libs have fairly good coverage, GUI apps not 16:22 ok 16:22 +1 16:22 +1 received from slangasek 16:22 +1 16:22 +1 received from mdeslaur 16:22 +1 16:22 +1 received from pitti 16:23 #endvote 16:23 Voting ended on: Allow XFCE provisional MRE for all but the "Related" list: 16:23 Votes for:4 Votes against:0 Abstentions:0 16:23 Motion carried 16:23 THat's looks quorumish. 16:23 pitti: Want to relay to the list? 16:23 infinity: can do 16:23 #action pitti to relay XFCE vote results to the list 16:23 * meetingology pitti to relay XFCE vote results to the list 16:23 (and to wiki, implied) 16:24 #topic Community bugs: (none) 16:24 #topic Next chair 16:24 me, yes? 16:24 stgraber, unless he disappears again, then kees? 16:24 would be kees 16:24 stgraber is out next time too 16:24 Oh, sneaky Stephane. 16:25 kees it is. 16:25 whee 16:25 #topic AOB 16:25 Anything else? 16:26 Going once. 16:26 Twice. 16:26 #endmeeting