On Tue, Aug 13, 2013 at 1:37 AM, Chris Wilson <[email protected]> wrote:
> I would love to see support extended for a bit longer after deprecation. This is a matter of resources; we struggle to maintain security releases against 3 simultaneous releases (e.g. right now 1.4.x, 1.5.x, and the up-coming 1.6). Adding a fourth probably isn't possible without a ton of help. > We have apps in production running Django 1.3. There won't be any security > fixes. If there's a critical vulnerability, we may have to do a lot of > unpaid work to either backport the fix, I have to say I find this kinda hilarious: you *know* it's a lot of work to backport stuff, and you'd like *us* to do that work instead of you. > I'm not asking anyone to do my job for me (I hope) but it would be really > nice to have something like 3 years of support for core infrastructure like > Django, that's really painful to upgrade, and even more painful to replace. > It would certainly help me to sleep better at night. > But you are, actually, asking us to work for you. And we're happy to do it! This is what open source is all about; volunteering to do work (often rather thankless work) to help other people sleep at night. But there's a limit to the free time we have, and there's a limit to the amount of scut work you can expect a volunteer community to do for you. Look at it this way: you run 1.3 still, so you have a personal vested interest in backporting work. If *you* don't have the time to do it, what makes you think that *we* do? Jacob -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
