Maemo Bugzilla
Yes, I know it's currently a waste of time as it's rarely updated and contains no relevant feedback from Nokia or their developers.
I raised bug #630 some time ago to constructively criticise the current process. Sadly nothing has changed so I urge you to vote or comment on this bug in order to raise the priority. If you think I'm out of line, fair enough - leave that as a comment too! :) I feel bad about giving Nokia a hard time so soon after the release of OS2006, but Nokia talk about being involved in the Open Source community yet have very little direct contact with real users as you would expect with say the Mozilla Foundation. Key features are missing from the 770 - eg. Bluetooth audio (bug #667 - yet we have no way of knowing why, or if a solution from Nokia is in the wings. For all we know, it may be impossible to implement but it would at least be nice to know! So come on Nokia, sort out your communication and Bugzilla management! |
I've not found bugs that slow to be updated. I did a report in bugzilla and it shows almost 1 bug actioned for each day August, maybe thats not enough, but things seemed to be being addressed. Though the idea about naming the QA is a good one.
Rich |
I've seen few if any bugs actioned to be honest, other than the stock response from MaemoQA "passed to upstream maintainer" (followed by silence) - perhaps it depends on our definition of action.
Personally I would prefer if the "upstream maintainers" became more directly involved with those who are reporting the bugs, rather than the bug report disappearing into a black hole ("passed to upstream maintainer") from where it may or may not reappear at some unknown time in the future with the corresponding Bugzilla update "Is this now fixed in OS200x? Thanks, MaemoQA". The lack of progress reporting and general defect management is disheartening - how difficult would occasional updates be, such as "we've reproduced and identified the problem, a fix will be checked in for the next release"? Or "No sorry, the 770 hardware cannot support the A2DP profile because of <insert technical reason>" I'd say the vast majority of bugs have received no response other than mass assignment to upstream maintainers (and while assignment is an action, it's not real progress). Check out the 2GB MMC bug (bug #621) - a working patch was provided, yet we still have no indication if it will be fixed in a future release. At least MaemoQA passed it to the upstream maintainer, but without further feedback and dialog for all we know the upstream maintainer may have been hit by a bus or quit Nokia (neither of which I hope is true, naturally!) |
Re: Maemo Bugzilla
Perhaps providing a glimpse into bugzilla will help more of the community become involved and thereby encourage more bug status updates by the maemo developers:
maemo Bug Jar - A Quick Look at maemo Bugzilla - 2008.04.17 through 2008.04.23 Bug activity this week:
Ten biggest bugs by number of votes:
Is your pet bug not in the top ten? Please post about it (and don't forget to link to it). You might attract some votes. |
Re: Maemo Bugzilla
I hadn't looked at #630 in a while . . . depressing. :<
|
Re: Maemo Bugzilla
An interesting table: https://bugs.maemo.org/report.cgi?x_...op&value0-0-0=
Wouldn't this thread be useful stickied and with more bugs shown here to be voted? I think it would motivate people to vote more, and could be a starting point to newbies to get involved. |
Re: Maemo Bugzilla
Quote:
In any case, I'm still taken with the idea of providing a weekly snapshot of what's happening within maemo Bugzilla. I like to think that providing more frequent information about, and quick access into, the system might increase its use, ideally by all parties. In any case, I'm willing to give it a try. So, I'm looking for suggestions. What information should I include? How should I present it? Should I just sit down and be quiet? |
Re: Maemo Bugzilla
I like your previous idea of Biggest Bugs by Severity. I don't think you should worry so much about justifying your list statistically, as it appears you would like to do. Just an opinionated list would be fine, to me. If anyone disagrees they could create a counter-list. I don't think the FBI uses statistics to create their Most Wanted list, in terms of dollars lost in crime or people killed -- neither should you.
Most Important Bugs Fixed along with a brief explanation of what the bug actually fixes might be nice. |
Re: Maemo Bugzilla
sjgadsby, can I send this bug to your list: metalayer-crawler grabs RAM & CPU, paralysing device.
I think a lot of people suffer from this problem (me included), but it has only 3 votes at the moment. Edit: I totally agree with geneven. |
Re: Maemo Bugzilla
I've practically given up on #303 :-(
|
Re: Maemo Bugzilla
Quote:
|
Re: Maemo Bugzilla
AOL!
Stuff added as you cant post something less than 10 characters. So I voted for it to. |
Re: Maemo Bugzilla
# 2055 is my pet bug. It's frustrating, yes, because it interferes with the way I want to use my tablet, but more so because it's such a silly failure in the interaction between two core parts of the OS. Ah well, at least timeless has finally confirmed the bug. I no longer have to wonder if it's somehow just me.
|
Re: Maemo Bugzilla
maemo Bug Jar #2
A Quick Look at maemo Bugzilla 2008.04.24 through 2008.04.30 6 new bugs were opened:
2 bugs were confirmed:
6 bugs were closed:
Ten biggest open bugs by number of votes:
Ten biggest open bugs by importance*:
Have a pet bug? Please post about it. (And don't forget to link to it!) You might attract some votes. |
Re: Maemo Bugzilla
maemo Bug Jar #3
A Quick Look at maemo Bugzilla 2008.05.01 through 2008.05.07 As of 2008.05.07, maemo Bugzilla contains 3089 bugs, with 1217 of them being open. 18 new bugs were opened:
5 bugs were confirmed:
21 bugs were closed:
Ten biggest open bugs by number of votes:
Ten biggest open bugs by importance*:
Have a pet bug? Please post about it. (And don't forget to link to it!) You might attract some votes. |
Re: Maemo Bugzilla
Looking at these bugs, some should be taken with a pinch of salt as the community has developed work arounds or solutions. Perhaps the bugs aren't completely fixed, but they are at least partially there. So looking at this section (Ten biggest open bugs by number of votes:)
Quote:
Therefore, is this still a bug - or is the buginess only that Nokia don't have this working out-of-the-box? Quote:
Quote:
Now this won't work with the internal player yet (though I imagine adding an alsa-sink and editing the conf files should enable it), so is this why it's still a bug, or the fact that it doesn't work out of the box? And from (Ten biggest open bugs by importance*:): Quote:
I see that there are still bugs against the RSS feed reader (for example), the source for which is now available (http://repository.maemo.org/pool/mae...s-feed-reader/). I would encourage people to look at the bugs and see if there is source now available for the applications in question. If there is source, I'm quite sure the bugs will get fixed more quickly if people submit patches. |
Re: Maemo Bugzilla
#3061 Fun stuff. Not gonna get a 4.1 version because it's "not out yet" . . . yet more reason for Nokia to avoid that bugzilla. :\
|
Re: Maemo Bugzilla
:(
Best i can do on diablo is use nitro for app crashes but it's no bugzilla by any standards. |
Re: Maemo Bugzilla
Quote:
Now, I have tangential questions. I asked them previously in another thread, killing it. (We all have our talents.) What's the etiquette for maemo bugzilla? For instance, I've noticed you, GeneralAntilles, vote for your own submissions. I've not done so, as it feels, well, improper to me. Am I being dunderheaded? I've not found an etiquette FAQ for maemo Bugzilla. Perhaps I should submit an enhancement request. |
Re: Maemo Bugzilla
Quote:
Bugzilla is a place to notify developers of bugs and contribute information that would be useful in the fixing of the bugs. It is not a place for advocacy viz. "I REALLY WANT THIS BUG FIXED!"More directly, bugzilla has an etiquette page, but it doesn't cover voting. Personally, I'm of the opinion that you should be doing everything you can to help the developers find, prioritize and fix bugs— voting is an effective way to help them do just that (well, when people actually vote on what's important to them :\). This isn't like voting for yourself in a political election where one might submit that you have a conflict of interests, you're indicating to the developers what's important to the community and you're a part of the community. I vote on the bugs which are either important to me or I believe should have a high priority (like the 24h bug which, while not important to me personally, I believe is an important bug), and, usually, bugs that I submit are important to me so I end up voting on them. ;) That said, I don't vote on all of my bugs. In summary, vote on what matters to you. |
Re: Maemo Bugzilla
I'm with you GeneralAntilles shouldn't matter if you post the bug if its important to you, then vote for it. BTW Whoohoo I'm a member new 40th post lol.
|
Re: Maemo Bugzilla
maemo Bug Jar #4
A Quick Look at maemo Bugzilla 2008.05.08 through 2008.05.14 As of 2008.05.14, maemo Bugzilla contains 3112 bugs, with 1223 of them being open. 23 new bugs were opened:
3 bugs were confirmed:
18 bugs were closed:
Ten biggest open bugs by number of votes:
Ten biggest open bugs by importance:
Have a pet bug? Please post about it. (And don't forget to link to it!) You might attract some votes. EDIT: At the request of an @maemo.org person (name withheld to protect the guilty), I've also posted this summary to the maemo developers' mailing list. |
Re: Maemo Bugzilla
Quote:
Andre, already, is certainly saying the right things. |
Re: Maemo Bugzilla
maemo Bug Jar #5
A Quick Look at maemo Bugzilla 2008.05.16 through 2008.05.21 As of 2008.05.21 maemo Bugzilla contains 3133 (+21 this week) items, including 1218 open issues (-5 this week):
16 new bugs were opened:
2 new enhancements were opened:
7 bugs were confirmed:
0 enhancements were confirmed. |
Re: Maemo Bugzilla
maemo Bug Jar #5 (continued)
19 bugs were closed:
5 enhancements were closed:
Ten biggest open bugs by number of votes:
Ten biggest open enhancements by number of votes:
Ten biggest open bugs by importance:
Ten biggest open enhancements by importance:
Have a pet bug? Please post about it. (And don't forget to link to it!) You might attract some votes. This summary will also be posted to the maemo developers' mailing list. |
Re: Maemo Bugzilla
Ha . . . I hadn't realized how busy I'd been this week. It's amazing how much old stuff that's been fixed for a while still hadn't been closed.
On that note, it'd be good if we could get some people together to go over all the old bug reports with a fine-toothed comb whenever Diablo finally hits and pick out all the ones that have been fixed and either resolve them themselves (if they've got editbugs—talk to Andre or Karsten if you believe you really deserve it) or toss them over to me or somebody else with editbugs. There's a lot of old bugs lying around that have been fixed that are just jamming up the works sitting there unresolved. Also, I'm on to you sjgadsby! Splitting up your list into two posts . . . what a "Thanks!" whore! :p |
Re: Maemo Bugzilla
Stephen deserves a device discount for all this work. ;)
|
Re: Maemo Bugzilla
Quote:
|
Re: Maemo Bugzilla
Quote:
|
Re: Maemo Bugzilla
I think this bugs are fixed:
Please support vertical scrolling by dragging in mail window (Even in the chinook betas). OS2008 applications menu open or close inconsistently (I haven't seen this in Diablo-20, while it always happens in chinook). Application Manager updates/refreshes entire app list even if an install is canceled.. (This is fixed in diablo). GA, could you mark it as fixed (if they are fixed)? |
Re: Maemo Bugzilla
Quote:
Thanks, yerga! |
Re: Maemo Bugzilla
Quote:
|
Re: Maemo Bugzilla
Quote:
|
Re: Maemo Bugzilla
Quote:
|
Re: Maemo Bugzilla
Quote:
Even if you don't (yet) feel like closing bugs -- just leave comments about progress in Diablo on any issue. Getting devs to do so more frequently is on our (the maemo.org bugmasters) list. Until then, let's just do it ourself. Also, I support the comment about bugzilla permissions. You believe you should have 'em? Feel free to poke us in #maemo anytime! |
Re: Maemo Bugzilla
Thanks for joining itT Karsten!
|
Re: Maemo Bugzilla
Welcome Kasten!
Quote:
Lots of cool things can be done that makes it easier for the end-users. :D |
Re: Maemo Bugzilla
Quote:
|
Re: Maemo Bugzilla
Quote:
But, yes, substitute "Bugzilla" for "Garage" in your post and that might work OK (though translating a forum post into a useful bug submission isn't always useful or easy). |
Re: Maemo Bugzilla
Oh yes, you are correct. For the 3rd part apps, there should be a smart way then to know which Garage bug tracker it should go to. This becomes as a mini-incentive for developers to maintain their apps in the Garage.
|
All times are GMT. The time now is 19:54. |
vBulletin® Version 3.8.8