I think the survey is a great idea. Following on from Shai's question "one big project, or many small ones?"... I am the latter, so the "which version" doesn't really work for me even with multiple answers allowed. I tend to: . Start each new project with the latest stable version. . Upgrade existing projects to latest stable version if I'm doing major rework (and have time to deal with any upgrade issues). . Leave well alone for projects that are running happily. . I don't have any really old projects, but I'll keep them all on supported versions.
Splitting into 2 questions would be one way to capture this. Maybe: When starting a new project which version of Django you use: [ ] I use the latest long-term support release. [ ] I use the latest stable version. [ ] I run off of master. [ ] I use a "favourite" version. For existing projects when do you upgrade Django: [ ] When there is a new long-term support release. [ ] When there is a new stable version. [ ] I run off of master. [ ] When I want a new feature. [ ] When I am working on that project again. [ ] When the version I am using is nearing the end of its support (or after). [ ] I don't bother upgrading Django, even if it becomes unsupported. Cheers, Mark. -- 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/5a176c0d-8d8a-4edc-8ca0-97ed05a2c9ba%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
