Obviously getting feedback from users is not too vital to you guys 
otherwise you would'nt have ignored the Issue Tracker for 4+ years. How is 
it that no one is held accountable for this? How is this acceptable for a 
company such as Google? 

If it takes you this long just to fix the issue tracker, I can only imagine 
how long it will take for the actual issues themselves to get resolved. 
Maybe 5 years later we will actually get Servlet 3.0 support. Probably not 
though.

On Wednesday, July 9, 2014 10:48:52 AM UTC-4, Jesse Scherer (Google) wrote:
>
> Over the past few years we have fallen behind on updating our issue 
> tracker on Google Code. But since getting feedback from our users is vital 
> to us, we will be renewing our focus on making the tracker useful to you.
>
> We must work through the large number of open issues which exist today. 
> Many of the older issues issues represent popular feature requests, but 
> others were opened long ago and are no longer relevant to the person who 
> opened them or to the App Engine community.
>
> We wish to fix this so that developers can easily find and follow issues 
> which apply to them. So, over the next few weeks we will review open issues 
> and close those that are obsolete and merge related issues together when 
> possible.
>
> There is much work to do here, and in some cases we may inadvertently 
> close issues which are still relevant and important. If an issue which 
> affects you is closed and marked as obsolete or as a duplicate of another 
> issue, please comment on the issue so we can take another look.
>
> How you can help
>
> --------------------------
>
> 1. Check for a duplicate first. If so, star that issue. We often do sorts 
> by number of stars, so if it's a common issue, lots of duplicates can cause 
> us to miss it
>
> 2. Write a clear, concise bug report. This is a report that needs to be 
> read several times. Write very clearly reproduction steps, OS, SDK version 
> and post code if you can. If we can't understand the bug report, we will 
> close it. 
>
> 3. Follow up. We will sometimes post questions in the bug. If we don't 
> receive a response, we will close the bug. Also - if it turns out to be 
> user error, it helps us a lot if you post your fix. This sometimes helps us 
> expose places where we can improve our documentation.
>
> Thank you all in advance for your support and commitment.
>
> -- 
>
> Jesse Scherer | Technical Program Manager | jsch...@google.com 
> <javascript:>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

Reply via email to