Re: OFF TOPIC LIST CRITERIA

Would it be surprising to know that I know the difference between a user issue and a bug and feature. I have commercial experience and training in safety critical software (aerospace). Believe me that is an entirely different world. With entirely different standards. Obviously if I want an

Re: OFF TOPIC LIST CRITERIA

Hi THough Sean requested a non-reply, but this is sincerely crazy. @Zahid - what Sean said is actually mentioned in Spark's website - u...@spark.incubator.apache.org -- for usage questions, help, and announcements.

Re: OFF TOPIC LIST CRITERIA

OK *user support. user@ is DONE !!!* I reported a work around to an existing bug actually to the experienced user. and "the experienced user" was "not aware" of the setting in the log4j.properties so he learned something new too. Clearly neither were you. Also it may surprise some people but

Re: OFF TOPIC LIST CRITERIA

BCC user, dev, and I encourage others to not reply. I said _dev@_ is not for user support. user@ is. You heard that yesterday, too, and not to cross-post. You actually got answers to several questions, despite their tone, from experienced developers of the project. Messages like yours are, I

OFF TOPIC LIST CRITERIA

Sean Owen says the criteria of these two emailing list is not help to support some body who is new but for people who have been using the software for a long time. He is implying I think that I should only send email when I find bugs so that I can help him in his work. A one way street. He is