2015-04-07 17:25 GMT+02:00 Marc Tamlyn <[email protected]>: > The primary questions to establish answers to before a possible merge in > my opinion are: > - Do we ship both, or just the new one and release the old one as a third > party package? >
I'd like to make the new theme the default unless the developer opts out. Since the admin CSS and JS receives very little maintenance, keeping the current theme under django/contrib/admin/classic_theme/static or in a third-party package doesn't make a significant difference for us. The former is more convenient for users who choose to opt-out: all they need is to add 'django.contrib.admin.classic_theme' before 'django.contrib.admin' in INSTALLED_APPS. That will save us some angry emails ;-) This leaves the question of how long we keep supporting the classic theme. I suggest to go for the usual two-releases deprecation cycle and leave it up to the community to maintain it separately from Django 2.1 on. My suggestion would be that we should publicise via this mailing list (and > django-users etc) that we are planning to integrate this, and you can use > it now via your app. This should hopefully get you more bug reports early > and we can merge it in a more finished state for the 1.9 alpha. > Yes, that's a good idea in any case. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CANE-7mWS9gb94jg9XQiR%2BBU9NP4wU4n%2Bvfd9mnfpK0CQK4Tn2w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
