On 21 maj 2013, at 14:51, Jannis Leidel <lei...@gmail.com> wrote: > - combine the localflavor packages into one Python package again, call it > django-localflavor > - give all the individual country maintainers also access to that package > - have a central documentation, e.g. django-localflavor.readthedocs.org > - update the Django docs to point to that package > - ask the maintainers of the 7 already released packages to point to the > newly created django-localflavor > > What do you think?
+1 This will make handling backwards compatibility easier, especially by having a central deprecation policy on outdated or invalid data in separate localflavors. Users have the right to know when compatibility might break and when a fix is going to get deployed. Such a combination will also enable users to use a flavor that lacks a formal maintainer. Just $0.02 from the just-proclaimed django-localflavor-pl maintainer. -- Best regards, Łukasz Langa WWW: http://lukasz.langa.pl/ Twitter: @llanga IRC: ambv on #python-dev -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
