I'm with the grasshoper. We've been patient for quite a while, but we
need a release framework so us mortals (==non-core developers) can
safely post ticketsm. We've been quite, not wanting to interfere with
the crucial work of releasing 1.0, but we have alot of good ideas that
need documentation
Jacob, please release a roadmap ASAP or let us know what version we
should use for new tickets. It's important to have a roadmap (and I'm
+1 for grasshoper's suggestion), even if you'll change it within a
week:
"
1. Jacob is always by definition right about how Django should
behave. This means he has final veto power on the core functionality.
2. Jacob is allowed to change his mind about any matter at a later
date, regardless of whether he previously invoked Rule 1.
Got that? Jacob is always right, even when he was wrong.
"
(adapted from Larry & Perl - http://en.wikipedia.org/wiki/Larry_Wall)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
