... the more popular your software, the more bugs are inevitably discovered when it goes into wide release, no matter how diligent your beta testing.
True. However Diablo, as just released, probably didn't have very extensive beta testing period. At least there wasn't any public one. Just getting access to an early build was like joining a secret society or something.
Nokia/Maemo should consider releasing a release candidate or beta versions in the future so that developers have a relatively stable target and power users can report on the arrows on their backs before the version for the average user is released.
That said, Diablo is a .1 update and mostly compatible with Chinook applications and the new seamless software update feature should help deliver bug fixes in a painless manner.
Anyone not comfortable with some minor breakage should probably wait for another week or two before taking the plunge.
Come to think of it, that would be a good time to see an up-to-date microb engine replacing the existing one based on a year-old alpha of Firefox 3.0...
I'd like to see a new microb in a week or two; but that's just not happening. I expect they were busy on Diablo, as there were weekly updates up to the end; that means they'd be starting pretty much now, and a month or so might be more reasonable.
FYI to those that want Gnumeric, it does not install on Diablo. It requires the same dependencies as the old Rhapsody. (The new one can be installed now)
True. However Diablo, as just released, probably didn't have very extensive beta testing period. At least there wasn't any public one. Just getting access to an early build was like joining a secret society or something.
Nokia/Maemo should consider releasing a release candidate or beta versions in the future so that developers have a relatively stable target and power users can report on the arrows on their backs before the version for the average user is released.
That said, Diablo is a .1 update and mostly compatible with Chinook applications and the new seamless software update feature should help deliver bug fixes in a painless manner.
Anyone not comfortable with some minor breakage should probably wait for another week or two before taking the plunge.
Come to think of it, that would be a good time to see an up-to-date microb engine replacing the existing one based on a year-old alpha of Firefox 3.0...
In some respects, the *secret* announcement was a lot like a RC release; not sure how much was tested personally, but there was *something in the way of testing* done.
I second that vote for replacing that engine *next week* with an updated one. But seeing that Gecko 2.0 hasn't been alive much more than a month (if memory serves), there is still some work yet to be done to merge hildon and other aspects of the new engine into microB.
I also have gnumeric working. Not sure what I did to get it that way, but it just installed fine, and it opens and runs fine. Just tried install Rhapsody, and it also installed fine. It seems to run fine, too.
Honestly, I'm not sure why they didn't have that link (or a copy) setup already; maybe none of the maemo honchos were running Diablo, and didn't realize that we were all using the Chinook repo.
Come to think of it, that would be a good time to see an up-to-date microb engine replacing the existing one based on a year-old alpha of Firefox 3.0...
Not likely to happen. They're on track for Fremantle with the Gecko trunk release, but you're unlikely to see it in an SSU update before then. You're more than welcome to compile the MicroB svn, though, which definitely has more than a few improvements over the version shipped with Diablo.
Honestly, I'm not sure why they didn't have that link (or a copy) setup already; maybe none of the maemo honchos were running Diablo, and didn't realize that we were all using the Chinook repo.
There's bucketfuls of information about the how and why on the -developers mailing list, on the wiki, in Planet, and on maemo.org announcements. Read up.
