Michael did accurately represent what I said during our discussion.
That said, rather than "in a week or two" I guess a more complete statement (from me) would have been "until we get any obvious hardware programming issues resolved and reach the point where the remaining work does not require access to internal hardware information, which I expect to be in a week or two, but which could be longer or shorter depending on the issues we find after initial release".
I was definitely expecting a week or two of post-release gotcha-fixing, but there was a bigger difference between what users saw and what we saw internally than we had seen on previous initial code drops.
EDIT - just noticed that the initial release was only 13 days ago, so maybe "a week or two" will still turn out to be an OK guess![]()




Reply With Quote
