5 ms·
It sounds and looks like an off by one bug. But it could be nasty to fix if people have already created events with an off by one bug. Any update to fix the dat
by NathanKP 14y ago
It sounds and looks like an off by one bug. But it could be nasty to fix if people have already created events with an off by one bug. Any update to fix the date picker could then cause their scheduled dates to show up a month early, and would therefore also have to include some sort of script to update existing scheduled events users have created.
- deleted 14y ago[deleted]
- ch0wn 14y agoYap, there was a change in the NumberPicker that seemed to have caused it: https://github.com/android/platform_frameworks_base/commit/a1410e6789ce72bc423793315a51aea8b6bad6c7 https://github.com/android/platform_frameworks_base/commit/a...
- swohns 14y agoThat makes sense, but why is the patch taking so long?
- Lewisham 14y agoRushing a patch and possibly breaking something further is worse than just having the bug you have out now. As a former intern, usual Google practice is to rollback rather than attempt to fix with non-client apps, in order to take a more measured approach to the issue and not accidentally break something with a hasty fix. Android is in a different position as rollbacks aren't possible, but my guess is the release managers would take a similar view to not rushing.
- zmmmmm 14y ago50% of comments: what horrible QA, don't they test anything? Other 50% of comments: why is the patch taking so long!
- SoftwareMaven 14y agoIt may be a trivial <=12 instead of <12 in the controller that populates the view. If it is more than that, ugh. It wouldn't be so bad for new devices, but for people who upgraded, this could be seriously ugly.