![]() |
2010-10-24
, 16:52
|
Posts: 117 |
Thanked: 26 times |
Joined on Dec 2009
|
#82
|
MeeGo is going to be on a 6 month cycle. But it's always open, so the release is constant (unlike say, Android, which is released when Google feels like it.)
![]() |
2010-10-24
, 16:55
|
Posts: 1,746 |
Thanked: 2,100 times |
Joined on Sep 2009
|
#83
|
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.
![]() |
2010-10-24
, 16:58
|
Posts: 117 |
Thanked: 26 times |
Joined on Dec 2009
|
#84
|
There is no release because well, it's coming out on Wednesday and there'll be 1.1 updates later probably.
![]() |
2010-10-24
, 16:59
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#85
|
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.
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.
The Following User Says Thank You to Stskeeps For This Useful Post: | ||
![]() |
2010-10-24
, 17:02
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#86
|
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.
![]() |
2010-10-24
, 17:18
|
Posts: 1,513 |
Thanked: 2,248 times |
Joined on Mar 2006
@ US
|
#87
|
I don't exactly recall what you mean by 'not built for a month' - we had some down time with the ARMv7 build but all the due while we were doing ARMv5 images. We uncovered a GCC bug that broke even the simplest of things, including DBus and it took some time to locate and fix.
Even if MeeGo 1.1 isn't the swan I hoped myself it would be, I'm bloody proud of the work and effort we've (as in the team and the people contributing to the port) put into the N900 side of things.
![]() |
2010-10-24
, 17:19
|
Posts: 117 |
Thanked: 26 times |
Joined on Dec 2009
|
#88
|
![]() |
2010-10-24
, 17:23
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#89
|
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.
![]() |
2010-10-24
, 17:29
|
|
Posts: 1,671 |
Thanked: 11,478 times |
Joined on Jun 2008
@ Warsaw, Poland
|
#90
|
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.
The Following User Says Thank You to Stskeeps For This Useful Post: | ||
![]() |
Tags |
troll, trololololol |
Thread Tools | |
|
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?
As you go on to other communities, remember to build them around politeness, respect, trust and humility. Be wary of poisonous people and deal with them before they end up killing your community.. Seen it happen to too many IRC channels, forums, open source projects.