640k
Silver Member
- Joined
- Nov 4, 2009
- Messages
- 2,114
- Reaction score
- 0
those that are calling this a political statement aren't doing a very good job of reading between the lines. the replies are evident that moto is not happy with 2.1 in its current condition and cannot promise a significant enough change that will minimize issues upon rollout.
i applaud moto for trying to hash through the issues before releasing it. it's rare to see developers bring a level of QA to a product like moto is perceiving to be doing.
the original timeline was based off of target dates. in an IT world, a target date can easily be changed if goals are not met in time. in most situations, if those goals fall past the original target date, good project managers will take a step back and make sure that all of the project's bases were covered before defining a new one.
my guess is they've redefined a new target date, but we all know that if that date chagnes, moto will look worse. if they keep coming out with dates, and never deliver, moto will become a laughing stock.
moto has been applauded for their DROID and has been recognized as a once struggling company as one that is relevant again. do all of you really think they want to screw that up now?
i can also guarantee you that moto is not losing money off of their failed target date. the DROID is a huge success for moto, their first in a long while. and even at 2.0, it was still a solid phone. 2.0.1 helped to correct alot of common complaints among users and moto wants 2.1 to be the right step.
and let me throw this out there for you guys that are thinking, "well i can have 2.1 now, and it works, why can't moto get it to work???" remember, all of the 2.1 integration that is available to us is recompiled, merged code from other devices, versions, etc., just to "wedge" something in so that we can enjoy alternatives. there are still a ton of issues between all of the versions that aren't being directly addressed by these ROM developers, that moto would be privy to.
at this point, i wouldn't be surprised if we got right to 2.1.1. or they call it 2.2, or the DROID/Milestone's 2.1 will be different from N1's 2.1, etc., etc.
i applaud moto for trying to hash through the issues before releasing it. it's rare to see developers bring a level of QA to a product like moto is perceiving to be doing.
the original timeline was based off of target dates. in an IT world, a target date can easily be changed if goals are not met in time. in most situations, if those goals fall past the original target date, good project managers will take a step back and make sure that all of the project's bases were covered before defining a new one.
my guess is they've redefined a new target date, but we all know that if that date chagnes, moto will look worse. if they keep coming out with dates, and never deliver, moto will become a laughing stock.
moto has been applauded for their DROID and has been recognized as a once struggling company as one that is relevant again. do all of you really think they want to screw that up now?
i can also guarantee you that moto is not losing money off of their failed target date. the DROID is a huge success for moto, their first in a long while. and even at 2.0, it was still a solid phone. 2.0.1 helped to correct alot of common complaints among users and moto wants 2.1 to be the right step.
and let me throw this out there for you guys that are thinking, "well i can have 2.1 now, and it works, why can't moto get it to work???" remember, all of the 2.1 integration that is available to us is recompiled, merged code from other devices, versions, etc., just to "wedge" something in so that we can enjoy alternatives. there are still a ton of issues between all of the versions that aren't being directly addressed by these ROM developers, that moto would be privy to.
at this point, i wouldn't be surprised if we got right to 2.1.1. or they call it 2.2, or the DROID/Milestone's 2.1 will be different from N1's 2.1, etc., etc.