Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Many Android bugs with 500+ stars closed as obsolete on December 25

code.google.com

Post reply on HN
Print view View original

91–100 of 201 posts

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#91

Post by chralieboy »

mpdehaan2 wrote: post #88

Managing any project with thousands of contributors is very hard - namely, duplicate bugs, low quality bug reports, bugs that are no longer valid given OS or version changes, etc. I can't imagine how hard it is to manage something on the scale of Android, where it's so consumer-oriented, half of everyone with a phone (roughly) potentially could be using the bug tracker. There may be some interesting room to build a b…

StackOverflow provides a good example of how this could work. They identify duplicates as you type the questions and have many moderators dedicating time, for free, on cleaning things up.

Of course that doesn't solve the difficult matter of actually fixing the bugs, but I'm sure the Android developers would sincerely appreciate it. Closing duplicates or reports with little information sets a standard for the bugs that do get fixed.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#92

Post by realrocker »

Since many of these bugs are also simultaneously raised by OEM's they are closed internally without feedback. And feedback to what bug, they are so many for the same! Also lot of them are feature enhancements and are really opinionated actually to work on. It could be better but it's not that bad. You won't believe the hoops you gotta jump to get anything done. Too many stakeholders in AOSP!(which has both pros and cons). I work on the AOSP for an OEM.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#93

Post by cryptoz »

baq wrote: post #86
cryptoz wrote: post #6

Google's handling of Android bugs is unpleasant and difficult to swallow. The QA seems minimal and little or no attention is paid to user filed bugs. The barometer on the Nexus 5 is still broken after a year+ of software updates. Infuriating. The bug with hundreds of stars is marked obsolete! The barometer is still broken. I'd like to debug and fix it but other things have priority, and I don't feel confident that if…

does pressurenet even work? i can't find any news about it, the site ( http://pressurenet.io/ ) is down for at least a couple of weeks and it looks like nobody else is using it since my map is always empty (which may be an artifact of the site being down). all this is a little bit disheartening.

Hi, yes pressurenet is working! We've had some DNS issues, perhaps you could try if http://pressurenet.cumulonimbus.ca and that might work.

As for your map being empty, that sounds like a bug, perhaps related to the DNS error I mentioned.

Thanks for the report.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#94

Post by droidist2 »

mariuolo wrote: post #29

Just wait long enough until the bug becomes obsolete. It's the same as the Ubuntu(™) way. The user (if still alive) can re-submit it for the newer version, if applicable and the cycle goes on.

Haha, Attrition Driven Development?

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#95

Post by droidist2 »

arthursilva wrote: post #10

Android dev is smelly, even if you target 4.0+. Any mid sized app need several workarounds/hacks in order to work properly.

Absolutely. Android dev makes me appreciate the relative robustness and elegance of front-end web dev, and that's saying something.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#96

Post by tehwalrus »

duskwuff wrote: post #69
tehwalrus wrote: post #46

Earlier quoted context omitted.

There have only been two apple charging interfaces for iPods, iPhones and iPads (excluding the shuffle), and the new one was necessary (if I understood correctly) to take advantage of faster USB3 data transfer rates.

Lightning doesn't currently support USB3, unfortunately. It did get rid of a lot of obsolete old interfaces that were present in the 30-pin dock connector pinout, though, and opened up possibilities for new devices (like the HDMI adapter).

Thanks, I wasn't really sure.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#97

Post by vorg »

kelukelugames wrote: post #5

Silently? This isn't that dramatic. edit. title has been fixed.

The original title "Someone silently closed 37% (19/52) of Android bugs with 500+ stars on Dec 25th" is fairly accurate. Silently not only means without adding a comment, but also hoping no-one would notice which is why Christmas Day is chosen. It reminds me of a year ago, also under cover of Christmas Eve, when one of the 5 despots of Groovy, the programming language chosen by Google to power its Gradle-based Android builds, launched a weekly mailout newsletter from his own personal website, putting announcements there ahead of the community mailing list, and soliciting for subscribers in a clear attempt to take over.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#98

Post by cpncrunch »

arthursilva wrote: post #10

Android dev is smelly, even if you target 4.0+. Any mid sized app need several workarounds/hacks in order to work properly.

We target 2.3/3.0 and have required very few workarounds/hacks. iOS is a hell of a lot worse - there are various bugs either introduced or "fixed" (requiring a workaround) in each release.

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#99

Post by ldng »

eli wrote: post #13
kelukelugames wrote: post #5

Silently? This isn't that dramatic. edit. title has been fixed.

I think the implication is that it happened without much fanfare and during a holiday because they didn't want people to notice.

It's a christmas gift for the Android dev team, right ?

Re: Many Android bugs with 500+ stars closed as obsolete on December 25

#100

Post by on_and_off »

higherpurpose wrote: post #36
krschultz wrote: post #22

At some point in a long living project, you have to declare some bugs are #wontfix. You are just lieing to yourself if you think you will ever get to the end of the bug backlog. It also can become an anchor, the team is focused solely on fixing bugs here and there instead of moving the ball forward (and hopefully fixing more fundamental problems along the way). I've made the call to mass close tickets like this. It's…

This reminds me. Google has the (rather great) Google Moderator tool - so why aren't they using it on a site where Android fans can ask Google properly for features? Using that "issues" list for features is such a pain. Right now if the community wants a new certain feature or they really hate one of the already implemented features, it has to make a big fuss about it on r/Android, an unofficial feedback channel.

The purpose of this (arguably horrible) tracker is not to ask for features but to report bugs. I am not sure that Android fans should be their target group for their future developments either. This is a very niche group and I highly doubt that their preoccupations closely match those of the average Android user.
Post reply on HN