Re: Has anyone from the Maemo team actually responded to any bugs?
 

I've seen a couple of photos that look like this on the net. However, it may well be that those have all been taken by preproduction devices, I don't know. I just remember being not so impressed by the quality when I first saw some samples a couple of weeks ago.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Please check out threads http://talk.maemo.org/showthread.php?p=328657 and http://talk.maemo.org/showthread.php?t=29907&page=4 to be up to date on the question of basic expected functionality.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

I was going to wait till Maemo 6 was released, but I took the plunge anyway. So, the question now is...will we be able to upgrade to Maemo 6 software on our N900's? Or will we have to buy the new N950's or N1000 or whatever it is?

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Maybe. Until 6 is out we will not know for sure imho.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

These debates about whether it's possible to release updates in small pieces when they're ready, or whether it's possible to do development in the open or not always seem very odd when there are a good number of existing desktop Linux systems, considerably more complex than Maemo, that manage to do this as a matter of routine.

It works, we know it does, because we're already doing it.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Also see the comments in https://bugs.maemo.org/show_bug.cgi?id=5709 and the corresponding Brainstorm ticket.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

About the initial question of this thread, a couple of links that you might or might not find interesting

http://maemo.org/profile/list/catego...illa_reported/
http://maemo.org/profile/list/catego...illa_comments/

And perhaps more interesting, it must be possible to extract Maemo 5 bugs filed since October 9 (the day Summit participants got devices to test) that have been resolved as fixed, and probably even more accurate stats of bugs filed on the sales release that have been addressed already. There is quite a lot of information at http://bugs.maemo.org and anybody can extract it doing some clever searches.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Something like this should be stickied, seriously. Thanks qgil :)

Re: Has anyone from the Maemo team actually responded to any bugs?
 

If I'm not wrong there is only 80 bugs fixed so far. Could that be right?

https://bugs.maemo.org/buglist.cgi?q...op&value0-0-0=

Re: Has anyone from the Maemo team actually responded to any bugs?
 

OK, here's a question: if we do end up OTA fixing bugs automatically on the go, how do we communicate what's been fixed?

Honestly, the average consumer (and quite a few of them have the device), will probably not want to search for bug fixes all the time so they're likely to not bother finding fixes to what's bugging them (pun intended). But if you do it automatically then they'd probably like to know that their email clients now work perfectly etc.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Fixes show up in updates, so no one has to search.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

OK, cool! Good to know that's been taken care of nicely :)

Re: Has anyone from the Maemo team actually responded to any bugs?
 

It would be nice just to be able to get the FW to use my PAYGO 3 sim card. The rest of the stuff should really be bug fixes, and concentrate on new features later.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

If that is https://bugs.maemo.org/show_bug.cgi?id=5315 , it is fixed internally.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Yes, that could be right, as bugs.maemo.org is not the only source of bug reports for Nokia. :-)

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Just shooting to the air, but I bet on a portrait keyboard, since the browser will have a portrait mode is reasonable to think in a portrait keyboard, at least make a lot of sense for me :D

Re: Has anyone from the Maemo team actually responded to any bugs?
 

This is also sad :(

Hiding bugs in internal-only trackers just keeps people in the dark for no good reason.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

And that's what made so wonderful Ari Jaaksi's announcement at Maemo Summit 2009 that Nokia will be shifting to use bugs.maemo.org as the sole Maemo bugtracker.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Migration is not gonna happen in short time. It's not just nokia employee using it but some subcontractors, 3rd party companies, etc. But feel free to devote your bugs on bugs.maemo.org here and brainstorm. And note that Nokia does appreciate your submission.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

The whole MMS thing is very sad since when i talked to customer swervice AND THE OFFICIAL NOKIA FLAGSHIP STORE IN NEW YORK, they all told me YES YES THER N900 has MMS all for me to find out after buying it that it does not and looks like a new device will be out in the 2nd half of 2010 that WILL more than likely have it. its cool though u live and u learn and i have learned that when talking to official like sales folks and cust. reps make sure i record the convo for quality assurance

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Ah. That is good news.

They can all get bugzilla logins too can't they?

Re: Has anyone from the Maemo team actually responded to any bugs?
 

btw i saw the bug for the bluetooth file sharing and voted for it and now some great humanitarian created petrovitch ! i love this place.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Yes.

Realistically, do expect Nokia to keep some updates to bugs, and some entire bugs, private within our happy, public bugtracker though. They're still going to want to keep some details of upcoming releases and devices hidden, and there will still be information that cannot be disclosed due to licensing, security, or whatnot.

Still, this will eliminate the excuse of not copying non-sensitive bugs to the public bugtracker one at a time, as they come up, just because it's too much work. Plus, it does away with all that busywork Andre does now playing middleman, freeing his time up for tasks more appropriate to his high skill level.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Well, I'd hope that can be minimised, but certainly there's a legitimate need to have (some) security bugs hidden, and that's pretty common practice in mainstream Linux distribution bug trackers too.

Yup, it'll be a big step forward. It's not enough in itself, Nokia engineers need to have the confidence that they can communicate openly by default without marketing breathing down their necks (as if hiding things from your customers and releasing software that's less well tested than it could be was good marketing anyway), but it should help.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Understand that this platform started from the direction of closed (ie, commercial world), unlike something like, say, Pandora. If you look back over the history of Maemo you can easily see the steady (but slow) progress toward increased openness.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Yes, though a phrase involving "kicking and screaming" does spring to mind at times, movement does appear to be in the correct direction.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Application Manager supports changelogs for individual updates (if the package maintainer bothers to fill them in), so I would argue that if individual updates were released one-by-one the changes in each package would be more visible to the user than if hundreds of updates were rolled into one SSU.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

i knew that thanks, but just getting it on the device would be good.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Changing a corporate behemoth to operate in a new way is like steering an oil supertanker. A super tanker can't turn on a dime, and neither a large corporation. So nice and steady change is the best pace one can hope for.

Re: Has anyone from the Maemo team actually responded to any bugs?
 

Fixed internally is a good beginning, but, now... 3 weeks after the fix nothing happens... and no way to get a internally version.

Have we all together start to work for Nokia? ;)
Is buying the phone not enought?

Okay, stop kidding. Is that the way that we must wait many weeks or month for every single small fix?

There are a lot of even small issues in the calendar, in the contacts and so one. Sometimes only about 1 oder 2 hour's of work including testing, I guess.

Release small Hotfixes for this small bugs and issues would really disarm a lot of the upset!

Re: Has anyone from the Maemo team actually responded to any bugs?
 

There is difference between bug-fixing from developers point of view and release management from the program point of view. Once developers fixed a problem and verification has run successfully, packages are handed over to release management. People in the release management group have their own schedule for releases and currently those done in monolithic way due to various reasons, both technical and operational (for example, any incremental update would still need to be properly working in monolithic release due to production line requirements). In addition, Nokia-wide approaches are to be followed as nobody is turning working production processes to Maemo specifics overnight; rather Maemo needs to adopt.

Said that, I'd too would like to see repository updates working incrementally sooner than later. However, I know the difference between upgrading through repository and getting properly working monolithic build could be very hard to achieve sometimes. Unfortunately, space/memory limitations on the device side are not helpful in allowing apt/dpkg to solve all upgrades properly 100% of time and bugs are bugs, they are in apt/dpkg too. I know, I've been doing GNU/Linux distribution development with apt for more than 10 years...