> The problem is that people pop up every couple weeks and ask precisely > the sort of thing you're asking: in effect, "what's the status of > this, and when will it land in trunk". The answers to these questions > haven't changed in a very long time; what's needed is people writing > code, not people asking the same things over and over.
How about changing anything then? 1) This is not documented at those places where people finds out these features exists. They think like "authors has documentation and feature exists => feature is supported". I think someone should find out what branches/features are unsupported now and clearly write about it. 2) Also more than half of people (usually newcomers) don't try to search in archives before asking anything. Maybe write an answering bot for them that will reply immediately with similar archived threads? :\ -- Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov, MSN: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
