hi, Am Mittwoch, den 20.08.2014, 17:40 +0200 schrieb Alexander Sack: > > Have we identified the regression window? aka which landing caused this?
it is very likely that it simply never worked, it was only exposed when
we started having actual screen lock support (which hides the second
notification) in place ... and even then you need to have two meetings
or have to have set two alarms to exactly the same time to actually see
it ... i knew it was broken but i have only hit that condition exactly
once since the issue was first seen a few weeks ago (when pat booked me
for a meeting at the same time i already had one)
i think retroactively putting time into finding a landing for this
instead of just investing the time into a fix is just wasteful ... we
should definitely add a dogfooding test case for it to prevent it in the
future though.
ciao
oli
signature.asc
Description: This is a digitally signed message part
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
