Are Django versions released too often?
17th December 2013
My answer to Are Django versions released too often? on Quora
The Django release process is well documented (see Django’s release process) and has been specifically designed to address the concerns of developers who don’t want to have to spend too much time keeping up to date with the latest version.
Minor releases happen roughly every nine months, and introduce new features usually without breaking backwards compatibility. If a feature is deprecated, it will raise a warning in the version that deprecates it, a louder warning in the next version (9 months later) and will be removed in the version after that (1.5 years after the feature removal was first announced).
If even that is too fast for you, you can stick with a “Long-term support” release, which get security fixes applied for 3+ years. Django 1.4 is the most recent of these, and will be supported until at least March 2015.
Read https://docs.djangoproject.com/e... for more information. Personally (and I’ve had no input at all in to the release process design) I think it’s all extremely well thought out.
More recent articles
- Weeknotes: Llama 3, AI for Data Journalism, llm-evals and datasette-secrets - 23rd April 2024
- Options for accessing Llama 3 from the terminal using LLM - 22nd April 2024
- AI for Data Journalism: demonstrating what we can do with this stuff right now - 17th April 2024
- Three major LLM releases in 24 hours (plus weeknotes) - 10th April 2024
- Building files-to-prompt entirely using Claude 3 Opus - 8th April 2024
- Running OCR against PDFs and images directly in your browser - 30th March 2024
- llm cmd undo last git commit - a new plugin for LLM - 26th March 2024
- Building and testing C extensions for SQLite with ChatGPT Code Interpreter - 23rd March 2024
- Claude and ChatGPT for ad-hoc sidequests - 22nd March 2024
- Weeknotes: the aftermath of NICAR - 16th March 2024