Thanks, for the pointer. I think even if this gets people think about the problem its a good start, I will raise this question again after 1.2 release. Vitaly Babiy
On Mon, Feb 8, 2010 at 6:46 PM, Karen Tracey <kmtra...@gmail.com> wrote: > On Mon, Feb 8, 2010 at 6:39 PM, Vitaly Babiy <vbabi...@gmail.com> wrote: > >> Hey Guys, >> So 1.2 is almost out the door so I wanted to raise an issue that I would >> love to start working to fix for 1.3. >> > > Not to discourage you, but be aware the focus of most attention until 1.2 > actually goes out is still 1.2. Feature freeze doesn't mean the release is > done, it means attention shifts to bug fixing. You many not find many people > ready to start thinking deeply about 1.3 just yet. > > Karen > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
