View Single Post
GeneralAntilles's Avatar
Posts: 5,478 | Thanked: 5,222 times | Joined on Jan 2006 @ St. Petersburg, FL
#31
Originally Posted by qgil View Post
This thread is about how to handle feature requests and now you are mixing with bugs. A different battle even if in bugzilla they are so close.
Originally Posted by GeneralAntilles View Post
New hardware doesn't explain why so many perfectly valid and reasonable enhancement requests and bugs that were filed right after the first releases of OS2008 went totally and completely ignored until the clock for new OS2008 improvements ran out and they were simply WONTFIXed.
We were talking about generic Bugzilla voting and reasons why people might not feel very inclined to vote (on bugs or enhancements). So, yes, I'm also talking about bugs.

Originally Posted by qgil View Post
The common denominator of these bugs seems to be: won't be fixed in Diablo but won't be a problem in Fremantle because XYZ is refactored.
See, that excuse might fly if these bugs had been filed only a few months ago, but many of these bugs have been sitting ignored for almost as long as OS2008 has been available, only to be WONTFIXed recently because Nokia can't be bothered to triage their damn bugs.

Originally Posted by qgil View Post
The teams have to negotiate between the time they invest in the old components to be discontinued or building the new components with the fixes build in. In case of doubt they move forward to the next release, yes. Hopefully releasing early SDKs helps rising those issues before, while the teams are still investing most of their time in the current release.
Yes, I'm glad these wont be issues for Fremantle, but it's not particularly heartening that current device owners are still screwed.

It would be much less of an issue if new releases didn't invalidate old hardware, but they do. The same thing happened to 770 bugs when the N800 was released.

Clearly there isn't an easy way around new hardware invalidating old in the embedded market, but if Nokia would stop ignoring community bug reports and invest a little time in at least trying to push fixes and improvements for current releases the community would be a lot happier.

Clearly resources are limited, and clearly fixing every single bug and enhancement for the current generation isn't realistic, but a little effort in this direction would go a looong way.

Originally Posted by qgil View Post
So basically, all those requests will be satisfied in Fremantle even though they get wontfixes in Diablo.
WONTFIXed because Nokia didn't bother to look at the bugs while the window for fixing them in OS2008 was still open. If the bug missed that window because it was filed too late in the cycle, fine, but missing it because it sits dead for 8 months first isn't acceptable.

Originally Posted by qgil View Post
Andre does his job as I do mine and others do theirs. Even if Andre is not a Nokia employee, he is being funded by Nokia and gets a good salary to be as efficient community bugmaster as he indeed is. As said above about the feature requests, in order to have a Brainstorm working the product managers need to be directly involved, agreed.
Problem is, Andre can only do so much running back and forth, and that running back and forth detracts from more useful activities like actually getting Nokia to use Bugzilla. . . .

Routing all communication between Nokia engineers and managers, and the community through one person is incredibly inefficient. The result seems to be bugs going ignored until the window of opportunity to have them fixed in the current release has closed.

I'm more optimistic about the future, but you'll understand my frustration with how things seem to be working now and how things worked in the past.

Anyway, this is somewhat off-topic.
__________________
Ryan Abel
 

The Following 2 Users Say Thank You to GeneralAntilles For This Useful Post: