/srv/irclogs.ubuntu.com/2016/08/12/#lubuntu-devel.txt

tsimonq2wxl: merged! \o/ https://code.launchpad.net/~tsimonq2/livecd-rootfs/lubuntu-next-image/+merge/30120220:08
tsimonq2wxl: one down, one to go :)20:08
wxlcool20:08
wxli didn't even see the response20:08
wxlslangasek got sick of waiting on infinity and just did it? :)20:09
tsimonq2XD yep20:09
wxldaang20:09
wxli have to say it's rather strange20:10
wxladam is usually very on top of things20:10
* tsimonq2 nods20:10
tsimonq2wxl: we even get our own version XD 2.42320:10
wxloooooh20:10
tsimonq2!info livecd-rootfs yakkety20:10
ubot93livecd-rootfs (source: livecd-rootfs): construction script for the livecd rootfs. In component main, is optional. Version 2.422 (yakkety), package size 47 kB, installed size 329 kB20:10
tsimonq2wxl: we just have to wait :P20:10
tsimonq2wxl: what happens when the images are spun up? do you think it would be good to announce something?20:12
wxltsimonq2: get all the testcases taken care of20:12
wxltsimonq2: then start testing!20:12
wxltsimonq2: then finalize the choices on applications20:12
wxltsimonq2: make new testcases20:12
wxltsimonq2: test more20:13
wxltsimonq2: then make it lubuntu :)20:13
wxltsimonq2: we also need to discuss what to do with lxde. i mean we shouldn't really do two images. i don't think. maybe we should have lubuntu-lxde-core/desktop? i don't know. more thinking here.20:14
tsimonq2yeah20:19
tsimonq2wxl: the question is, will LXQt be *default* for 16.10 or will we just have an extra LXQt set of images?20:20
tsimonq2wxl: our plan was the latter, right?20:20
wxltsimonq2: i suspect the latter. we have a lot of work to do still.20:20
wxli think decisions on the applications alone will take us a whole cycle.20:20
wxllike seriously.20:20
tsimonq2yeah20:21
tsimonq2wxl: let me whip up a step-by-step proposal detailing our transition to LXQt. Then, if you like it and the rest of the team likes it, we can refer to it in the future.20:22
tsimonq2wxl: and it will at least be a for-sure roadmap20:22
wxltsimonq2: sounds good. would be nice in the form of a blueprint. there's probably already one there you can just edit20:22
tsimonq2wxl: good idea20:22
wxltsimonq2: i think you should put a date on there for people to refer to. maybe i'm stepping out here, but i'd advise putting 17.10 as the plan.20:23
wxltsimonq2: as i don't necessarily support the notion of releasing new features in an LTS and it's too late for 16.1020:23
tsimonq2wxl: why not 17.04?20:24
wxltsimonq2: new features in an LTS can be a problematic matter. people depend on an LTS being absolutely rock solid. if we're not 100% sure of that, it will create a riot.20:24
tsimonq2wxl: 17.04 is not an LTS...20:25
wxlizznot?20:25
wxloh20:25
wxlit's not :)20:25
wxlyeah right20:25
wxlderp20:25
tsimonq2wxl: 18.04 is, :P20:25
tsimonq2hehehehehehe :)20:25
wxlso yes maybe 17.04 might be good. if we can make it there.20:25
tsimonq2alright I'll plan this out20:25
wxli think it will take us several weeks just to figure out each application. i'm not freaking kidding.20:26
tsimonq2yeah20:26
tsimonq2wxl: so for a work item, do you think it would be smart or excessive to specify a work item for each LXQt blueprint we have?20:34
wxltsimonq2: i kind of think so.20:34
tsimonq2wxl: E: Invalid option. Please specify either "smart" or "excessive"20:35
tsimonq2XD20:35
wxlsmart20:35
tsimonq2k20:35
tsimonq2wxl: is there any specific order we should decide on things, and if so, what do you suggest?20:38
tsimonq2(applications for LXQt)20:38
wxltsimonq2: i'm not sure it matters too much. but if we get the "easy" ones first it might allow us to test them while we work on the "hard" ones (like the browser)20:39
tsimonq2ok20:39
tsimonq2wxl: so there's "Approved" and "Discussion" blueprints20:40
tsimonq2wxl: we only need to decide on "Discussion" ?20:40
wxltsimonq2: yes, but i didn't think we had decided on ANY :O20:40
tsimonq2wxl: https://blueprints.launchpad.net/lubuntu-next20:40
wxlsoooo might want to run those past gilir to be sure20:40
tsimonq2wxl: well obviously LXQt :P20:40
wxlbah launchpad's updating20:41
tsimonq2not for me...20:41
wxlnow it works20:42
wxlugh all those should be renamed to z-series then i guess20:42
tsimonq2wxl: but what about Discussion/Approved20:43
tsimonq2s/Approved/Approved?/g20:43
wxlassume that approved is approved but check with gilir for certainty20:43
tsimonq2ok20:45
tsimonq2wxl: I'm struggling, what should I start with, and given the blueprint's current status, what's the due date20:46
tsimonq2s/date/date?/g grrrrrr20:46
wxllike i said20:47
wxlstart with the easy stuff :)20:47
wxlyour guess is as good as mine, really20:47
tsimonq2well you said browser is hard20:47
tsimonq2¯\_(ツ)_/¯20:47
wxlyeah there's that20:47
tsimonq2wxl: due date?20:48
wxltsimonq2: well, we'd HOPE to do z cycle, eh?20:49
tsimonq2wxl: well are we going to allocate a week or two for each or are we going to set one due date for all?20:49
wxlwell at this point let's make a proposal based on what we think is best20:50
wxli think if we give us a week or so it gives us time to argue it and the ability to focus on just one thing at a time20:51
wxlwe can use it as an opportunity to get the community to engage20:51
tsimonq2ok20:52
wxlwe need to submit the proposal to the community and make sure they accept it, too20:52
wxlso we need to be willing to change it20:52
wxland of course we need gilir's backing20:53
tsimonq2yeah20:54
wxllunch20:57
tsimonq2me too :P20:59
tsimonq2wxl: so Julien responded21:32
tsimonq2wxl: he said: "It was approved at some point, but if you have a better idea, you can add it to the discussion"21:33
tsimonq2wxl: I also asked him about the poll, he said that he can't look now, but he'll let me know later21:33
tsimonq2wxl: slangasek approved and the crontab is in production!21:45
tsimonq2\o/21:45
tsimonq2hey yofel, LXQt image gets generated tomorrow! \o/21:57
yofel\o/21:58
tsimonq2I remember you saying something about that...21:58
tsimonq2thought I would let you know :)21:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!