> As I see, maybe undesirable, as this list is declared a developers' list, > but there are a lot of users in this list requesting knowledge from (us).
The fact that ppl are waiting for answers doesn't make this a support list. We have support forums/lists which are meant to solve these issues, and there are even companies offering paid support. Such support issues on the development list just distract developers from real development, and forces developers to spend their time on issues they a) are not necessarily the best candidates to solve b) didn't choose to solve when subscribing to the list c) could spend on enhancing the software. I'm personally subscribed to this list because I'm willing to offer my free time for _development_, not support. All in all, we can much efficiently use our scarce resources if we keep discussions on topic on the proper medium. And for those users who now think how rude this sounds, I have to again remind them, that this is a free project, so never, ever, ever expect more from volunteers than you yourself gave to the community. Also remember that you already got a superb compiler for free. IOW, if you feel you don't get enough support, or you don't get it quickly enough, think again, and try to actively answer those questions which you know the answer for. Do it on the harbour-users list, or on our forum. > I don't know, but we are compulsively to serve them, but now we are far away > from our starting point. We should generate less protuberance in the system > under development, if it is possible. It was just light observation leading > in this discussion now, sorry, it's time to finish it. Sorry but I strongly disagree. We've just released 2.0.0 final and one of the main point of such release, is that we can catch up with development with less concern that we temporarily break something. For those interested in problem-free fixing of bugs in last final release, 2.0.x branch was created at the time of the release, and such work shall be done there. Volunteers may start it right away by merging '[TOMERGE 2.0]' marked patches from trunk to 2.0.x branch. This will ensure that users won't have to wait for next major release to get any bugs fixed, but they can get it much more quickly with 2.0.1. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
