Thread: MeeGo is da Man
View Single Post
wmarone is offline wmarone
2010-10-27 , 15:56
Posts: 1,746 | Thanked: 2,100 times | Joined on Sep 2009
#8
Originally Posted by lma View Post
It's also far from ready for prime time. MeeGo 1.1 (due to be "released" shortly) contains many bugs that would be considered release blockers in any other distribution but get through here because of MeeGo's "take what's in the repos on $RELEASEDATE and call it $NEXTVERSION" policy.
That's some awesome fearmongering there. The bug quoted in the article was highlighted and confirmed as a blocker, then resolved before 1.1, so that article is full of crap and whoever wrote it obviously doesn't care enough to fix it. Worse yet, the "read more" link goes to an ENTIRELY DIFFERENT BUG.

Additionally, it looks like there's going to be an ABI break with 1.2 (softfp vs hardfp) so even the promise of forward binary compatibility is broken.
Fortunately, there's no one using MeeGo 1.1 on ARM at this point aside from the N900 port, and the entire development process is wide open so there's no excuse for getting caught by this. It must be done, and now is a better time than ever because it only gets worse.

In short, MeeGo Handset 1.1 is only useful for development purposes, 1.2 (hopefully) will be the first release that will be suitable for building commercial products and that's 6 months away.
No reason someone couldn't make 1.1 work with hardfp now if they really wanted to ship with it. And if they were the responsible company we hope they are, they would push upgrades and updates to users as time went on and make it a moot point.
 

The Following User Says Thank You to wmarone For This Useful Post: