[03:20] <bluesabre> http://www.markshuttleworth.com/archives/1496
[07:11] <flocculant> bluesabre: you preferred alleviate then :p
[10:02] <bluesabre> flocculant: your word was much too rich for my vocabulary
[11:09] <flocculant> bluesabre: :)
[11:10] <flocculant> I guess we should let people know about the gpg sig thing somehow
[19:03] <Nairwolf> hi ;) Have you some feedback about 16.04 ? 
[19:10] <Nairwolf> What's next ? How can I be more involved ? 
[19:11] <flocculant> Nairwolf: involved in what? 
[19:13] <flocculant> not much will be going on for a bit 
[19:14] <flocculant> if you want to be more involved in testing things - then I can help with that
[19:14] <Nairwolf> I would like to be more involved in development (and I think I will send soon an email to bluesabre about that), but today, I would like to know what would be the next things to do for Xubuntu
[19:14] <flocculant> for xubuntu today - nothing :)
[19:15] <Nairwolf> ok, but, I know usually soon after a release they are an Ubuntu summit with a lot of talks. Do you know when it is ? 
[19:15] <flocculant> beginning of May I think
[19:16] <flocculant> don't much notice that tbh - we don't participate there
[19:16] <Nairwolf> yes, but that was like that I was informed about the snappy package when it was announced some time ago
[19:17] <flocculant> mmm
[19:17] <Nairwolf> it interesting some times to hear what would be the future for Ubuntu and others flavours
[19:17] <flocculant> :)
[19:18] <flocculant> 3rd to 5th May 
[19:25] <Nairwolf> Thanks ;)
[19:31] <Nairwolf> So when you will need to do new testing ?
[19:42] <flocculant> Nairwolf: when there's something to test
[19:45] <Nairwolf> ok
[19:45] <Nairwolf> and are you planning some meetings with the Xubuntu team ? 
[19:46] <flocculant> Nairwolf: they will be planned yes
[19:46] <flocculant> Nairwolf: not sure how we'll work QA this cycle just yet
[19:47] <flocculant> might not use package tracker
[19:47] <Nairwolf> oh, why ? 
[19:47] <flocculant> might try and push using dev ppa's with xenial for longer
[19:47] <flocculant> might do all sorts of things
[19:47] <flocculant> we do that more for LTS than other versions
[19:48] <flocculant> anyway - all undecided at the moment
[19:49] <Nairwolf> ok
[19:50] <flocculant> hang about - check the mailing list :)
[19:50] <Nairwolf> I think it would be more efficient to know 'when' we can make package test. I suppose if there is a dev ppa, we can know when there is a new package version, and then report tests on bugtracker. 
[19:50] <flocculant> well 
[19:51] <Nairwolf> Maybe I wrong, but for this release, I thought there are several test report with different package version. 
[19:51] <flocculant> that's exploratory testing - fancy name for using dev versions all the time
[19:51] <flocculant> anyway - been a long few days - not thinking about it currently :)
[19:52] <knome> if we knew when new package versions are released we'd be magicians
[19:52] <Nairwolf> yes, you should be tired. 
[19:52] <flocculant> hi knome 
[19:52] <knome> hello flocculant 
[19:52] <Nairwolf> knome: my english is so bad... I didn't want to say that like that ! 
[19:53] <Nairwolf> I wanted to say in this order : You see a new update of Orage for example, or Thunar, and you go report your tests on the bug tracker. 
[19:53] <knome> but that's what you can do already
[19:55] <knome> by doing scheduled package testing sprints, we aren't encouraging anybody from testing those packages outside the sprints
[19:55] <knome> we are just making sure everything gets tested at all
[19:55] <Nairwolf> yes, but on http://packages.qa.ubuntu.com/ you can't distinguish the version which is be tested
[19:56] <knome> no, but why should you?
[19:57] <Nairwolf> Maybe there is something I don't understand.... Look this page : http://packages.qa.ubuntu.com/qatracker/milestones/350/builds/105268/testcases/1559/results
[19:57] <Nairwolf> It's bug report for Catfish
[19:57] <knome> testcase, you mean
[19:57] <Nairwolf> But it's really difficult to to know if the first test report is for the same software version of the last test report
[19:57] <Nairwolf> (yes, testcase, sorry)
[19:58] <knome> explain me why that is important?
[19:59] <Nairwolf> At the beginning, just after a new release like 16.04, imagine a bug has been found on Catfish. Some testers report it on a testcase like that. 
[19:59] <Nairwolf> Few months later, the bug is solved and corrected. It's really instersting to test catfish right now (in order to know if the bug is still present). 
[20:01] <Nairwolf> some testers say "ok, the bug is solved, I can't reproduce the bug anymore, great job developpers ;)". But few days later, someone like me (probably a little bit stupid) who hasn't updated catfish could report the same bug already solved
[20:01] <Nairwolf> I hope it's clear...
[20:01] <knome> well, the last part isn't
[20:02] <knome> i mean i don't understand how it's a problem that the tracker doesn't show the version number
[20:02] <Nairwolf> oh, you right, this testcase is supposed to be used with the daily build, right ? 
[20:02] <knome> indeed
[20:03] <Nairwolf> ok, I see
[20:03] <knome> what the tracker could actually do (ping flocculant) is to show a different icon for bugs that are "fix released"
[20:03] <knome> that would likely make it easier to browse the bugs that are supposed to happen still
[20:04] <Nairwolf> in this case, it would be interesting to be informed that there is a new version of package X and testers could be more focused on this package
[20:04] <Nairwolf> yes, you right knome ;)
[20:05] <knome> i agree that "new versions" aren't very visibly listed anywhere, but i think flocculant is doing a pretty good job of mentioning about worthwhile new versions
[20:05] <knome> it's not like it happens all the time and it slips from the team
[20:05] <knome> we usually have a good idea about new major versions, and they are communicated on the mailing list too
[20:06] <flocculant> knome: the tracker(s) do have a different colour for fixed bugs
[20:07] <knome> right...
[20:07] <knome> wasn't that critical/non-critical before?
[20:07] <Nairwolf> Oh, yes, I think flocculant is doing a good job, and I didn't want to critize him
[20:08] <flocculant> knome: slightly different issue there - doesn't matter *where* on any tracker a bug is listed - if it is Fixed, it's Gold(ish)
[20:08] <knome> ok
[20:08] <flocculant> both obviously
[20:08] <knome> :)
[20:09] <flocculant> all that aside - I'm not convinced yet that we'll be using package this cycle
[20:09] <knome> ackety ack
[20:09] <flocculant> if this cycle follows others then participation will be loooooow
[20:09] <flocculant> if it turns out it's not - we can boot package tracker up 
[20:09] <knome> especially as it's lts+1..
[20:09] <flocculant> yup
[20:10] <knome> you mean yuppety yup?
[20:10] <flocculant> :D
[20:11] <flocculant> frankly I think between now and the .04.1 and wherever we are with 16.10 - thunar will get the lion's share of testing ;)
[20:12] <Nairwolf> flocculant: why are you saying that participation will be looooooooow ? 
[20:12] <flocculant> Nairwolf: because it's lts +1 
[20:12] <flocculant> experience tells us that testing wise - participation is low :)
[20:14] <Nairwolf> oh, I see. 
[20:14] <Nairwolf> And how have you found partitipation for this lts in comparaison for last lts ? 
[20:15] <flocculant> lower
[20:15] <flocculant> but run slightly differently
[20:15] <Nairwolf> oh really ? 
[20:15] <flocculant> yep - really
[20:15] <knome> !yup
[20:15] <knome> perfect
[20:15] <Unit193> knome: Troll. :P
[20:15] <flocculant> that's going to get old pretty quickly :p
[20:16] <knome> Unit193, no, yak
[20:16] <knome> flocculant, the secret is to only call it once in a while
[20:17] <flocculant> :)
[20:17] <Unit193> flocculant: You didn't jump to yukkety, right?
[20:18] <flocculant> Description:	Ubuntu Yakkety Yak (development branch)
[20:18] <Unit193> !info base-files
[20:18] <flocculant> not that it's much yet :)
[20:19] <knome> only 310 kB of yak
[20:20] <flocculant> definitely no steak on the body 
[20:24] <flocculant> btw - the basic of where I am with my thinking is at http://pad.ubuntu.com/xubuntuqa-y-cycle if anyone is interested
[20:26] <flocculant> bluesabre: especially perhaps you :)
[20:26] <knome> :D
[20:27] <Unit193> slickymaster: A reminder to bump the docs.
[20:27]  * flocculant refuses user docs existence this cycle :p
[20:28]  * slickymaster is having dinner at the moment.
[20:28] <knome> slickymaster, you fat boy :P
[20:28] <slickymaster> thanks for leaving your message, we'll get back to you as soon as possibel
[20:28] <flocculant> knome: can't remember if I said this last night - or even before but ... 
[20:29] <knome> flocculant, yes? :)
[20:29] <slickymaster> not I'm not
[20:29] <flocculant> in #xubuntu would it not be better to actually have the release note in the topic rather than the x.org thing? 
[20:30] <knome> flocculant, but the x.org thing is more user-facing
[20:30] <flocculant> knome: but the release note is more supporty :)
[20:30] <knome> then it's wrongy :(
[20:31] <flocculant> anyway
[20:31] <flocculant> said it now
[20:31] <knome> yeah
[20:31] <knome> and heard
[20:32] <flocculant> shall forget it now :)
[20:32] <knome> lol
[20:32] <knome> wfm
[20:32]  * flocculant can't decide whether to put xubuntu on the little tv box and install znc on it or not
[20:33] <knome> :D
[20:33] <knome> why not?
[20:33] <Unit193> ZNC doesn't need xorg!
[20:33] <flocculant> Unit193: it might not - but it serves the tv too 
[20:33] <flocculant> openelec atm
[20:34] <Unit193> Kodi!
[20:35] <flocculant> is what it runs yes
[20:35] <flocculant> quite nice for what it is actually
[22:30] <slickymaster> knome, did you forget https://code.launchpad.net/~flocculant/xubuntu-docs/fixlink/+merge/291795
[22:30] <slickymaster> ?
[22:31] <knome> likely so
[22:31] <knome> :P
[22:31] <slickymaster> do you want me to review it or will you?
[22:31] <knome> if you are motivated to merge it now, feel free to
[22:32] <slickymaster> ok