17:03 #startmeeting 17:03 Meeting started Tue Feb 28 17:03:37 2017 UTC. The chair is mdeslaur. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 17:03 17:03 Available commands: action commands idea info link nick 17:03 * stgraber waves 17:03 [topic] Apologies 17:03 No apologies 17:03 * mdeslaur looks around for infinity 17:03 hola 17:04 [topic] Action review 17:04 hrm 17:04 hi infinity 17:04 Oh hai. 17:04 Are you already in progress? 17:04 yep 17:05 we're at the action review, you've arrived just in time :) 17:05 * infinity sits quietly in the corner. 17:05 infinity to follow up with maas SRU exception 17:05 infinity: what's the status on your action items? 17:05 Defer on MAAS, defer (but working on this week) seed/maint-check. 17:06 ack 17:06 slangasek: how about yours? 17:06 defer :/ 17:06 ack 17:06 doko has an agenda item about a freeze exception for python2.6 and openjdk-9 17:07 that should be 3.6 17:08 doko: I'm a bit confused by the request...you want a freeze exception for zesty? 17:08 or do you want to upload what's in zesty to xenial and yakkety? 17:08 no, I want standing exceptions for python3.6 and openjdk-9 in xenial and yakkety 17:08 yes, exactly 17:09 "Not used by any package builds" as in, there aren't any python3.6 extensions built in the archive? 17:09 correct. the only one I plan to do is python3-stdlib-extensions, just adding the tk and gdbm extensions from the standard lib for 3.6 17:10 this will be a space penalty of about 100k for 3.5 users 17:10 This probably technically belongs more to the SRU team to ACK/NACK, but if there are no rdeps in the archive to worry about *and* no regressions in upstream tests, it's likely fine. 17:11 the new SRU process should handle updating to new versions 17:11 I'm fine to follow that one as well. just thought to get approval for the updates here 17:12 Well, a couple of the people here are also there. :P 17:12 And with that other hat on, I'm fine with it, so long as upstream tests don't regress. 17:12 yes, given that the TB previously punted these things to the SRU team as a whole, from my side the preferred process now is: 1) create a wiki page detailing the exception, 2) get the SRU team to review it 17:13 well, xenial has pre-releases ... so until the upload of the first upstream release, these could regress 17:13 sample exception wiki page: https://wiki.ubuntu.com/SnapcraftUpdates 17:14 doko: I get your point, but it also seems like it would be poor form for an upstream test to regress between a pre-release and the final version. :P 17:14 well, then call it snapshots ... these are not even pre-releases ... 17:14 (upstream BEHAVIOURs could change, and I acknowledge that's an issue, but not a huge one for non-default versions) 17:15 but let's see for the first run of the tests ... 17:15 Upstream behaviours changing or not, though, I'm inclined to agree that an LTS should ship a proper upstream release, not a snapshot of who-knows-what. 17:15 * slangasek nods 17:17 ok, next topic? 17:17 [Add new agenda items above this line - include your name] 17:17 Could be contentious. 17:17 hehe 17:17 [topic] Mailing list archive 17:18 rbasak asked on the list if the SRU team can accept NEW packages in stable releases 17:18 Oh, yeah. I didn't see that until just now. 17:19 Notwithstanding Mark's attempt to take a 90 degree turn there, the answer is "it has to be an AA because permissions". 17:19 Which I'd highlight rbasak on, but he's not in here. 17:19 I agree with sabdfl's response as a general recommendation, but there are a few packages there that are required in the archive 17:20 that's been fine in the psst, for some things 17:20 * slangasek nods 17:20 infinity: so there is a permissions issue there? 17:21 mdeslaur: Yeah, you just plain can't manipulate the NEW queue without ~ubuntu-archive. 17:21 Quite intentionally. 17:21 ok, so I guess that answers the question 17:23 infinity: can you tell rbasak? 17:23 oh, you already are 17:24 ok, next topic 17:24 [topic] Community bugs 17:24 no open bugs 17:24 [topic] AOB 17:24 anybody have anything else they would like to discuss? 17:24 * tsimonq2 waves 17:24 Just a quick thing. 17:24 Hey TB, I just wanted to shoot a quick question your way. You may have heard that Lubuntu is thinking about and working on moving to LXQt. Is this something that requires review and acceptance by the TB once we have something to work with, or can we just continue as is? We had a team member that dragged his feet on it and stopped progress, but I'm heading the subproject now, so anything the TB h 17:25 ad to say on it before might be outdated. 17:26 Is the move controversial where the TB needs to get involved? 17:26 We don't need to be involved. Framework changes happen. 17:26 See KDE's move to plasma, etc. 17:26 Not necessarily, but it's essentially an overhaul of the whole DE. 17:26 Like, moving underlying framework. 17:26 infinity: Ok, that makes sense. 17:27 yeah, I don't think there's any sort of charter statement w/ the TB that defines Lubuntu must be "this" :) 17:27 Ok that's cool :) 17:27 if you said "we're going to make Lubuntu's metapackage a clone of Kubuntu's", I would go "um" 17:27 Yeah :P 17:27 but technologies change 17:28 Alright, fair enough. :) 17:28 Thanks for your time. :) o/ 17:28 tsimonq2: thanks! 17:28 Anybody have anything else they would like to discuss? 17:29 tsimonq2: Massive bonus points if you can eliminate --no-follow-recommends while you're at it. 17:29 tsimonq2: It's a huge pain in the butt. 17:29 infinity: Where is this? :P 17:29 mdeslaur: I don't 17:29 tsimonq2: Your seeds don't follow recommends. You're the only flavour that doesn't now. We can discuss out of band another time. 17:30 [topic] Next chair 17:30 slangasek with stgraber as backup 17:30 ack 17:30 that's all folks! 17:30 #endmeeting