MobileRead Forums - View Single Post

taming · 09-07-2012, 01:13 PM

The beta process sometimes ends before a last internal round of changes. I am not sure why that happens, but for 2.0 I suspect it had something to do with firm deadlines related to the release in Japan. The developers do not seem to be the folks who control that kind of thing. Sameer and his team are great. I am pretty sure that they are less happy than we are when things go pear shaped.

BTW, in the last version tested before the 2.0 release, both kepub and ePubs had slow page turns. On release, the kepub page turns had been fixed. In the past, we were not able to test the installation process that happens in general release either.

I would also love to know why interim fixes for things like this are not released even as they are working on other things. My best guess (and it truly is a guess) is that they are working on something that might make the easy fix not work for everyone, or perhaps for anyone, as some other part of the firmware is worked on.

I do know that when you bake temporary fixes into code, odd things can happen later.

09-07-2012, 01:13 PM	#1169
taming Trying for calm & polite Posts: 4,012 Karma: 9455193 Join Date: May 2010 Location: Mostly in Canada Device: kobo original, WiFI, Touch, Glo, and Aura	The beta process sometimes ends before a last internal round of changes. I am not sure why that happens, but for 2.0 I suspect it had something to do with firm deadlines related to the release in Japan. The developers do not seem to be the folks who control that kind of thing. Sameer and his team are great. I am pretty sure that they are less happy than we are when things go pear shaped. BTW, in the last version tested before the 2.0 release, both kepub and ePubs had slow page turns. On release, the kepub page turns had been fixed. In the past, we were not able to test the installation process that happens in general release either. I would also love to know why interim fixes for things like this are not released even as they are working on other things. My best guess (and it truly is a guess) is that they are working on something that might make the easy fix not work for everyone, or perhaps for anyone, as some other part of the firmware is worked on. I do know that when you bake temporary fixes into code, odd things can happen later. Last edited by taming; 09-07-2012 at 01:19 PM.