|
2011-02-09
, 21:09
|
Posts: 1,141 |
Thanked: 781 times |
Joined on Dec 2009
@ Magical Unicorn Land
|
#2
|
The Following 2 Users Say Thank You to stlpaul For This Useful Post: | ||
|
2011-02-10
, 07:57
|
Posts: 196 |
Thanked: 224 times |
Joined on Sep 2010
@ Africa
|
#3
|
My question is this. When will the Meego community achieve a release that is suitable for every day usage by semi ordinary users ?
Prior to the release of Meego 1.1, I thought it was going to at least be something to "play with". Ie it would be semi usable for people who didn't mind suffering through updates, bugs, etc. Kind of like a Fedora rawhide release. IT wasn't. It turned out to be nothing more than a terminal.
I've been watching the Meego 1.2 efforts and I don't see that 1.2 does much of anything yet again for the end user.
Aside from looking at Bugzilla entries, where is it stated exactly what Meego 1.2 and 1.3 are supposed to do ? Ie, where are the deliverables for these milestones ?
It seems that the 1.0 and 1.1 releases consisted of exactly what got (mostly) done (and not yet fully debugged) when the milestone freeze date rolled around.
If I was a leader at Nokia, I would march over to Redhat and drag them into the Meego effort. They know how to develop OS software and work with communities. Nokia seems to be floundering around literally aimlessly !
PS: don't give me the "release early and release often" line. That only applies when there is actually something to release.
The Following 2 Users Say Thank You to buchanmilne For This Useful Post: | ||
|
2011-02-10
, 09:06
|
Posts: 650 |
Thanked: 497 times |
Joined on Oct 2008
@ Ghent, Belgium
|
#4
|
|
2011-02-10
, 09:33
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#5
|
What I remember from the talk Carsten gave on Fosdem last weekend, is that Meego has already been burried under a thick layer of bureaucracy, and you shouldn't even touch it with a 5 meter stick.
After that talk I just gave up on Meego, the way they are treating it will take ages to get something reasonable out the door - no wonder the new CEO will probably kill it off.
And I wasn't the only one attending that talk that left with that feeling.
The Following 7 Users Say Thank You to Stskeeps For This Useful Post: | ||
|
2011-02-10
, 13:02
|
Posts: 650 |
Thanked: 497 times |
Joined on Oct 2008
@ Ghent, Belgium
|
#6
|
|
2011-02-10
, 13:17
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#7
|
Flexibility. You talked about a 6 month release cycle. Granted, it is better than what Nokia manages with the n900, but might be too slow (unless the first release is feature and functionality complete - which I doubt).
The world is moving to rolling updates, fast and flexible fixes...
MeeGo aims to get products out to the market from different categories during a one-year period after a release, for the devices to be able to always use the latest and greatest MeeGo software. During this period, a lot of updates may be made to support the release and its users. The goal is to keep the quality stable, so that updates can be put into use without problems. This is a quality-first period.
Fixes are actively integrated for two years after the MeeGo release and security fixes are integrated and updated, when necessary, to existing MeeGo releases.
|
2011-02-10
, 15:18
|
|
Posts: 1,062 |
Thanked: 961 times |
Joined on May 2010
@ Boston, MA
|
#8
|
|
2011-02-10
, 15:21
|
Posts: 968 |
Thanked: 974 times |
Joined on Nov 2008
@ Ohio
|
#9
|
Only thing really added on top is the compliance stuff which is in it's early stages but needed to deliver on one of MeeGo's benefits, which is the promise that a MeeGo compliant app will run on a MeeGo compliant device. And that there's things to be solved (stating our faults instead of it being one big marketing slide praising MeeGo)
|
2011-02-11
, 05:43
|
Posts: 41 |
Thanked: 22 times |
Joined on Aug 2010
|
#10
|
Earlier this week we happened to get a peak into a supposedly confidential internal memo that painted a disappointing picture for Meego.
My question is this. When will the Meego community achieve a release that is suitable for every day usage by semi ordinary users ?
Prior to the release of Meego 1.1, I thought it was going to at least be something to "play with". Ie it would be semi usable for people who didn't mind suffering through updates, bugs, etc. Kind of like a Fedora rawhide release. IT wasn't. It turned out to be nothing more than a terminal.
I've been watching the Meego 1.2 efforts and I don't see that 1.2 does much of anything yet again for the end user.
Aside from looking at Bugzilla entries, where is it stated exactly what Meego 1.2 and 1.3 are supposed to do ? Ie, where are the deliverables for these milestones ?
It seems that the 1.0 and 1.1 releases consisted of exactly what got (mostly) done (and not yet fully debugged) when the milestone freeze date rolled around.
If I was a leader at Nokia, I would march over to Redhat and drag them into the Meego effort. They know how to develop OS software and work with communities. Nokia seems to be floundering around literally aimlessly !
PS: don't give me the "release early and release often" line. That only applies when there is actually something to release.
Last edited by me2000; 2011-02-09 at 21:00.