Active Topics
-
The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 11 hrs, 29 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 7 hrs ago - more...
nosa101 |
2010-05-13
, 13:14
|
|
Posts: 1,667 |
Thanked: 561 times |
Joined on Feb 2010
|
#131
|
Originally Posted by taril
You haven't even tried it yet
|
|
2010-05-13
, 17:04
|
|
Posts: 119 |
Thanked: 124 times |
Joined on Jan 2010
@ Brazil
|
#132
|
Originally Posted by Hynkel
Ok, check it back in about 9 weeks then, since it would have passed 1 and 3/4 month!!
At least there is a hint of a release date there, "some weeks still but not months" :P
 |
|
2010-05-13
, 17:46
|
|
Posts: 4,384 |
Thanked: 5,524 times |
Joined on Jul 2007
@ ˙ǝɹǝɥʍou
|
#133
|
Nokia is diverting many of their maemo developers to assist with finishing Duke Nukem Forever... PR1.2 development will resume when Duke Nukem Forever is released...
__________________
Class .. : Power User
Humor .. : [#####-----] | Alignment: Pragmatist
Patience : [###-------] | Weapon(s): Galaxy Note + BB Bold Touch 9900
Agro ... : [###-------] | Relic(s) : iPhone 4S, Atrix, Milestone, N900, N800, N95, HTC G1, Treos, Zauri, BB 9000, BB 9700, etc
Class .. : Power User
Humor .. : [#####-----] | Alignment: Pragmatist
Patience : [###-------] | Weapon(s): Galaxy Note + BB Bold Touch 9900
Agro ... : [###-------] | Relic(s) : iPhone 4S, Atrix, Milestone, N900, N800, N95, HTC G1, Treos, Zauri, BB 9000, BB 9700, etc
Follow the MeeGo Coding Competition!
|
|
2010-05-13
, 18:13
|
|
Posts: 119 |
Thanked: 124 times |
Joined on Jan 2010
@ Brazil
|
#134
|
Will Duke Nukem Forever come embedded with Meego devices?
|
|
2010-05-13
, 20:23
|
|
Posts: 384 |
Thanked: 95 times |
Joined on Jan 2010
@ Romania
|
#136
|
I know the reason why PR 1.2 is late. Nokia want to test their customers fidelity. If we pass the test they will reward us with a firmware who has all the symbian features plus all the best that maemo brings. Then the OVI store will fill with a lot of cool applications and games, even NGAGE.
That's why we have to be patient. The problem is that the guys didn't tell us how long the test will be.
Cheers!
That's why we have to be patient. The problem is that the guys didn't tell us how long the test will be.
Cheers!
 |
|
2010-05-13
, 22:41
|
|
Posts: 290 |
Thanked: 165 times |
Joined on Sep 2009
|
#137
|
what i just dont get is why nokia cant give us release dates..
is it that hard for them to plan ahead? incredible..
for example i take the Eclipse foundation and there release trains that are planned ahead i think about 10 to 12 months.
those release trains are big, they are a huge huge codebase. Not just the eclipse core system and jdt tooling. no many many sub projects all targeting a specific release date almost a year ahead with mile stone builds every 1.5 month or so.
did they ever in all these years form 1.0 to now 3.5 and busy finalizing 3.6 miss one target date? no they never did..... I find that pretty amazing for such a large codebase.
what i hope nokia is going to do is say we are releasing a new firmware every 2 months in the first week of that month.
then just plan make a cut (branch) a few weeks before the release, strart testing internally, fix some regressions, make 1 public beta or something 1 week before. then test some more and release.
in the mean time the trunk stream also progressed and the cycle starts over. (with a bit of planning what to get in (try to) in the next.
is it that hard for them to plan ahead? incredible..
for example i take the Eclipse foundation and there release trains that are planned ahead i think about 10 to 12 months.
those release trains are big, they are a huge huge codebase. Not just the eclipse core system and jdt tooling. no many many sub projects all targeting a specific release date almost a year ahead with mile stone builds every 1.5 month or so.
did they ever in all these years form 1.0 to now 3.5 and busy finalizing 3.6 miss one target date? no they never did..... I find that pretty amazing for such a large codebase.
what i hope nokia is going to do is say we are releasing a new firmware every 2 months in the first week of that month.
then just plan make a cut (branch) a few weeks before the release, strart testing internally, fix some regressions, make 1 public beta or something 1 week before. then test some more and release.
in the mean time the trunk stream also progressed and the cycle starts over. (with a bit of planning what to get in (try to) in the next.
|
|
2010-05-14
, 03:57
|
|
Posts: 35 |
Thanked: 56 times |
Joined on Jan 2010
|
#138
|
Originally Posted by jcompagner
Because FW updates aren't something to tack a release date on. You can't schedule a bugfix or a feature that didn't make it into the previous firmware because it wasn't ready yet.
what i just dont get is why nokia cant give us release dates..
is it that hard for them to plan ahead? incredible..
for example i take the Eclipse foundation and there release trains that are planned ahead i think about 10 to 12 months.
those release trains are big, they are a huge huge codebase. Not just the eclipse core system and jdt tooling. no many many sub projects all targeting a specific release date almost a year ahead with mile stone builds every 1.5 month or so.
did they ever in all these years form 1.0 to now 3.5 and busy finalizing 3.6 miss one target date? no they never did..... I find that pretty amazing for such a large codebase.
what i hope nokia is going to do is say we are releasing a new firmware every 2 months in the first week of that month.
then just plan make a cut (branch) a few weeks before the release, strart testing internally, fix some regressions, make 1 public beta or something 1 week before. then test some more and release.
in the mean time the trunk stream also progressed and the cycle starts over. (with a bit of planning what to get in (try to) in the next.
Just ask all those Android users waiting on a 2.x update how they feel about release dates LOL
| The Following User Says Thank You to EverythingBlaxx For This Useful Post: | ||
|
|
2010-05-14
, 04:41
|
|
Posts: 170 |
Thanked: 75 times |
Joined on Jun 2008
@ NYC
|
#139
|
Originally Posted by EverythingBlaxx
Understood it's hard and improbable to ask for a release date, but with PR 1.2, how hard would it be for them to release a "no going to be released this month" date.
Because FW updates aren't something to tack a release date on. You can't schedule a bugfix or a feature that didn't make it into the previous firmware because it wasn't ready yet.
Just ask all those Android users waiting on a 2.x update how they feel about release dates LOL
It would resolve the misplaced anticipation.
It's also more feasible than releasing even a target month?
1:"Hey Bob, think we can release this month?"
2:"Probably not, we still have 6 testers that haven't reported in"
1:"Ok, I'm going to release that it won't be available this month."
Is that asking too much?
|
|
2010-05-14
, 05:53
|
|
Posts: 515 |
Thanked: 259 times |
Joined on Jan 2010
|
#140
|
Originally Posted by Konceptz
Hmm, if its unpredictable, they can't tell you right?
Understood it's hard and improbable to ask for a release date, but with PR 1.2, how hard would it be for them to release a "no going to be released this month" date.
Originally Posted by Konceptz
I understand the community wanting to talk about stuff that is coming down the pipe. How about users taking leaked information with a grain of salt and not placing expectations on Nokia that they did not create themselves.
It would resolve the misplaced anticipation.
Originally Posted by Konceptz
Nice. Make a unfounded generalization, trivializing a process that you have absolutely no view into. Very helpful. ;-)
It's also more feasible than releasing even a target month?
1:"Hey Bob, think we can release this month?"
2:"Probably not, we still have 6 testers that haven't reported in"
1:"Ok, I'm going to release that it won't be available this month."
Is that asking too much?
 |
| Tags |
| black hole, vortex of dumb |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 13:00.