[03:28] <roasted> Hello friends. I've been following the Unity 7.2.1 launchpad. I'm trying to understand the SRU process. I see that 7.2.1 14.04 SRU 1 was "released" 22 hours ago. Is that part of a review process? Just questioning it given that I'm not seeing it via updates, etc.
[03:46] <Pici> roasted: It looks like 7.2.1 is in trusty-proposed right now.
[03:47] <Pici> See step 6 here: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
[03:48] <roasted> Pici: yeah I just enabled that and pulled in 7.2.1. I'm good now. :)
[03:48] <roasted> Pici: I just took 'released' as in, it's RELEASED, like part of the regular update system.
[03:48] <roasted> not released as in, ahh just in pre-release for now, etc.
[03:49] <Pici> yeah, it is a little confusing
[03:50] <roasted> seems like the min 7 day wait period applies... now
[03:51] <roasted> There's one last thing that I'm unsure of. There's a bug targeted for 7.2.1 that is in progress right now. Given that SRU 1 is in trusty-proposed, is that to say that whenever that bug gets fixed, it effectively misses SRU 1 since SRU 1 is here now? Or is there always a chance to merge it later as part of regular updates once SRU 1 is in the regular update repo?
[03:53]  * Pici shrugs
[03:55] <tarpman> roasted: Fix Released for the upstream project is separate from Fix
[03:55] <tarpman> argh
[03:55] <tarpman> Released for the Ubuntu packages
[03:56] <tarpman> roasted: you'll notice most of the bugs still say Fix Committed in trusty, ie. they're in trusty-proposed
[03:56] <roasted> So if I understand right, Fix Committed is proposed, Fix Released is "hey just open software updater"
[03:57] <tarpman> and wait for your local mirror to update
[03:57] <roasted> What does that mean for the SRU 1 being in proposed now for the bugs that are targeted for SRU 1, but not 'fixed' yet?
[03:57] <tarpman> that they missed the milestone. unfortunate, but happens
[03:58] <roasted> :(
[03:59] <tarpman> roasted, which bug in particular are you affected by? just curious
[03:59] <roasted> let me dig it up quick
[03:59] <roasted> it's the highlight offset one I'm curious about
[03:59] <roasted> minor, but an aesthetic annoyance
[04:00] <roasted> https://bugs.launchpad.net/unity/+bug/1309739
[04:00] <ubot5> Ubuntu bug 1309739 in unity (Ubuntu) "Unity launcher icon edge illumination is offset" [Medium,In progress]
[04:01] <tarpman> yeah, see the merge proposal on that one? the reviewers approved it, but it hasn't actually been merged yet. I take that to mean it missed the cutoff, whenever that was
[04:01] <roasted> bummer
[04:01] <tarpman> there will be more SRUs. 12.04 has had 7 so far, and I don't think it's done yet
[04:02] <roasted> yeah, I believe it. It's just one of those things where it's the one thing I notice continuously that my OCD is ruffled by.  :P
[04:02] <tarpman> oh, I know what you mean
[04:03] <roasted> mostly because I have a hard time figuring out exactly how I can identify when an application needs attention...
[04:03] <tarpman> you know the expo view, super-S? the yellow border makes room for the unity launcher on the left even when you're not running unity
[04:03] <tarpman> totally aesthetic thing, but bugs me every time ;)
[04:03] <roasted> so via tweak I just use set the icon backgrounds to no coloring so I can actually see the borders that get highlighted.
[04:03] <roasted> But when you adjust the icon sizes, that bug comes into play.
[04:04] <roasted> I mean the icons don't bounce every 30 seconds to remind me that I have an awaiting message, so the highlights are all I use.
[04:04] <roasted> hence my interest in it :P
=== mythos_ is now known as mythos
=== om26er_ is now known as om26er
=== roadmr is now known as roadmr_afk
=== roadmr_afk is now known as roadmr