[07:00] <didrocks> hey sil2100, how were your holidays?
[07:02] <sil2100> didrocks: hello, thanks, not bad
[07:02] <sil2100> Although very busy, so as always I didn't even start resting properly ;)
[07:03] <didrocks> sil2100: yeah, that's the issue with one week vacations :)
[07:06] <didrocks> sil2100: FYI, we have some unity regressions with unity 6.0
[07:06] <didrocks> sil2100: can you look at backporting the existing fixes? there is also those branches that I think we need (please investigate with duflu):
[07:06] <didrocks>   https://bugs.launchpad.net/compiz/+bug/1019337
[07:07] <didrocks> https://code.launchpad.net/~vanvugt/compiz/fix-1019337.2/+merge/114597
[07:07] <didrocks>   https://bugs.launchpad.net/unity/+bug/1024911
[07:07] <didrocks> and we need a fix for bug #1024459
[07:07] <sil2100> didrocks: thanks! Will look at those once I get up-to-date with e-mail
[07:07] <didrocks> sil2100: also compiz gsettings isn't there yet
[07:07] <didrocks> so we need it :)
[07:07] <sil2100> didrocks: did the compiz release happen?
[07:07] <didrocks> no
[07:07] <didrocks> Mirv went on holidays before getting it done :(
[07:08] <didrocks> so in priority order I would say:
[07:08] <sil2100> Ouch, ok, we'll handle that then - but first the regressions I think?
[07:08] <didrocks> - unity fixes backported and unity SDRU
[07:08] <didrocks> yeah, in // with the SRU :)
[07:08] <didrocks> check with duflu if he's working on the latest bugs
[07:08] <didrocks> and ensure we really need the other merge fixes
[07:09] <didrocks> and meanwhile look at remaining MR not review for 5.0
[07:09] <didrocks> reviewed*
[07:09] <didrocks> sil2100: there are some emails on the PS ML about mandatory branches for the 5.0 unity SRU
[07:09] <sil2100> Aye aye, yessir :)
[07:09] <didrocks> so you can leverage both in parallel :)
[07:09] <didrocks> sil2100: good luck and… welcome back \o/
[07:09] <mhr3> sil2100, also, the failure to merge https://code.launchpad.net/~mhr3/unity/update-core-preview-api/+merge/112756 needs to be looked at
[07:09] <mhr3> sil2100, and hello :)
[07:10] <sil2100> mhr3: hello ;) Ok, will look
[07:10] <sil2100> Good to be back \o/
[07:10] <didrocks> "on the road again!"
[07:11] <mhr3> road... to hell? :)
[07:12] <didrocks> heh ;)
[08:01] <MCR1> didrocks: Hi :) I would need your help x2 I guess. Do you have a minute ?
[08:01] <didrocks> MCR1: yeah?
[08:01] <didrocks> for your MR, we need tests :)
[08:01] <tbf> is the code style documented somewhere? any reason for method names starting with a upper case letter? seems uncommon.
[08:01] <MCR1> didrocks: Do you mean the one with the compression ?
[08:02] <didrocks> MCR1: well, for each new plugins :)
[08:02] <didrocks> for compiz
[08:02] <didrocks> for the compression, I don't think it's needed
[08:02] <didrocks> just get some designer's feedback
[08:03] <MCR1> didrocks: Why does this need designer feedback - I did not change one pixel ?
[08:04] <didrocks> MCR1: to ensure that there is no visible change at all
[08:04] <didrocks> seems that Cimi already tried what you did
[08:04] <didrocks> and saw a difference
[08:04] <didrocks> so I prefer they can reviewed, as seb told you on the MR :)
[08:06] <MCR1> didrocks: I can guarantee that no difference is visible, but I also can understand that you do not want to trust all those binaries ;), that is why I suggested someone could reproduce it by simply installing trimage and dropping all pngs in there...
[08:06] <didrocks> MCR1: yeah, please ensure you ping JohnLea when he's around or Cimi :)
[08:07] <MCR1> didrocks: ok.
[08:08] <MCR1> didrocks: Second question: I fixed a bitesize bug in font-manager: rn/font-manager/font-manager.fix-961034/+merge/114991
[08:08] <MCR1> sorry, https://code.launchpad.net/~mc-return/font-manager/font-manager.fix-961034/+merge/114991
[08:08] <didrocks> MCR1: oh nice! please subscribe the sponsoring team, so that today's patch pilot can look at it :)
[08:09] <MCR1> didrocks: Is this the Font Manager Team ?
[08:10] <didrocks> MCR1: no, I don't really know about upstream, I'm speaking about downstream here, as getting the patch into ubuntu :)
[08:10] <MCR1> didrocks: So who should I add to the reviewers ?
[08:12] <didrocks> MCR1: if you don't want to wait on upstream, please follow the ubuntu sponsorship process: https://wiki.ubuntu.com/Bugs/Patches
[08:12] <didrocks> and https://wiki.ubuntu.com/Bugs/HowToFix
[08:13] <MCR1> didrocks: Thanx for the links - will save them and study those :)
[08:13] <didrocks> MCR1: yw ;) do not hesitate if you have any question!
[08:47] <didrocks> JohnLea: hey, how are you?
[08:54] <sil2100> seb128: hello!
[08:54] <seb128> sil2100, hey, how are you? had nice holidays?
[08:56] <sil2100> seb128: busy ones, but nice, thanks - and how are you?
[08:57] <seb128> sil2100, I'm good thanks
[08:59] <sil2100> seb128: I'm catching up on things right now - I saw an e-mail from Timo saying that some SRU (compiz? unity?) was in the process of being released
[08:59] <sil2100> Did any SRU besides the lenses got released?
[09:00] <sil2100> From the unity side?
[09:00] <seb128> sil2100, no
[09:00] <didrocks> sil2100: it's not really, that's what I pinged you this morning
[09:00]  * didrocks wasn't explicit enough maybe, but did a full summary at 9AM
[09:00] <seb128> sil2100, there is a need to redo a compiz update over the previous SRU one, a regression was detected (decorator segfault) which duflu fixed since
[09:00] <didrocks> seb128: already gave the full links this morning FYI :)
[09:01] <seb128> ok
[09:01] <seb128> sil2100, check what didrocks wrote to you I guess ;-)
[09:01] <didrocks> bug lists, branches to merge
[09:01] <sil2100> didrocks: ah, ok, since I just read an e-mail that stated that one of them was already pending for release, so I thought that at least something went in ;)
[09:01] <sil2100> seb128: ok, just making sure - thanks!
[09:01] <didrocks> sil2100: no, nothing since you last worked :(
[09:01] <seb128> yw!
[09:01] <seb128> welcome back to crazy unity world ;-)
[09:02] <didrocks> sil2100: I think popey also have the information about what happened and can give them to you :)
[09:02] <seb128> didrocks, sil2100: the music lens SRU got in
[09:02] <seb128> well it's in the queue
[09:02] <seb128> so one thing happened :p
[09:03] <didrocks> yeah, was mostly done when sil2100 was leaving as it's mostly the same than the release :p
[09:10] <didrocks> sil2100: also for compiz, I gave a full list to Mirv about commits that I think we should backport (it's on the ML I guess)
[09:14] <sil2100> I saw that e-mail indeed
[09:34] <jokerdino> hey guys o/
[09:35] <jokerdino> i am just feeling a little excited. i just submitted my first merge proposal for a bitesize bug. https://bugs.launchpad.net/unity/+bug/937334 let me know how to improve on that. Thanks again.
[09:36] <seb128> jokerdino, hey, well done!
[09:36] <jokerdino> thanks.
[09:36] <JohnLea> didrocks; hyia
[09:36] <jokerdino> i wasn't sure how it actually works. so, thought I would try first and learn from mistakes.
[09:37] <didrocks> hey JohnLea, how was your week-end?
[09:37] <JohnLea> didrocks; good but wet; summer here is terrible
[09:37] <JohnLea> didrocks; and yours?
[09:37] <seb128> jokerdino, can you do before,after screenshots? as commented on the bug that will need design input, see JohnLea's comment as well on the bug
[09:38] <jokerdino> oh sure. i have it.
[09:38] <seb128> jokerdino, adding a line will have an impact on the layout and size of the overlay
[09:38] <jokerdino> hm that's right.
[09:38] <jokerdino> but i couldn't see much obvious difference though
[09:38] <didrocks> JohnLea: was nice, enjoyed the national fest, fireworks… avoiding the rain :)
[09:39] <JohnLea> jokerdino; thanks for looking at this, email the screenshot to john.lea@canonical.com
[09:39] <seb128> can you add them to the bug as well?
[09:39] <jokerdino> alright. will do both.
[09:39] <didrocks> JohnLea: I wanted to have your input on bug #907464. I didn't think that design had to be involved as it really seem like a bug to me, but bilal asked for it :)
[09:41] <JohnLea> didrocks; I've updated the bug with all the correct statuses, bilal will now be happy ;-)  You were right, but better safe than sorry
[09:41] <didrocks> JohnLea: excellent! thanks :)
[09:42] <jokerdino> seb128, JohnLea: added; emailed
[09:42] <seb128> jokerdino, thanks
[09:46] <JohnLea> jokerdino; +1 from me, adding comment to this effect to the bug now.  Thanks for fixing ;-)  If you are ever looking for more bugs to fix ;-) , take a look at the list under the heading "Design changes signed off but not handed over" @ http://people.canonical.com/~platform/design/designer.html or
[09:46] <JohnLea> under heading "unity" @ http://people.canonical.com/~platform/design/upstream.html
[09:47] <jokerdino> will do more fixing in the future. thanks much for positive feedback :-D
[09:48] <JohnLea> jokerdino; np, ping me on IRC if you are looking at a bug and have any questions
[09:49] <jokerdino> sure sir.
[10:03] <MCR1> JohnLea: I would need your help too, I guess: https://code.launchpad.net/~mc-return/unity/unity.merge-reduce-png-filesizes/+merge/110978
[10:28] <JohnLea> MCR1; looking now
[10:31] <MCR1> JohnLea: Thanks a lot. Unfortunately I have some more design decisions for you to make, just tell me when you are ready for those ;)
[10:32] <JohnLea> MCR1; as the assets will be visually unchanged by the proposed branch, no design signoff is needed.  It's purely a technical decision, so I'll point you back to Seb128.  For what it's worth it looks like a good change to me, but as it is not a user facing change it is outside of my remit
[10:32] <JohnLea> MCR1; what are the other questions, I'm ready ;-)
[10:32] <MCR1> JohnLea: Oh that are many. Where should I start ?
[10:33] <JohnLea> MCR1; start with the changes that are closest to landing ;-)
[10:34] <MCR1> JohnLea: Well, I would say that bug 1022743 is quite important.
[10:35] <MCR1> JohnLea: Imho the way Compiz/Unity share their shortcuts is currently very wrong creating multiple troubles.
[10:36] <JohnLea> MCR1; there is also the companion bug, https://bugs.launchpad.net/ayatana-design/+bug/775434
[10:37] <MCR1> JohnLea: I did not see that one, but from the title I have to agree. :)
[10:38] <JohnLea> MCR1; I was just discussing moving one shortcut from CCSM to this panel with popey this morning.  But really we want to get all the shortcuts defined in a single place, and almost all configurable.
[10:38] <MCR1> JohnLea: This is imho one of the most important problems we have. It is also a problem with the type of shortcuts.
[10:38] <JohnLea> (the 'almost' bit of the above sentence refers to things like the SUPER key which we might want to make configurable because of the complexity of what is bound to it
[10:39] <JohnLea> ^ 'not want' I meant
[10:40] <JohnLea> MCR1; are you volunteering to have a look at fixing this ;-)  If so the best way to start would be by pinging didrocks as he knows this area of code well, and will be ultimately responsible for accepting your patches
[10:41] <MCR1> JohnLea: A big problem is the type of shortcuts as Compiz should know and control all keys, otherwise this creates multiple problems...
[10:42] <JohnLea> MCR1; yes, and the Compiz shortcuts should be exposed through the 'keyboard shortcuts' panel.
[10:42] <JohnLea> which is missing atm
[10:43] <MCR1> JohnLea: Sure, I would like to fix that - and I think I would be capable to take a shot at it - I just need to find the commit, which transformed the Alt HUD key-shortcut from hardcoded to Compiz.
[10:44] <MCR1> JohnLea: And then imitate that for all the other keys ;)
[10:47] <JohnLea> MCR1; there is *a lot* of special behaviour around both the SUPER and ALT key, so I would start by exposing all the other keys, and then get to these last.  It might be that SUPER has to stay non-configurable, but the companion keys used with SUPER can be changed e.g SUPER+V could be changed to SUPER+Y, but not SHIFT+V.  You should see what I mean when you look at the code.  If we can get all the keys *other* than ALT and SUPER configurable and ex
[10:47] <JohnLea> posed in the 'keyboard shortcuts' overlay we will be doing well, and once that is done take a look at ALT
[10:48] <MCR1> JohnLea: ALT is already configurable afaik
[10:49] <MCR1> JohnLea: But I know what you mean - I am still in the process of trying to analyze all this code, but there is definitely room for improvements there
[10:49] <JohnLea> MCR1; cool, the more we can make configurable the better, perhaps it is just SUPER that will have to stay fixed in the first iteration of this improvement?
[10:52] <JohnLea> MCR1; basically the intent would be to make as many keyboard shortcuts as possible configurable and exposed in the keyboard shortcuts panel.  Another tricky one might be 'Ctrl + Super + Cursor down' ( see https://docs.google.com/a/canonical.com/document/d/1jqeKtIJwqLtl58Wk_fqjr9Rrgxn9zsouCYOo-cZsLSE/edit?hl=en_GB ) which should perform different actions based on the state of the currently focused window.  Not implemented yet, but I think it is on
[10:52] <JohnLea> didrock's todo list?
[10:52] <MCR1> JohnLea: I am very glad that we agree 100% on this :) I will try my best to work on it, but I might need help of the guys who worked on that part of the code...
[10:53] <MCR1> JohnLea: I already talked with smspillaz about that problem, I guess with some hints from him (when he is back) we can get things done 8-)
[10:55] <JohnLea> MCR1; while we are talking, one other thing that needs to be added to the compiz keyboard shortcuts is the ability to bind two different shortcuts to the same action.  This would be very useful for supporting shortcuts that are depreciated or users are used to from other platforms in addition to the default shortcuts
[10:57] <JohnLea> MCR1; smspillaz will be away for another couple of weeks, didrocks is the person who should be able to help you out with any questions.
[10:57] <MCR1> JohnLea: Compiz is already capable of doing two different actionswith the same shortcut. It will warn you, but allows to do that - but I like your "two different shortcuts to the same action" idea also very much :)
[10:58] <JohnLea> MCR1; cool ;-)  I think there is some issue with the 'two different actions' because I asked smspillaz about it 2 or 3 months ago and he said it didn't work but would be easy to fix.
[10:58] <MCR1> JohnLea: Ok, then I'll nerve him. I am very satisfied that you agree on those hardcoded hell, because that is one of the most important problems.
[10:59] <MCR1> JohnLea: For smspillaz everything is easy to fix ;)
[10:59] <JohnLea> MCR1; I am very happy that you are taking a look at this, it is a bit of a neglected area in need of some rejuvenation.
[11:00] <MCR1> JohnLea: He is a coding genius. Do not expect my coding qualities to be even near his level ;)
[11:01] <JohnLea> MCR1; as long as your coding qualities are of a sufficient level to get your  code accepted by didrocks we are good ;-)
[11:02] <MCR1> JohnLea: We'll see ;)
[11:22] <API> didrocks, one thing, I have just read that thread about accessibility always on on GNOME 3.6
[11:22] <didrocks> API: yeah?
[11:22] <API> fwiw, the port to the new atk-bridge library is
[11:22] <API> was proposed to be merge
[11:22] <didrocks> I saw your branch, thanks :)
[11:22] <API> https://code.launchpad.net/~apinheiro/unity/a11y-a11y-always-on
[11:23] <API> ah ok
[11:23] <didrocks> let's wait on upstream to look at it :)
[11:23] <API> it was about that, not sure if alex launi is stil reviewing unity branches
[11:23] <API> wait on upstream?
[11:23] <didrocks> API: btw, what's the actual status of a11y in unity?
[11:23] <didrocks> API: well, the other dx guys ;)
[11:23] <didrocks> API: is it full, what's missing,
[11:23] <API> didrocks, so it is ok on setting alex launi to review the branch?
[11:23] <API> didrocks, about the status
[11:24] <API> at this moment my old extra-a11y ppa is not required
[11:24] <didrocks> API: no, just set the unity-team as reviewer
[11:24] <API> as all the branches get merged
[11:24] <API> didrocks, ok, will change the reviewer
[11:24] <didrocks> API: so, is it fully accessible?
[11:24] <API> resuming a11y status
[11:24] <didrocks> yep :)
[11:24] <API> I reviewed the status
[11:24] <API> launcher works
[11:24] <API> dash and alt+f2 also works (with some "buts")
[11:25] <API> alt+tab switcher changed a little since the last time I worked on that
[11:25] <API> so it would be required a review
[11:25] <API> panel service still works
[11:25] <API> so in summary, there are stuff working
[11:25] <API> but still room for improvement
[11:25] <didrocks> API: so, it's usable for a daily usage in your opinion?
[11:33] <API> didrocks, sorry, adding a comment to the merge review and adding unity-team to the reviewer list
[11:33] <didrocks> API: no worry ;)
[11:33] <API> well, unity is usable for a daily if no other option is available
[11:33] <API> but as I said, there are some "buts" and some new stuff since the last time I worked on that
[11:33] <didrocks> ok, thanks for the status API :)
[11:34] <API> so I guess that using it daily will get people frustrated
[11:34] <API> as there are other options as xfce, gnome-shell, and still unity2d
[11:35] <didrocks> API: possibly, yeah…
[11:51] <TheMuso> c
[12:00] <sil2100> didrocks: so that you're up-to-date - I just built the new unity 6.0 regression fixes packages and will test those, and in the meantime I am also preparing MRQ branches for compiz SRU with some (most) of the commits you marked in your e-mail
[12:25] <didrocks> sil2100: great great! :)
[12:28] <sil2100> didrocks: some of the commits you pointed at are already merged into the 0.9.7 source branch btw. ;)
[12:29] <didrocks> sil2100: great, but we aren't basing from the branch, isn't it?
[12:29] <didrocks> sil2100: IIRC, you added patches manually?
[12:30] <sil2100> didrocks: well, I was cherry-picking every fix that went into 0.9.7 branch earlier - not sure about now, since Timo was doing the patches last week
[12:30] <didrocks> ok
[12:31] <sil2100> Since it's not so easy as with the new packaging branches you made :(
[12:31] <didrocks> sil2100: thanks for the notice :)
[12:31] <didrocks> yeah
[12:31] <sil2100> With the new one it's just a lazy bzr merge neede ;)
[12:31] <didrocks> that's why now that upstream is in bzr, I switched to that :)
[12:31] <sil2100> *needed
[12:31] <didrocks> wasn't possible when they were in git :)
[12:44] <sil2100> didrocks: btw. since I see that Timo ported as a distro-patch the fix for LP: #994841
[12:44] <sil2100> didrocks: I remember you said that it's not necessary before, since it's just related to tests?
[12:49] <didrocks> sil2100: indeed, it's not necessary to us
[12:50] <sil2100> didrocks: ok, so I remove it
[12:50] <didrocks> thanks ;)
[13:17] <sil2100> didrocks: regarding the compiz SRU, I'd like Sam to approve one MRQ before setting it to approved - since no one from the compiz team yet approved it, although they did comment that it seems ok
[13:17] <sil2100> https://code.launchpad.net/~vanvugt/compiz/fix-1019337.2/+merge/114597
[13:17] <sil2100> And it's a very important branch
[13:17] <didrocks> sil2100: sam isn't around for some weeks
[13:17] <didrocks> sil2100: so you need to find someone else I'm afraid
[13:18] <didrocks> the code is fine. However, I'm not sure it's fixing the issue
[13:18] <didrocks> but this code can't harm
[13:18] <sil2100> didrocks: the previous MRQ that went already in was supposed to fix it, this is a follow-up more or less
[13:19] <sil2100> didrocks: you think I can approve it?
[13:19] <didrocks> sil2100: yeah, I can only say the this code makes sense and can do no harm :)
[13:19] <didrocks> so yeah, you can approve it I guess
[13:19] <sil2100> Thanks \o/
[13:19] <seb128> sil2100, didrocks: the bug points to a ppa and 3 users confirmed the ppa fixes the issue
[13:19] <seb128> not sure what commit Mirv's included in there though
[13:19] <seb128> but it's easy to check out
[13:20] <didrocks> ok, good ;)
[13:20] <didrocks> thanks seb128
[13:20] <seb128> yw
[13:20] <didrocks> sil2100: go on then ^
[13:21] <sil2100> seb128: I have the packaging branch, so I see that the 2 fixes in mention are in, so indeed
[13:21] <sil2100> seb128: thanks for the notice!
[13:21] <seb128> didrocks, yw!
[13:22] <didrocks> seb128: completion issue infected you now? :)
[13:22] <seb128> sil2100, yw!
[13:22] <seb128> didrocks, it seems so, though I can't blame mines on my IRC client ;-)
[13:22] <didrocks> heh
[13:24] <sil2100> 6.0 regression fixes in trunk, cherry-picking
[13:27] <sil2100> didrocks: lp:~sil2100/unity/ubuntu_quantal_fixes
[13:28] <didrocks> sil2100: sweet! already tested?
[13:29] <sil2100> didrocks: for now I tested if the fixes work, but I can perform manual-tests or similar if needed
[13:29] <sil2100> didrocks: should I create a doc for it as always and proceed with all the tests, or just this is sufficient?
[13:30] <didrocks> sil2100: just create a small doc telling that the fixes work and you didn't notice any regression
[13:30] <didrocks> sil2100: just do the tests that seems sensible to those fixes
[13:31] <sil2100> didrocks: ACK! Proceeding with that in a moment though, I'll just finish some compiz bzr'ing
[13:32] <didrocks> sure :)
[13:32] <didrocks> sil2100: the branch looks good, I'm downgrading compiz (as I tested latest trunk) and rebuilding unity
[13:51] <sil2100> didrocks: https://docs.google.com/a/canonical.com/document/d/1UsC-oNhBmxHTi-2caZHaZ3YiyUA5SR7IqofdoBhgjRc/edit#
[13:52] <didrocks> sil2100: on a meeting, back afterwards :)
[13:52] <didrocks> sil2100: it's running fine btw :)
[13:52] <sil2100> didrocks: I also proposed some fixes and the .2 branch to lp:compiz-core/0.9.7 if anything
[13:52] <sil2100> didrocks: so we should be ready for compiz SRU tomorrow \o/
[13:53] <sil2100> didrocks: good luck on the meeting
[13:54] <sil2100> brb in a moment, storm
[14:24] <sil2100> Back
[15:02] <sil2100> didrocks: can't notice any regressions in the new 6.0 branch
[15:02] <didrocks> sil2100: neither do I
[15:02] <didrocks> sil2100: I'll upload it I guess :)
[15:02] <sil2100> didrocks: \o/ thank you
[15:02] <didrocks> sil2100: thanks you! :)
[15:02] <didrocks> now compiz SRU? ;)
[15:02] <didrocks> and unity one?
[15:03] <sil2100> didrocks: as for compiz SRU - we'll wait for Daniel to be back tomorrow to comment on the 2-3 additional fixes I asked for merging - if he says that these are valid SRU commits and get approved, we're almost done I think
[15:03] <sil2100> didrocks: I prepared the packaging branch with updated patches
[15:04] <didrocks> ok, the branches on the ML are all merged?
[15:04] <didrocks> there is the software-center one
[15:04] <didrocks> and the first super + W IIRC
[15:05] <sil2100> didrocks: you mean the two unity ones for the software center? Not yet merged, but I think we can approve those
[15:05] <sil2100> didrocks: the super + W fix is still a '?'
[15:05] <didrocks> sil2100: there are 2 things about it
[15:05] <didrocks> sil2100: there is the bug
[15:05] <didrocks> about "windows flying away"
[15:06] <didrocks> this is a just a bug and should be fixed
[15:06] <didrocks> the second is under discussion :)
[15:06] <sil2100> Ah, ok ;)
[15:07] <sil2100> didrocks: ok, I'll look at this windows flying away bug then
[15:07] <sil2100> didrocks: what about the software center fixes for unity? In your opinion, can those get into 5.0?
[15:08] <didrocks> sil2100: yeah, once properly reviewed
[15:09] <sil2100> Orajt
[15:10] <sil2100> Shit, storm again, brb in a moment (again)
[15:10] <sil2100> eh
[15:28] <sil2100> Trevinho, andyrock, bschaefer: anyone of you around by any chance?
[15:28]  * Trevinho present
[15:29] <sil2100> Trevinho: are you particulary busy right now ;) ?
[15:29] <Trevinho> sil2100: not yet
[15:29] <sil2100> Since we would need someone from unity to review https://code.launchpad.net/~bilalakhtar/unity/5.0series-sru-software-center-integration-fixes/+merge/110214 and https://code.launchpad.net/~gary-lasker/unity/software-center-launcher-integration-tests-for-5.0/+merge/114241
[15:29] <sil2100> As we would like those to land in the nearest SRU
[15:29] <Trevinho> ok, I'll check them
[15:29] <bschaefer> sil2100, im around
[15:29] <sil2100> bschaefer: ^
[15:29]  * bschaefer got randomly logged out
[15:29] <sil2100> :)
[15:30] <sil2100> Trevinho, bschaefer: just looking for someone who might test these MRQs (or one MRQ, as the other are just tests), browse through the code and approve if all is OK
[15:31] <bschaefer> sil2100, yeah I can give them a test :), my day just started
[15:31] <sil2100> Excellent
[15:31] <sil2100> Thanks
[15:31] <bschaefer> np!
[15:44] <andyrock> sil2100, pong
[15:51] <sil2100> andyrock: hi! Trevinho and bschaefer are already dealing with my problem :)
[15:52] <andyrock> sil2100, ok... I was watching the tv for le tour de france :)
[16:01] <sil2100> Ok everyone, need to jump out to the bank now and for dinner - see you tomorrow!
[16:14] <andyrock> om26er, can you update the status of this bug? https://bugs.launchpad.net/unity/+bug/962395
[16:14] <andyrock> I mean adding unity 5.0 and Ubuntu (Precise)
[16:14] <andyrock> :)
[16:15] <om26er> andyrock, looking
[16:17] <andyrock> om26er, thank you
[16:17] <om26er> andyrock, done ;-)