Totally agree with Brandon here on the bugs/issues reporting.
On Friday, March 16, 2012 4:42:18 PM UTC+1, Brandon Wirtz wrote: > > > If you honestly want to add value to GAE, please go to each bug and > state why these are not issues and what the work around is. > > > > I think it is unfortunate that GAE doesn’t close “By Design” more of these > so people don’t feel they are being worked on when they aren’t. > > > > Someone just mentioned that sometimes this API “Fails without error”. That > is a bug. If someone would open a ticket about “If you do X the API fails > without error” I would bet money that in 90 days Google would fix the > issue, either as “Now Fails with Error” or “Now Handles calls formatted as > X” > > Yeah, I’m harsh, and unfiltered. You may not see that as helpful, but the > truth is I told you why 2 years later the issue isn’t fixed. > > “Bugs” that don’t include “Code As follows gives result X when expected > Result is Y” aren’t bugs, they are bad coders complaining that they can’t > figure something out. That annoys me far more than the people who got > suckered in to MS that should be on HR. Mainly because the create an app > page says MS is magical except when it is down. The Bug database is so > filled with whining people that I don’t blame Google for not wanting to > read it. > > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/VOzTWZEeuwEJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
