Its really all about the feedback (or lack of it). Sooner or later the lack of feedback will result in a lack of reports by developers.
I would have thought that it would be worth Google's time to add a mechanism to the internal register so that the issues copied from the external register ares updated with public comments/status. Otherwise the free crowd sourcing that is currently occurring will evaporate. William On Jul 22, 7:26 am, Peter Sinnott <psinn...@gmail.com> wrote: > On Jul 21, 7:28 pm, Mark Murphy <mmur...@commonsware.com> wrote: > > > On Thu, Jul 21, 2011 at 2:20 PM, Peter Eastman <peter.east...@gmail.com> > > wrote: > > > Does anyone who works on the OS actually read bug reports? > > > Yes. However, b.android.com is not the issue tracker of record -- an > > internal one is. Hence, I am sure that there are some issues that are > > being addressed but b.android.com has not been updated. And I am sure > > there are plenty of issues that are largely being ignored, for > > whatever reason. > > Seems a little silly to have 2 different bug trackers. > Giving the impression that the public tracker is ignored defeats the > point of having one. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
