[00:38] <bluesabre> flexiondotorg: cool
[00:38] <bluesabre> krytarik, Unit193: see any changes that need to be made to the stacked branches? 
[00:38] <bluesabre> I defer to you guys as the core pros
[05:15] <Unit193> bluesabre: http://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/trunk/view/head:/etc/xdg/xdg-xubuntu/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml#L26
[06:56] <Unit193> bluesabre: Also, http://paste.openstack.org/show/M8PGeFpA5F2yqGGfgYSA/ looks nicer.
[07:48] <flexiondotorg> bluesabre, Shall I submit the ubuntu-mate-base branches as merge proposals? They include the Xubuntu BASE changes plus I added xubuntu-base to xenial.
[09:07] <Unit193> bluesabre: While I'm at it, for shimmer-themes: http://paste.openstack.org/show/BKuDWsasvTuQmZOsAQiY
[09:17] <Unit193> http://paste.openstack.org/show/KnQXLadmVDTYUolyhM7h to be more complete, actually.
[11:24] <bluesabre> flexiondotorg: please do. I won't be around during the day, so hopefully you'll be able to field any questions. Please also ping knome and Unit193 since they have a lot of insight of whats going on with it currently
[11:24] <flexiondotorg> bluesabre, Wilco
[11:25] <bluesabre> Unit193: yes, that had also occurred to me just recently (gmb), I'll take care of that and your other suggestions this evening
[11:41] <flexiondotorg> https://code.launchpad.net/~ubuntu-mate-dev/debian-cd/ubuntu-mate-base/+merge/284435
[11:41] <flexiondotorg> https://code.launchpad.net/~ubuntu-mate-dev/livecd-rootfs/ubuntu-mate-base/+merge/284432
[11:41] <flexiondotorg> https://code.launchpad.net/~ubuntu-mate-dev/ubuntu-cdimage/ubuntu-mate-base/+merge/284433
[11:42] <flexiondotorg> Unit193, knome See above ^^^^
[11:42] <flexiondotorg> I've pinged infinity too.
[11:43] <knome> Unit193, can you please review that?
[11:49] <Unit193> 1. They should be stacked merge proposals...  2. That's messing with files of a past release, bad idea.  3. That's not currently going to work for Xubuntu.  4. There's a better way to do that than to hardcode release links for every version of that..
[11:50] <Unit193> That's just of debian-cd.  There's also some oddity in the next one.
[11:51] <Unit193> And by that, it adds both 'ubuntu-mate' and 'ubuntu-mate-base' in one section, and has a merge conflict.
[12:01] <flexiondotorg> Unit193, What merge conflict?
[12:02] <Unit193> The big one that says '>>>> THIS' and '<<<< HERE', I believe.
[12:05] <flexiondotorg> The diff in the MPs do not show any conflicts.
[23:15] <knome> flexiondotorg, did you find the conflict in the diff?
[23:17] <flexiondotorg> knome, I'll look again. I was at work earlier so only glanced.
[23:17] <flexiondotorg> One min...
[23:17] <Unit193> flexiondotorg: w3m -dump https://code.launchpad.net/~ubuntu-mate-dev/livecd-rootfs/ubuntu-mate-base/+merge/284432 | grep -e confli -e '<<<<' -e '>>>>'
[23:20] <flexiondotorg> Yep, spotted it.
[23:26] <flexiondotorg> Conflict sorted.
[23:26] <flexiondotorg> https://code.launchpad.net/~ubuntu-mate-dev/livecd-rootfs/ubuntu-mate-base/+merge/284432
[23:26] <flocculant> the thing is here
[23:26] <flexiondotorg> ?
[23:26] <flocculant> that while this is all well and good 
[23:27] <flocculant> we've been trying to get this running for cycles
[23:27] <knome> flocculant, we're on top of it.
[23:27] <flocculant> and I will not try and force this through via QA - nor will I sign it off when it ends up landing in April
[23:28] <flocculant> it's hard enough to get people - either in testers/users or 'team' to test what we do have
[23:28] <Unit193> flocculant: That's fine, means a jumpstart for 16.10 if nothing else.
[23:28] <flocculant> I will not be forced into a corner on this
[23:28] <Unit193> Honestly, yes.  If it doesn't drop soon, don't officially release the ISOs.
[23:28] <flocculant> Unit193: yep - fine by me :)
[23:29] <knome> totally.
[23:29] <Unit193> Just means I can stop messing with those things.
[23:29] <flocculant> heh
[23:29] <flocculant> don't get me wrong here - I think it is a good idea for sure
[23:30] <Unit193> Points still stand though, wily shouldn't be touched by these merges, and the task right now is still xubuntu-core and we may not have time for migration stuff.
[23:30] <flocculant> but I'm not ticking the box for something we support for 3 years like we've done for things we support for 9 months
[23:30] <Unit193> flocculant: I'm starting to wonder if it were to land right now if releasing would be a good idea, thinking holding off anyway might be good.
[23:31] <flocculant> I'd rather it was rock solid ( or as solid as we get)
[23:31] <flocculant> I'd want to see upgrade results
[23:32] <flocculant> xubuntu-core>x-desktop and images to suit seems like a really sensible thing for us to do 
[23:32] <flocculant> all for it 
[23:32] <flocculant> but not going to be browbeaten :)
[23:33] <Unit193> Xubuntu has gotten far enough away from my ideal I don't even like to re-install in VMs. :/  And yeah, upgrade paths work, or did for wily's upgrade.  I should likely test again.
[23:33] <flocculant> and I assume -core would be a step back towards people *like* you 
[23:34] <flocculant> and was the original impetus
[23:34] <knome> flocculant, i'm about to add a "done" work item for you in the bug blueprint. just let it be; i want to see if that fixes something in the tracker.
[23:35] <knome> flocculant, and done. more specifically, if you look at the burndown, you can see several days with clearly broken bars; this is because the tracker doesn't for some reason process the bugs blueprint
[23:36] <knome> flocculant, you can confirm this yourself by looking at the overview tab in the next 25 minutes :)
[23:36] <flocculant> looking now - and bugs is now missing from overview
[23:36] <knome> so i want to see if adding a work item to the blueprint can fix it
[23:37] <knome> or if it's something else, like something timing out
[23:39] <flocculant> not sure - all I know is that currently bugs is gone from tracker
[23:40] <knome> as long as i have any idea, it's enough ;)
[23:40] <knome> just wanted to explain you why i added that work item for you so you don't go deleting it
[23:42] <flocculant> oh I don't delete other peoples tasks - just add some :D
[23:42] <flocculant> -bugs is an odd one
[23:42] <flocculant> not sure it's trackable really
[23:43] <knome> it's your task :P :P
[23:43] <knome> i couldn't figure out any other work item for the bugs blueprint
[23:43] <flocculant> no - it's my blueprint
[23:44] <flocculant> I rarely fix bugs - just ones on the QA print (testcases)
[23:44] <knome> your blueprint and your task ;)
[23:45] <knome> anyway... just don't touch it
[23:45] <knome> i'll do the further debugging later
[23:46] <flocculant> don't touch -bugs? 
[23:46] <knome> flocculant, that one work item in bugs
[23:46] <knome> ...which you obviously can't see in the tracker right now 
[23:46] <flocculant> I don't - all I do is add stuff an expect LP to magically set to released :D
[23:47] <knome> Work items:
[23:47] <knome> [flocculant] Copy open bugs over from Wily blueprint: DONE
[23:47] <flocculant> I wrote that? 
[23:47] <knome> no, i just did
[23:47] <flocculant> ha ha ha 
[23:47] <knome> as i said, i just created a work item for you...
[23:47] <flocculant> ok :D
[23:47] <knome> ...and i also said DON'T TOUCH IT >:)
[23:47] <flocculant> don't what?
[23:48] <knome> i want to see if that can fix the problem with the trackre
[23:48] <flocculant> :D
[23:48] <Unit193> Don't eat it.
[23:48] <knome> don't touch the tra-la-la
[23:48] <knome> (a good general advice for life if you are lost/unsure)
[23:48] <flocculant> I found touching worked better
[23:49] <flocculant> knome: anyway ...
[23:49] <knome> lol
[23:49] <flocculant> what I am saying is that for some reason -bugs is not showing up on tracker now - is that you?
[23:49] <knome> no, it's something that's failing
[23:49] <flocculant> aah ok
[23:49] <knome> either it's missing it sometimes because LP doesn't give it the information (maybe because there are no work items)
[23:50] <flocculant> well
[23:50] <knome> or because some code times out (because getting the bugs takes some time)
[23:50] <knome> so this is the debug measure number one :D
[23:50] <Unit193> How's the Xubuntu server coming along, anyway?
[23:50] <knome> (eg. where the fence is the lowest)
[23:50] <flocculant> as I said at some point - is there any point in -bugs? is there any point in tracking -bugs? 
[23:50] <knome> i think so
[23:51] <flocculant> who at some point says 'jeez dude fix that ... '
[23:51] <knome> i mean, it's not a list of ALL bugs, it's a list of important bugs we try to fix for the release
[23:51] <flocculant> do I say knome will you please fix the highlight issue for people over 25 :|
[23:51] <knome> you said
[23:51] <flocculant> or do we leave them till loads shout
[23:51] <flocculant> in which case - why track it
[23:51] <knome> well i don't think people over 55 can shout very loud..
[23:51]  * knome hides
[23:52] <flocculant> really? 
[23:52] <flocculant> pm me your phone number :D
[23:52] <knome> lol
[23:54] <knome> so.. i think i got what you were trying to say now
[23:54] <knome> no, nobody should tell anybody to fix the things tracker
[23:54] <knome> *tracked
[23:54] <knome> usually the person who will fix it adds it themself
[23:54] <knome> or somebody from the release/devel team
[23:56] <Unit193> flocculant: ...We/you want the upgrade path for core tested, don't you?
[23:56] <flocculant> well
[23:56] <flocculant> Id' rather people tested things we actually seed currently, but if people can do those extras that's a bonus
[23:57] <flocculant> as you know we don't oush testing it
[23:57] <Unit193> I haven't purged everything we seed on my xenial install!
[23:58] <flocculant> !
[23:58] <flocculant> what?
[23:58] <knome> now i get it
[23:58] <knome> Unit193 usually purges xfce4 too and installs kde
[23:58] <knome> but wants to keep the mouse art
[23:58] <Unit193> >_>
[23:58] <flocculant> knome: now I get the mail and see why you said don't delete the task
[23:58] <knome> :D
[23:59] <flocculant> knome: at least he keeps the art - I just wait for the cat to bring a disembowelled mouse home
[23:59] <knome> the cat is already in the slideshow!