On Wed, May 11, 2016 at 10:06 AM, Carl Meyer <c...@oddbird.net> wrote:
> > I'm not quite sure what this means. By "major release" here, you mean > "major release of the adopted project," not "major release of Django"? > So this means that security fixes for the adopted project will be > provided as patch releases on its current major release, but won't be > backported beyond that? > Yes, my intention was of major releases for the non-core project. We could always extend this to have the same level of coverage as Django; the question is if we treat non-core projects as things that are provisionally going into core and still maturing, or if we treat them as full projects in their own right where the goal is not core integration (which might be good). > > All of those points seem sensible to me, but I'd be interested in > hearing from people who've already been actively involved in localflavor > maintenance. > Me too - I'm not entirely clear what the state of maintenance and releasing is like for it at the moment. Andrew -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFwN1upcp2zrHrv9njmFvmqZ9KP89CzE6nDyR6Rs6BCmTJ65hg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
