Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

Also, we're shipping early and often - 1.1 has had daily repository dumps, weekly images since the beginning. So will 1.2 have. How is this not ship early and often? :P

There is no release because well, it's coming out on Wednesday and there'll be 1.1 updates later probably. It's known there's bugs and they're public because well, jolly, it's a open project. There'll always be what's determined release blockers and those that aren't. And any product ships with known bugs.

We are on a fixed release schedule. http://wiki.meego.com/Release_Engineering/Plans/1.1 remember?

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

Yes, except when you ask to try to run the N900 image, people say its not ready. So all we can do is sit on the outside and watch. That isn't open to me. Heck, the N900 image didn't even get built for a period of time because it had stopper bugs. And that prevented others from working on their parts and end users from testing it.

Lets say this... the N900 is the first and biggest Meego handset platform. And it literally has ZERO user testing on it. How can it be ready for release ?

Contrast this to how Fedora does things. Strict feature freezes. Daily/weekly builds. Code breakages are not allowed. Several live versions. Several RCs. Releases into a -testing repository. Lots of end user testing. Then and only then is it ready to be released. None of this has happened with Meego.

Don't dare tell me that anything they have thus far is ready for release, because by the open community standards, its not even close.

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

It's open. Not handed to you on a silver platter, but nonetheless open. You can even participate if you want.

Did you not read a word he said? Did you seriously ignore everything that Stskeeps just wrote, especially the line about ARMv5 images still being built?

You seem more than happy to attack and attack, but not to participate or pay any attention.

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

News to me. I have not heard any marketing information on this. I read the Linux homepage daily and I have not seen a single article.

The schedule here says it was supposed to release last week. (http://wiki.meego.com/Release_Engineering/Plans/1.1)

At the very least it slipped a week and nobody updated the plan. Contrast this to Fedora where there are release milestones and the plan gets updated as soon as a milestone slips. Google Fedora + slip and you'll see what I mean.

I understand the Meego team is probably pretty new and they are early in things, but this is a hugely important release for Nokia and they need to get things right, including the development and project management.

I will be very, very happy if a quality piece of software ships on Wednesday and I will heap praise on the developers if it happens.

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

Uhm..

Did you see http://tablets-dev.nokia.com/meego-codedrop.php and when we used it, and http://repo.meego.com/MeeGo/builds/ ?

Also, when a platform is in motion and being developed, there will be stopper builds. It's a fact of life. The light can't be showing 'green' constantly.

Again, look at the release page. And at http://wiki.meego.com/Release_Engine...lease_Timeline and at http://wiki.meego.com/Release_Engineering/Process , and at http://wiki.meego.com/Quality/Handse...eport/MeeGo1.1

These things happen, you know.

Also, let me remind you again: what is being shipped from meego.com is a platform, not a end-user product.

If it was an end-user product we'd have MP3 codecs, Flash and other things. And you'd have to help pay the royalities for those features.

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

No.

Please pay attention to figure 1:

http://wiki.meego.com/images/WeeklyReleaseCycle.png

That's the perspective the 'week' is supposed to be understood.

1.1.0.0 2010-10-21--2010-10-27

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

Thanks for the report. After 1.1 release, will we be on track to getting a N8x0 adaptation to test?

http://talk.maemo.org/showpost.php?p...4&postcount=41

We have to decide whether to move ahead with SSU^2 or MeeGo adaptation.

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

Here is the quality handset test report for October 22, 2010.
http://wiki.meego.com/Quality/Handse...ptance20101022

This is presumably the same software that you are saying will be released on October 27th.

Highlights

============================================
Key Issues:
8268- Double thumnail windows display when launching the xterm.
8414- Video playback is not smooth on N900.
7074- Incoming call can not be answered if dialer not open when call is received.
8194- [REG] Call a contact crashes contacts application.
===========================================

Result Overview
Total TCs 36
Passed 21
Failed 9
Not testable 6
Run rate 83.33%
Pass rate of total 58.33%
Pass rate of executed 70%

==========================================
Dial one outgoing call, accept by other party, terminate this call (phonesim, GSM & WCDMA) (GSM and WCDMA cannot be covered until real modem supported,Will use phonesim to test before real modem support)
==========================================
Scan wifi, check wifi connection (open/wep/wpa) and disconnection Fail
Bug 8043 - Settings application crashes on connecting to a WLAN AP
=========================================
As comment 1 of Feature 5770, usb mass storage device is detected by computer is moved to 1.2
========================================
Bug 7170- Battery level not shown
========================================
Top bugs
8268- Double thumnail windows display when launching the xterm.
7728- Sometimes black screen occurs when launching an application.
5850- It takes long time to launch core applications at the first time.
3590- The screen view is reversed when turn the device 180¡ãor 270¡ã
5790- Bluetooth settings does not display properly after tapping Bluetooth from Settings
7170- [N900] Battery level not shown
8043- Settings application crashes on connecting to a WLAN AP
8362- "start playing music" is not shown when no music is playing in music player.
7052- Some index letters of Video application are not displayed
8414- Video playback is not smooth on N900.
5882- DBus method requests to services not yet started timeout and loose context.
8194- [REG] Call a contact crashes contacts application.
==========================================

Call me a ignorant, but this doesn't look like the signature of software that is ready to ship 3 days from now. To me it looks like the team is shipping untested software that has a lot of bugs.

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

I think there's room for both, but I've been asking around about borrowing some build time to do a ARMv6+VFP build. And today while I was in transit I've spent time researching how to do it properly.

It seems like there's some awesome kernel work ongoing in the OpenWRT project, so that's covered..

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

I stand by that known bugs are better than unknown bugs. There was something about a big end user product shipping with thousands of known bugs.. :)

Also, some of these are simply features that wouldn't go into 1.1.

Keep in mind there's a release and then based on the featureset, fixes are delivered as things go along:

http://wiki.meego.com/images/MeeGoReleaseTimeline.JPG

So, yes, there's known bugs, but some were determined release blockers and some not. The release has to go out on a fixed release schedule. No delays.

In an ideal world we would start out with a perfect platform, add features, fix bugs in those features before they make it into Trunk. But fact is: we started off a non-perfect platform and non-perfect components.

1.2's where it's at.

1.1 needs to go out to let those who'd like to build a product (netbook, handset, ivi, whatever) based on the platform to finish up their work.

1.1 is already useful for some purposes, but Handset isn't there yet. Probably more like a Handset UX 0.5.