"From a technical perspective, the browser team did not have enough
time/resources to merge to trunk (nor was there a stable trunk of any
value until long after we were frozen) and get any work done for diablo.
We therefore had to choose not to merge to trunk and plan to do it for a future release. "
My understanding of this is "still same old browser code" in Diablo.
Thanks for that; disappointing.
From the linked email:
Originally Posted by
I think the key is that you're ascribing this to be an OS release.
It isn't. it's a dot release. We never claimed it was a new OS release,
the marketing information on this is quite clear, and I can't imagine
anyone from Nokia would have claimed otherwise.
Which does seem to explain some things; Nokia considers point releases differently than, say, Microsoft, where we have NT 5.0, 5.1, and 5.2 all billed as completely new releases, and with the versioning very much swept under the rug.
We can hope that SSU will decouple MicroB from the big dot releases, so maybe we'll see a real update in a month or two. :\
That is my hope.
It seems that the browser team couldn't get synced to the new mozilla stuff in the trunk because of the early internal development freeze imposed by everything else. With everything independently update-able, they might be able to reduce the freeze->release time somewhat.
In the worst case, at least making beta builds/releases might be easier for them now. Those previous beta releases indicate a slowly shifting development culture within Nokia but it has some ways to go to match upstream.
Nokia considers point releases differently than, say, Microsoft, where we have NT 5.0, 5.1, and 5.2 all billed as completely new releases, and with the versioning very much swept under the rug.
Version numbering is mostly a marketing thing, it would seem. Very different from project to project and very subjective. There are some stability-based versioning schemes out there but you still have to know the specific project cultural knowledge to know what they mean by version 2.9.
I kind of like the more objective, date-based versioning that Ubuntu and Gentoo use. Doesn't really tell you about the stability of it, but if every project used this at least you would roughly know what version of some dependency should go with what. Not perfect but better.
Me too. I really want to buy the navigation but when I've tested it
the software was sadly outdated, it shows petrol stations thats
been closed for at least 5 years and routing repeatedly
suggested making illegal turns ...
I want a single unit, but since a nüvi 205 costs just
a little more than the 3 year wayfinder license I guess its
no deal unless the software is considerably improved.
Is anybody in a position that can confirm that the navigation software will be updated ?
Looks like they're on target for trunk with Diablo+1, anyway, though I couldn't get an answer out of timeless re SSU and decoupled updates. . . . Doesn't leave me particularly hopeful for avoiding Nokia's glacial release cycle.
Well, I haven't the slightest clue where the correct repo is for Diablo, but if anyone comes up with any ideas involving 'sed s/chinook/diablo/' or equivalent, I suppose they could try them. (Hope mvo doesn't get in trouble over this...)
