The number of open tickets keeps growing. Searching out keywords in open issues is at this point very hard to do and real productivity killer. I believe we should be much more pro-active about catching issues as they open and routing them properly.
My comments on: HIVE-2085 Document GenericUD(A|T)F. This is the second ticket I have seen calling for "more documentation". All tickets like these should be closed instantly unless 1) User wants to write an xdoc or java doc and get it committed. Otherwise user can update the wiki. There are many things that could be documented "better" and having a ticket to remind us about each one is not practical. HIVE-2079 The warehouse directory shouldn't be 777'ed We need to intercept these issues better and get better descriptions of exactly what the person wants to do. Such as: 1) How does this currently work? 2) What would be better ? 3) What needs to be changed ? 4) What is the timeline ? This will help the person get on the right track. It will also help us figure out how actionable the issue is. As many of these tickets sound nice, but some never come to fruition, then they sit indefinitely in open state. We need to be more aggressive in intercepting issues and not be afraid to close them as LATER, WONT FIX. Otherwise we are never going to be able to turn this around and the open issues are just going to keep growing. Suggest users to the wiki for ROAD map or the IRC. So they can discuss features before creating vague tickets. Edward
