On Nov 30, 7:33 am, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote: > And, finally, a bit of a controversial statement, but... > > I think we ought to call the release 2.0.
Well, there are lots of precedents. Emacs went from 1.12 to 13.0 at some point, so the jump from 0.96 to 2.0 does not seem that large :) The list looks good. My pet peeves are trivial bugs that prevent django-multilingual from working with clean Django checkout, but one of them (#3275) was recently fixed in qs-rf and the other (#3434), while still present in newforms-admin, is not as serious there as in trunk (I did not test it yet, but it looks like you will get javascript error instead of an exception in Python code). On the other hand, merging qs-rf will break the multilingual machinery anyway, so I just hope to have enough time between the qs-rf merge and the release deadline to make django-multilingual compatible again, as it might shake out some hidden Django bugs again. But that is most probably obvious to you: the list includes at least two branches with quite low-level changes, so we need to plan a significant amount of testing and debugging time _after_ those are merged or we will get a traditionally buggy .0 release. -mk --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
